UXDivers / Grial-UI-Kit-Support

This is our public repository for customers to report bugs about Grial UI Kit for Xamarin Forms
61 stars 26 forks source link

Grial roadmap #47

Open jpbrocca opened 8 years ago

jpbrocca commented 8 years ago

Hi everybody!

We have made the roadmap for next Grial version. In the process we had some disagreements so we -luckily- thought that the best way would be to listen to our customers :)

So our next version will simply add more screens covering more common Mobile UI patterns. Also we will provide more themes over Grial and support for tablets.

I would like to hear your thoughts about what screens you would like to have, so please add your comments on this thread.

Also, we welcome any feature request and suggestions. If we could not make it for our next version, those could be considered for future updates. Once we collect all your feedback we will make a poll and the most voted features will be added to the kit.

We encourage you all to participate and help us to help you :)

Thanks in advance! JP

markdav-is commented 8 years ago

I'm moving to PRISM for MVVM and it would be awesome if you supported Prizm OOTB.

ghost commented 8 years ago

Great documentation would be awesome. This comes from a newbie!

ssotir commented 8 years ago

I would love to see something covering the map control with custom pins and callouts. Why not a data binding feature.

mrutter commented 8 years ago

Hello everybody. This is a first "wish"-list of suggested features:

  1. Support for UWP/Windows Mobile.
  2. Deploy GrialKit as Visual Studio Template/Templates (avoiding copy of solution, renaming namespaces, changing projects GUID and so on). I was thinking to two different cases: a template for create a new complete solution; more templates to add singles features to a GrialKit solution (for eaxample, after creating a GrialKit based solution, ability to add items such as "Login Form", "Product List", "Social Profile", ...).
  3. A VS tool that allows developers to easily change GrialKit settings (colors and so on). BTW, my team and me started to develope such a tool but we had to stop developing due to time reasons.
  4. Support for Materials Icons (https://design.google.com/icons/)
  5. +1 for tablet support, of course!

... more suggestions to come in a next comment.

Thank you very much for your great work!

kandiva commented 8 years ago

First remove the unrealistic licencing terms. Make more screen templates for each type, to make it worth for $200 you should have at least 200 screen templates

dtila commented 8 years ago

Hi. In my oppionion the most important thing would be to move to a subversioned system so you can see the changes between the version which your app is using and the new one.

If is quite hard to do this, and you need a lot of diffs

deman4ik commented 8 years ago
  1. UWP support
  2. Tablets support
  3. Good new CarouselView implementation - Image Gallery and Content Rotator
  4. CustomTabBar like CustomNavBar
kolchy commented 8 years ago
abbasali-io commented 8 years ago
NVentimiglia commented 8 years ago
rsseurope commented 8 years ago
baris1987 commented 8 years ago
caseyniemann commented 8 years ago

Swipe Right and Swipe Left List Bar Top and Bottom Menu Bar (See Outlook & GHangouts) Right Hand Pull Tab--See Dropbox

babernethy commented 8 years ago
babernethy commented 8 years ago

Another common thing I seem to be adding is a wait/loading/progress-bar type overlay - a nicely designed and implemented option(s) for this functionality would be nice ...

NVentimiglia commented 8 years ago

On the font awesome note, I am using a static const file with all the icon names with the character code. eg.

<Label
          Grid.Column="1"
          HorizontalOptions="Center"
          VerticalOptions="Center"
          Text="{Binding Source={x:Static local:UXFontIcons.FAFileText}}"
          FontSize="28"
          TextColor="{StaticResource ComplementColorDark }"
          Style="{StaticResource FontIcon}">
        <Label.GestureRecognizers>
          <TapGestureRecognizer Tapped="OnBack" />
        </Label.GestureRecognizers>
      </Label>

Might be a good policy

jpbrocca commented 8 years ago

@NVentimiglia, yes it is a good idea.

I didn't have the time to write our plans for font icons but since you mention this I am going to write them here :)

Thanks! JP

jpbrocca commented 8 years ago

Hi again guys :) First of all, thank you for your suggestions!

