36

I'm switching for web development to Android development. I know some things about web usability and I see that UX is too often left behind on Android from my I experience with it.

As the interaction paradigms are pretty different from the web, I'm looking for resources about Android UI guidelines/best practices.

Could you give me some pointers here?

|improve this question

closed as not constructive by Ben Brocka Aug 3 '12 at 15:34

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.

42
|improve this answer
  • 6
    Could you add some information to each link to indicate what's being offered? – Rahul Jul 10 '11 at 16:51
13

Google launched Android Design which provides design guidelines to achieve a consistent style across the platform. It includes information about:

  • General principles such as consistency ("If it looks the same, it should act the same") or use of unobtrusive notifications ("Only interrupt me if it's important").

  • Layout and visual style including icon design, typography (Roboto typeface), color scheme, themes, considerations for multiple screen sizes and densities.

  • Interaction patterns and specific widgets to support them. You can find design guidelines to resolve common problems (navigation, user notification, etc.) and widgets the platform offers (buttons, lists, text fields, etc.) with recommendations for their use. I have included below an image used to illustrate the design of notifications:

Parts of a notification

|improve this answer
  • The following excerpt from those guidelines had me laughing though: When the previously viewed screen is also the hierarchical parent of the current screen, pressing the Back key will have the same result as pressing an Up button -- this is a common occurrence. However, unlike the Up button, which ensures the user remains within your app, the Back key can return the user to the Home screen, or even to a different application. (from the "Back vs. Up" section in the Patterns chapter, Navigation page) – Kris9000 Jan 15 '12 at 2:36
4

Motorola have a good page on Best Practices for User Interfaces with some videos. I think it's a great place to start.

To summarize each section title here (copied from the page above):

  1. Read the UI guidelines
  2. Understand and design for touch mode
  3. But, support multiple interaction modes
  4. Use notifications and the window shade
  5. Support interaction between applications
  6. Keep your UI fast and responsive (see Google I/O talk: Writing zippy Android apps)
  7. Use widgets and live folders
  8. Handle screen orientation changes
  9. Use images wisely
  10. Use layouts that adapt to multiple devices
|improve this answer
  • Moto link is dead. – Mudassir Nov 30 '17 at 11:14
3

http://androidpatterns.com is a nice resource as well, but beware of some inconsistencies and less accurate information, not to be used as a solo reference.

|improve this answer
2

I just stumbled over a Android Design Site where design principles of Android 4.0 are shown, quite similar to Apple and Microsofts Guidelines. So for archive purposes this post.

|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.