Final Agile Forum

Practical Agile
Mobile design
and Android 4.0
Target
May Forum
By
Adi Berda
Lara Korik
Yotam Ben Dror
Date
13 May 2013
2013 Practical Agile Mobile design
May Forum:
Practical Agile Mobile design.
and Android 4.0
Thursday, May 23, 13

v
Agile Mobile Design Forum
GregNudelman
Greg Nudelman is the author of Android Design Patterns: Interaction
Design Solutions for Developers (Wiley, 2013) and a co-author of the
Smashing Mobile Book. He blogs about Android design
at AndroidDesignBook.com where Greg hosts monthly free Agile
Android Design Masterclass.
For 12 years, Greg worked with today’s top Fortune 500 companies,
non-profits, and startups: eBay, WebEx, Wells Fargo, IBM, Groupon,
Associated Press, US Patent Office, and many others.
Greg authored over 30 industry articles on mobile and tablet design
and design strategy for leading industry magazines: Smashing
Magazine, Boxes and Arrows, JavaWorld, ASP.NET Pro, UXmatters
and UXMagazine.

v
AgileDesign

v
AgileDesign
Trick #1:
Replace Kick Off Meeting
with a
Kick Off Design Workshop

v
AgileDesign
Trick #1:
Replace Kick Off Meeting
with a
Kick Off Design Workshop
Trick #2:
Replace Usability Testing
with a
RITE Using PostIt Notes

v
Workshop
1) Context
2) Goals
3) Personas
4) Vision Storyboard

v
Workshop Outline
1) Draw a storyboard
2) Convert it to initial wireframes
3) Apply X-Platform UX Framework
4) Re-draw wireframes
5) Apply UX Design Patterns
6) Re-draw wireframes
7) Practice user testing with Post-Its
Workshop

v
Storyboarding:
1) Establish a strong sense of place
2) Don’t use more than 6 sticky notes (try to)
3) Don’t spent too much time
4) You can use stick ﬁgures and detailed objects
Workshop

v
Wireframing
1) Draw on post-its
2) Don’t try to make it too accurate
3) Separate keyboard

v
RITEstudyvsUsabilitytesting

v
Rapid
Iterative
Testand
Evaluation

v
UsabilityTest
1) 8-10 participants
2) fairly elaborate prototype
3) pre-deﬁned tasks
4) laboratory setting
5) minimal prototype changes during the study
6 ) at the end of the study a usability report is produced
outlining issues and recommendations.

v
UsabilityTest
1) 8-10 participants
2) fairly elaborate prototype
3) pre-deﬁned tasks
4) laboratory setting
5) minimal prototype changes during the study
6 ) at the end of the study a usability report is produced
outlining issues and recommendations.
RITEstudy
1) 9-12 participants in 3-4 rounds (3 people per round).
2) allowing to update the prototype and ﬁx the issues
discovered during the previous day’s testing
3) simplest possible mobile prototype, usually paper or linked
HTML

v
So.. RITE study is just like 3-4 smaller usability testing?

v
Doesn’t it make sense that mobile teams should update the
existing user-centered methodologies to meet the demands
of this new platform?

v
#1: Mobile usability tests encourage project managers to
treat user-testing as something to check-off, not lead the
design process.

v
#2: Mobile usability test prototypes are often too rigid for
demands of mobile.

v
#3: Mobile usability tests are focused on reports, not
solutions.

v
CreativeVision
Google focused the design principles of Android 4.0
around five overarching goals, which applies to the core
apps, as well as to the system at large. As you design apps
to work with Android, consider these goals:
KeyAndroid4.0DesignPrinciples
“ A M a t u r e d A n d r o i d ”

v
Google focused the design principles of Android 4.0 around five
desired goals, which applies to the core apps, as well as to the
system at large. As you design apps to work with Android, consider
these goals:

v
RightSizefor
EveryDevice
MobileSpace
Unbound
ThinkGlobally
ActLocally
TapAnywhereWelcometoFlatland
Google focused the design principles of Android 4.0 around five
desired goals, which applies to the core apps, as well as to the
system at large. As you design apps to work with Android, consider
these goals:

v
WelcometoFlatland Semi-transparent, greyscale, almost wire-framy.
Sometimes, can be a challenge for users (how people know where to tap?)
On the other hand, opens a lot of opportunities.
I’m not a physical object, I’m a pure digital product.

v
Messagingapps:iOSvs.Android4.0KeyAndroid4.0DesignPrinciples

v
Semi-transparentmenusofAndroid4.0KeyAndroid4.0DesignPrinciples

v
Windowsmobilevs.Android4.0KeyAndroid4.0DesignPrinciples

v
TapAnywhere Everything on the screen is a touch target

v
Android4.0vs.iOStablerowsKeyAndroid4.0DesignPrinciples

v
Android“Tap-worthyAreas”vs.
iOSbeveledbuttons

v
RightSizeforEveryDevice

v
LargerdeviceshavemorebuttonsKeyAndroid4.0DesignPrinciples

v
Rotatingadevicemeansyouloseor
gainoptions

v
Rotatingadevicemeansyouloseor
gainoptions
LayoutConsiderationsforSplitActionBars

v
MobileSpaceUnbound

v
MobileSpaceUnboundKeyAndroid4.0DesignPrinciples

v
HoloEverywhereKeyAndroid4.0DesignPrinciples
Gmail in Holo Light.Settings in Holo Dark
Talk in Holo Light with
dark action bar

v
ThinkGlobally,ActLocally

v
ThinkGlobally,ActLocallyKeyAndroid4.0DesignPrinciples

v
S u m m a r y

v
PatternDesign
“Take any form you choose and repeat it at regular intervals
and, just as repetitive sounds produce rhythm or cadence,
you have pattern. However, the use of pattern in design is no
haphazard matter, but a disciplined activity in which the artist
must impose a pleasing order and structure on the whole to
achieve an aesthetically satisfying end product”
Lewis F. Day

v
SPRINGBOARD/LIST
Thingsyouhave/thingstodo
Navigation
Orientation

v
TAPAHEAD
Typingavoidance
Slowerbandwidth
Betterexperience
Popularkeywords

v
GROUPTHESUGGESTEDOPTION
Organized

v
SEARCHFROMTHEACTIONBAR

v
MULTIPLYSEARCH

v
SEARCHRESULTS

v
SEARCHRESULTS
Information
Multipleviewoptions

v
ACTIONOVERFLOW

v
DASHBOARD

Practical Agile
Mobile design
Target
May Forum
By
Adi Berda
Lara Korik
Yotam Ben Dror
Date
13 May 2013
2013 Practical Agile Mobile design
Thanks!

Final Agile Forum

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Final Agile Forum (20)

More from Designit (16)

Recently uploaded (20)

Final Agile Forum