I have collected them on a Trello board: https://trello.com/b/NwNdlHQK/grial-2-0

This board is public, so you can vote your favorite features and also add comments.

Best, JP

jpbrocca commented 8 years ago

Hi @baris2887, thanks for your suggestions!

So I would like to get more info about your suggestions about:

Thanks a lot! JP

jpbrocca commented 8 years ago

Hi @rsseurope, thanks for your suggestions :)

Can you provide some sample about your suggestions:

If you could add some screen shots or links to some samples (could be an app to download from a store for instance) that would be great.

Thank you very much! Best, JP

rsseurope commented 8 years ago

@jpbrocca thanks for your interest in my suggestions!

  1. With the scheduler i mean some sort of planner tool like this: 1 2

these should be able to databind to appointments and should be stylable (for instantance the time between rows)

  1. screens for data processing apps are a little harder to describe. but maybe the following example will help. This is a form that is used in a web app for acquiring information. As you can see a lot of field with data are available. Maybe you could design a way to make this kinds of screens beautifull and userfriendly in xamarin apps 3
jpbrocca commented 8 years ago

Hi @rsseurope, definitively I am interested in all of our customer's suggestions so I am the one that should thank you :)

Ok, for the first one (scheduler) we can create all the templates, bindings and the screens to support that. Is that what you are looking for ?

For your second suggestion we will keep it in mind and see what we can do for such cases :)

Best regards and again thanks! JP

rsseurope commented 8 years ago

@jpbrocca perfect!

DavidSilverlight commented 8 years ago

I would love to see the following included in templates for the upcoming roadmap.

a) Mapping functionality b) Video Player functionality c) Rich Textbook Editor d) Tab control e) Entry validation behaviors, similar to the email and password, for things like phone, dob, etc.

rex232 commented 8 years ago

I hope coming version can include a blank and clean template

Korayem commented 8 years ago

Hey @jpbrocca :)

I already sent you this on email, but since you're collecting things here, I thought of re-sharing it.

The market doesn't have a feature rich Tabs UI Control which is, IMHO, one of the most used UX design patterns in mobile. Current TabbedPage is nice, but renders totally different experiences across Android and iOS with little to no control over layouts.

Features

Would love to see the following features:

Example

image

Loai-Alhalabi commented 8 years ago

Hi,

JamesPetras commented 8 years ago
  1. Tablet support
  2. Horizontal list view (e.g. grey menu - http://a5.mzstatic.com/eu/r30/Purple41/v4/d8/cd/01/d8cd01bc-8742-2295-c0f8-e049825d6b45/screen696x696.jpeg
  3. Custom tabbed page https://lh6.ggpht.com/p3TzR2lnejWUhsucWJiGaNIGptKfpCPVhRZyYfd6x9eBXRvY_z8_NRiBvBD6f2p1wg=h310
angelcalvasp commented 8 years ago

UWP Support :D

mrctito commented 7 years ago

1- Better documentation about each page template and control, showing how it compares with Xamarin default pages and controls.

2- More separated examples, small samples for each page template.

3- A lot of comments in source code.

4- Global Toasts notifications

5- Swipe Right and Swipe Left List Bar

anomaly2 commented 7 years ago

Modal error/notification dialogs

wkunker commented 6 years ago
  1. Documentation is sparse and doesn't seem to cover many of the basic conditions one can encounter when using this product; I have encountered more than a few Grial-specific problems which I could not find mention of in the Grial documentation. It seems like there's a typo in every other paragraph, but that seems to be par for the course in the Xamarin world (Xamarin/Forms documentation has the same problem).

  2. The way the license is enforced is ridiculous. You can't even run your application for development purposes if you change the bundle ID. I've encountered a few situations where this made my life more difficult at work. Do you really think developers are going to risk illegally using your product in production over 200 dollars? As it stands, I would not recommend Grial to anyone because of this restriction alone.