This is a slide deck that aided a presentation I gave at an Android Developers Group meetup. It can help you get past a few of the areas of the guidelines that could benefit from some further explanation and some modification of language. Please download the file and view in presentation mode to see the animations that were put in to help with the navigation section.
11. “These design principles were developed by
and for the Android User Experience Team
to keep users’ best interests in mind.”
- Android Design Guidelines
@triciacervenan 11
12. “Your app will play an important part in
keeping the overall Android experience
consistent and enjoyable to use.”
- Android Design Guidelines
@triciacervenan 12
13. You have about 30 seconds to captivate
someone before you potentially lose them
forever.
@triciacervenan 13
14. My own personal mantra: If I have to tell you
how to use it, I didn’t do my job right.
@triciacervenan 14
15. Ratings and reviews are second most
important contributor to rankings.
@triciacervenan 15
16. It’s easier to develop to the guidelines...
if you understand them.
@triciacervenan 16
23. Up is not Back, except when it is.
Up is Back, except when it’s not?
@triciacervenan 23
24. “When the previously viewed screen is also the hierarchical
parent of the current screen, pressing the Back button has the
same result as pressing an Up button—this is a common
occurrence.”
@triciacervenan 24
25. “When your app supports
navigation from a list of items
to a detail view of one of
those items, it's often
desirable to support direction
navigation from that item to
another one which precedes
or follows it in the list.”
@triciacervenan 25
26. “However, a notable
exception to this occurs when
browsing between related
detail views not tied together
by the referring list.”
@triciacervenan 26
27. “You have the ability to make
the Up behavior even smarter
based on your knowledge of
detail view.”
@triciacervenan 27
28. Rule #1: As long as the user stays in the same section, up is
back.
@triciacervenan 28
29. Rule #2: A collection list is not part of a section, so up is back.
@triciacervenan 29
30. Rule #3: If a user jumps to a
different section or app, up
takes the user to the top of the
new section.
@triciacervenan 30
31. Rule #4: See rules 2 and 3.
A collection list isn’t part of a
section, but the detail view that
it can bring a user to is. So, if a
user navigates to a detail view
from a collection list, up takes
the user to the top of that detail
view’s section.
@triciacervenan 31
34. Tip #1
An app is not a website. Be careful
about linking between sections. Or
don’t do it at all.
@triciacervenan 34
35. Tip #2
Your user is not stupid, but they are
in a hurry. Don’t make them have
to work extra hard to get the thing
done they are trying to do.
@triciacervenan 35
36. Tip #3
If you have to provide an alternate
“easier” way to do something, take
a look at your app structure. The
user may benefit from a revision
there instead.
@triciacervenan 36
38. 1
1
2
2
1 Main Action Bar
1
2 Top Bar/Tab Bar
2
3 Bottom Bar
3
3
3
@triciacervenan 38
39. 1
1 Main Action Bar
A
A C
C
B
B D
D E
E
A. Up button
B. Branding
C. App section navigation
D. Active app section’s options
E. Active app section’s options overflow
@triciacervenan 39
40. Tip #4
Don’t use an up button on the root
navigation view.
@triciacervenan 40
41. Tip #5
Google got rid of the menu button for
a reason. Don’t hide your navigation
in another version of a menu.
@triciacervenan 41
43. Tip #7
The action bar icons are not the
place to be creative. Use common,
standard, easy to understand icons
to indicate what the action is.
@triciacervenan 43
44. 2
2 Tab Bars
A
A
B
B
A. Fixed Tab Bar
B. Scrollable Tab Bar
@triciacervenan 44
45. Tip #8
Fixed tab bars do not scroll. Only use
them if you have two or three tabs.
@triciacervenan 45
46. Tip #9
Tabs should be used to group like
things together, not as your main
navigation.
Exception: Your app truly has only one section.
@triciacervenan 46
47. 3
3 Bottom Bar
A
A
B
B
A. Icons for view specific options
B. Overflow icon
@triciacervenan 47
48. Tip #10
Only use the bottom bar if you are
using it as a contextual bar. Section
options stay in the main action bar.
@triciacervenan 48
51. Tip #11
Don’t forget about your view
transitions. Make it obvious to your
user that views with contextual
action bars are different.
@triciacervenan 51
55. Tip #12
You need to constantly and
consistently give your user feedback
so they know what they did right and
what they did wrong, even if the
feedback only appears for a second.
@triciacervenan 55
57. Tip #13
Only provide landscape for an app that
will truly benefit from the size and
shape of that screen orientation.
@triciacervenan 57
58. Tip #14
Your average user probably bought
their smartphone for Facebook, to
take good photos, and text with a full
keyboard. Your app will be used as
much as it is memorable.
@triciacervenan 58
61. Tip #17
Be nice to your UX people and
product owners. They may change
their minds a lot, but its only
because they want what’s best for
the user.
@triciacervenan 61