This document discusses the importance of design patterns and guidelines for Android applications. It notes that design patterns provide proven solutions to common problems, and consistency through visual cues and context helps users intuitively understand applications. While innovation is still possible, breaking guidelines requires a good reason. Patterns should only be used if they solve real problems for an application.

1. Details Matter
Getting the Android Design Patterns
Juhani Lehtimäki, Snapp Solutions Ltd

2. “Users can figure it out. What’s the problem?”
“You are just nitpicking. It’s fine.”
“You just hate <insert company you like but you think I
don’t>”

5. Design Guidelines
Design Patterns

18. A Design Pattern
=
A Proven, Good Solution to
a Common problem

19. Android Design Guidelines

20. Consistency
● Cognitive load
● Intuitiveness by learning

21. Visual cues
● Interaction
● Functionality
● Make users feel home

22. Use Context

23. So, Do All Apps Need to
Look the Same Now?

24. Innovation and the Mature
Android Platform

26. Community driven
innovation

27. Taylor Ling, June 15, 2012
http://androiduiux.com/2012/06/15/side-navigation-ui-pattern-in-android/

28. http://developer.android.com/design/patterns/navigation-drawer.html

29. Commercial innovation

33. Android UI Design Patterns

34. Action Bar

46. Up

53. Navigation Drawer

56. Nope! Try

57. :-

60. WTF is this??

61. ?

63. Don’t need it?
Don’t use it!

64. Design patterns solves a problem
if you don’t have the problem
don’t use the design pattern!

65. Tabs

73. UX design is Nitpicking for
a Good Reason

74. “This is different”
“Do I use this differently?”

75. Learn Once
Use Everywhere

76. Gestures Are Hidden
but Awesome

77. Reinventing the Wheel
vs.
Innovation

78. Break rules & guidelines only if
you have a good reason to do so

79. Cheers!
+JuhaniLehtimäki
http://www.snapp.info/
http://www.androiduipatterns.com/