I'm developing a material design app. I want to know that can I add settings option in a Floating Action Button?
Like when user press the button (FAB), settings will be opened. Would this be a good user experience?
I know this question is framed quiet badly, but I didn't find a better way.
Please cooperate.
Thanks in advance.
I won't recommend that. According to Google guidelines, Settings can be shown in the following ways(Please refer the url) https://www.google.com/design/spec/patterns/settings.html#settings-grouping-settings.
And FAB is used for a promoted action. By promoted action means, an action of more priority, which eases a most used action(say, 'Compose' in Gmail).(Please refer this url)
https://www.google.co.in/design/spec/components/buttons-floating-action-button.html#buttons-floating-action-button-floating-action-button
And, of course you can decide where to keep these sort of thing. Ultimately you are the owner of your app :). But these guidelines are good to follow since it will meet a common user's expectation. Ultimately, UX matters ... :)
Related
I am relatively new to android development and I'm having a good time so far. My application is functional and I'm ready to add a few options for the user. There seems to be a wealth of information on the ways to do this and I'm having trouble sorting through it and determining which way is the current "accepted" method of providing options to the user.
Does anyone have a great resource to share?
It really depends on the particular app, existing UX, branding and a ton of other design considerations.
In general, starting from scratch, a good starting point (though not universally!) would be the action bar. It gives the user access to ways of manipulating the data on screen, as well as a way of consistently presenting secondary functionality (the overflow menu). Design docs, implementation docs.
I would heartily recommend going through the Patterns section of the design documentation, as it explains the rationale behind many of the core design decisions.
P.S. The reason I'm eager to underline that it's not universal is apps with established UX and user expectations. Examples include Facebook, Path, Google Maps. They all have their reasons for not sticking strictly to the action bar paradigms but they work with it as much as they can.
This Menu Doc page is particularly helpful. But basically if it is API < 11 then you use the hard menu button for an options menu. After 10 the menu items will show in either the ActionBar as action items or in the overflow button. But can still be located in a hard menu button if one exists.
You also always have the option of a contextual menu, primarily with a long click, for things like certain menus depending on the View that is triggered. So maybe show an edit, delete, save menu for a list item.
I am interested in doing my application similar to the contact apps where on click on the image pops up a small quick action menu(Not sure of the name). In that you get option to call them, email them or do similar activity. I too have a list view with a image in it. On click of the image I want to show a similar small action bar that will give quick links to users to navigate to my next activity. Please let me know how to do this. A quick sample will be good. Thank you for your time and help.
IMO GreenDroid is a full-featured UI framework, but if you just want the QuickAction in your apps, you can use this http://www.londatiga.net/it/how-to-create-quickaction-dialog-in-android/
Just feel this way is simpler :D
The GreenDroid QuickAction is what you are looking for I think https://github.com/cyrilmottier/GreenDroid
I would like to put fairly extensive help information within my app - both "how to use" and explanation of what one is seeing.
The app (map oriented) has a row of buttons at the bottom, and I was considering adding a help button.
Context sensitive help is mostly not appropriate, btw.
What are common and best practices for this?
Thanks
I wouldn't suggest using a help button, once the user knows how to use your app it will be useless, and will only takes some space.
What I do (but it's maybe not the best practice) is to show a popup on the first use. Within the popup I put some basic help and a link to my website which fully explains how my app works (with some screenshots to make it user-friendly). I also put a "Help" button in the activity menu which redirects to my website again.
What I can suggest is to explore by yourself how other android apps shows the help information, and reuse or adapt the one you prefer (this is what I've done).
I have put help into a menu item as I expect new users to click the menu button anyway (my app, Zwitscher also has a button bar at the bottom).
Clicking the menu item then starts an Activity that simply shows a table view that explains the various buttons in the system and contains a link to more information online.
See https://github.com/pilhuhn/ZwitscherA/blob/master/src/de/bsd/zwitscher/HelpActivity.java and
https://github.com/pilhuhn/ZwitscherA/blob/master/res/layout/help.xml
Another option I've seen sometimes is including a help option in the preferences/configuration screen.
Usually it starts a new activity with a sequence of steps to make the user understand everything.
I have one doubt, regarding the header navigation control. So my question is instead of having a normal/default title bar , my app should have a customized header view that should be placed at the parent (Top Position) of my screens and it(header) should have some options to be displayed in a horizontal view and those options should be reacting to the events and my inner view should navigate according to the select events
Is it possible to bring my thoughts live. Since i have seen this design and functionality in an android application, i am keen to know to do the same. So please let me know the details regarding the same,, if anybody knows.. Any help will be much thankful
Thanks in Advance...
I am guessing you are talking about something similar to the facebook or the twitter action bar. You could give this link a look. It is Google's own app Iosched and implements an action bar kinda similar to what you need. Use SVN to download the app source, play with it and implement your own.
http://code.google.com/p/iosched/source/checkout
P.S. You would also want to choose a few answers occasionally to increase your acceptance rate. Out of 29 questions you have asked, you have an acceptance rate of 25%. Defeats the whole purpose of Stack Overflow. ;)
i asked so many question regarding my title but i could not get my proper answer till yet.I need to implement androd's menu feature in my application ie when we goes to gallery in android phone, when we press menu than it comes with lots of option like share...etc.My question is can i implement same menu feature in my application? It is possible or not?
Thanks
To implement a "Share" feature, all you need to do is use createChooser() and an ACTION_SEND Intent.
Here is a blog post covering the technique.
If I am understanding your question you want to know if you can duplicate the feature of tapping on the menu button on the phone and having it pull up an options menu that you can then share via, gmail or some other posting medium?
If this is correct then I would have to say I would assume that you could duplicate this feature.
In short YES!
If you are wondering how you are to do this then I would start at here http://developer.android.com/guide/topics/ui/menus.html
Droidnova .com (I posted it like this because as a new user I can only post one link) also has a good little how to on menu's.
I would also like to add that this is my first time posting on stackoverflow so please let me know if this was a good post or what I should do next time.
Thanks,
Bactos