Slides from my three-part series Designing for Multiple Devices class run on the 20th of January with General Assembly in London.
The rise in mobiles and tablets have not only changed the way we consume and interact with content, but also the way we design and what we base our design approach on.
This series of classes will cover how user expectations as well as behaviour and consumption patterns have shifted—and what that means for designing products that will be used on multiple devices. Coming out of these classes, you'll be equipped with the essential principles and tools to tackle the multiple device jungle.
Three part series: Designing for multiple devices - GA, London, 20 Jan 2014
1. 3 classes
in 1
AN EVENING OF
D!"#$%#%$ for multiple devices
20 January 2014
Anna Dahlström
www.annadahlstrom.com
annadahlstrom
2. I’& A%%'
IA & UX designer | freelance since 2011
Swedish | in London since 2006
www.flickr.com/photos/dahlstroms/4411448782
3. (#" !v!%#%$
6.00 pm P'r) 1: Understanding the multiple device landscape
Practice
7.00 pm Break
7.15 pm P'r) 2: Practicalities of multiple device projects
Practice
8.15 pm Break
8.30 pm P'r) 3: Adapting to input, orientation & the future
Practice
Q&A
4. P'r) 1: Understanding the
multiple devices landscape
Introduction & defining your mobile strategy
5. (! w*r+, we design for
has become more complex
www.flickr.com/photos/pagedooley/2121472112
6. W! -"!, )* only have to deal with
different browsers, and the fold
www.flickr.com/photos/jorgeq82/4732700819
7. T*,'. #)’" br*w"!r" AND endless numbers
of devices & screen sizes
www.flickr.com/photos/adactio/6153481666
8. I% 2009 1% of global internet traffic came from
mobiles. By the end of 2012 it had risen to 13% and by
2015 #)’" /p!0)!, )* b! 'b*v! 50%.*
* Source: www.forbes.com/sites/parmyolson/2012/12/04/5-eye-opening-stats-that-show-the-world-is-going-mobile
www.flickr.com/photos/nasamarshall/6289116940
9. A" *f Q3 2012 we passed
1 billion smartphones in use
www.flickr.com/photos/raincitystudios/95234968
10. I 1'v! ' 2*b )1') #" -%3%*w% )* &'%.
F*r !v!r. 1-&'% that enters the world, five mobile
I’devices are created.*UX designer
m a freelance IA &
* Source: http://blogs.windows.com/ie/b/ie/archive/2013/07/17/the-companion-web-the-internet-and-how-we-use-it-is-evolving.aspx
www.flickr.com/photos/hlkljgk/5764422581
www.flickr.com/photos/helga/3952984450/
11. 41% *f !&'#+" are now opened on mobile devices *
* Source: http://econsultancy.com/uk/blog/62268-41-of-email-is-now-opened-on-mobile-devices
www.flickr.com/photos/jayfresh/3388253576
12. B. )1! !%, *f 2013, mobile phones will overtake PCs
as the most common web access device worldwide*
Source: www.gartner.com/newsroom/id/2429815
Image courtesy of Shutterstock
13. The average person looks at their phone
150 )#&!" ' ,'..*
* Source: www.textually.org/textually/archives/2012/02/030229.htm
www.flickr.com/photos/jorgeq82/4732700819
14. 40% *f p!*p+! use their phone in the bathroom. *
* Source: http://www.lukew.com/ff/entry.asp?1500
www.flickr.com/photos/exlibris/2552107635
19. B!f*r! )1! 4r") #P1*%!
the mobile use case was limited
www.flickr.com/photos/frantaylor/4296536332
20. W! b-#+) separate sites
for mobile & desktop
DESKTOP
FULL WEBSITE
BESPOKE
CUT
DOWN
WEBSITE
BESPOKE
CUT
DOWN
WEBSITE
http://desktopwallpaper-s.com/19-Computers/-/Future
21. I% f'0), we still do
but we’re noticing something
www.flickr.com/photos/demandaj/7287174776
22. U"!r" /p!0) an equal & continuous
experience across devices
www.flickr.com/photos/joachim_s_mueller/7110473339
23. “ 7 *-) *f 10 smartphone and tablet users expect the
same quality of experience on all devices. ” *
* Source: www.vibrantmedia.co.uk/press/press.asp?section=press_releases&id=256
www.flickr.com/photos/pandiyan/4550066009
24. (!r! 'r! a number
of reasons for this
www.flickr.com/photos/martinteschner/4569495912
25. P!*p+! 0'rr. *-) the same tasks on
mobiles as they do on desktops
www.flickr.com/photos/philippe/2462550872
26. D!v#0!" & "!rv#0!" are getting more
advanced & optimised for complex tasks
www.flickr.com/photos/joeybones/6791201819
27. W! %* +*%$!r *w% just one device but
multiple & use them interchangeably
www.flickr.com/photos/soyproject/6066959891
28. W! w'%) )* find what we’re looking for
irrespectively of the device we use
www.flickr.com/photos/visualpunch/7351572896
29. M*b#+! 0*%)/) ≠ &*b#+! -"! 0'"!
The latter is about the task, the former about
the total sum of the user’s mobile experience
www.flickr.com/photos/icedsoul/2486885051
30. H'v#%$ "!p'r')! sites
does, for the most part, not make sense
DESKTOP
FULL WEBSITE
BESPOKE
CUT
DOWN
WEBSITE
BESPOKE
CUT
DOWN
WEBSITE
http://desktopwallpaper-s.com/19-Computers/-/Future
31. S*, w1')
should we do?
www.flickr.com/photos/tomitapio/4053123799/in/photostream
32. O-r &'#% *p)#*%" are bespoke
mobile sites, responsive sites and apps
www.flickr.com/photos/martinteschner/4569495912
33. B!"p*3! &*b#+! "#)!" have a separate url
& means maintaining different sites
DESKTOP
FULL WEBSITE
BESPOKE
CUT
DOWN
WEBSITE
BESPOKE
CUT
DOWN
WEBSITE
http://desktopwallpaper-s.com/19-Computers/-/Future
34. R!"p*%"#v! "#)!" have the same url
& is basically “one site”
FULL WEBSITE
FULL
WEBSITE
FULL
WEBSITE
http://desktopwallpaper-s.com/19-Computers/-/Future
35. App", well we all know
they come from app stores
www.flickr.com/photos/paul-r/217948368
36. H*w do we know
when to do what?
www.flickr.com/photos/tomitapio/4053123799/in/photostream
38. “T*,'.’" p*p-+'r ,!v#0!" 'r! %*) )*&*rr*w'" so
building something which works on any device is better
than building something which works on
today's devices“
- C*&b#%!, w#"! w*r," fr*& @*%!/)r'p5!+ & @)r!%)w'+)*%
www.flickr.com/photos/lastquest/1472794031
39. Tw* &'#% /0!p)#*%":
technical limitations to the CMS, or
if required for the audience
www.flickr.com/photos/st3f4n/3476036180
44. F*r )1! 4r") )#&! smartphones and tablets made up
more than one-third of total clicks on Google in Q3*
* Source: http://econsultancy.com/uk/blog/63605-us-mobile-paid-search-spend-up-66-year-on-year-stats
www.flickr.com/photos/antoniolas/4367543346
56. M'#%+. "1'r!, +#%3":
ensure your site is optimised for mobile
www.flickr.com/photos/soundslogical/4255801733
57. “ D*%’) b-#+, '% 'pp f*r )1! "'3! *f #). Focus on
the goal of your mobile initiatives, prioritize your
company’s needs, and choose a solution that can best
address these needs now and into the future.* ”
* Source: http://success.adobe.com/en/na/programs/products/digitalmarketing/offers/apr/1304-32060-2013-optimization-survey-results.html
www.flickr.com/photos/dougbelshaw/4360008898
60. N*) '" !'". '" just
doing an app for e.g. iOS or Android
www.flickr.com/photos/nrkbeta/3906687294/in/photostream
61. N!!, )* 0*%"#,!r fragmentation
across different versions &
backwards compatibility
www.flickr.com/photos/aforgrave/6168689222
62. R!+')#v! %-&b!r of active
Android devices across different versions
Source: http://developer.android.com/about/dashboards/index.html
www.flickr.com/photos/blakespot/4773693893
63. C*&p'r#"*% *f adoption rate
for iOS7, iOS6 and iOS5
Source: www.fiksu.com/iOS-7-iPhone-5s-5c-Usage-Tracker
www.flickr.com/photos/blakespot/4773693893
64. Ev!r. p+')f*r& has their own
ui guidelines that their users are used to
www.flickr.com/photos/gadl/3570118243
65. ” M*%!. "p!%) developing a pretty but limited iPhone
app only benefits [...] the few, but money spent on the
website UI would have benefitted everyone. ”
- G'r. M'r"1'++ *% ‘(! 'pp )r'p’ #% .%!) M'$8#%!
www.flickr.com/photos/dougbelshaw/4360008898
66. (!r! 'r!
different types of apps
NATIVE APPS (e.g. Instagram)
• MOST OPTIMISED USER EXPERIENCE
• ACCESS TO DEVICE CAPABILITIES & APIs
• BUT REQUIRES PLATFORM SPECIFIC CODE BASE
HYBRID (e.g. First Facebook, Basecamp)
• USE OF HTML5 & JAVASRIPT
• WRAPPER TO PROVIDE NATIVE CAPABILITIES
• FEWER “VERSIONS” TO MAINTAIN
• BUT CAN BE TIME CONSUMING TO CREATE APP LIKE INTERACTIONS
• CAN'T JUST BE WRAPPED. MUST HAVE APP LIKE FUNCTIONALITIES
68. R!"p*%"#v! "#)!" have the same url
& is basically “one site”
FULL WEBSITE
FULL
WEBSITE
FULL
WEBSITE
http://desktopwallpaper-s.com/19-Computers/-/Future
69. “ D!"#$% & ,!v!+*p&!%) "1*-+, r!"p*%, to the
user’s behaviour & environment based on screen size,
platform & orientation. [It’s]...a mix of flexible grids &
layouts, images & an intelligent use of media queries. “
- S&'"1#%$ M'$8#%!
www.flickr.com/photos/adactio/5818096043
70. (! b'03b*%! #"
your grid & breakpoints
http://foundation.zurb.com/docs/layout.php
71. C*+-&%" & $-))!r" can be
fluid or fixed, or a combination.
http://foundation.zurb.com/docs/layout.php
73. “ C*%)!%) %!!," )* b! 01*r!*$r'p1!, to
ensure the intended message is preserved on any
device and at any width “
www.flickr.com/photos/theaftershock/2811382400
- Tr!%) W'+)*%
75. I,!%)#f. '%, pr#*r#)#"! the content
across devices & orientations
Mobile
Desktop/ tablet
1
Logo
1
Logo
2
Header
4
Bath section intro
5
Ad
3
Nav
8 Store
locator
6
Types of baths
2 Header
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
76. D*%’) 2-") work with columns
but think of the narrative of the views
www.flickr.com/photos/garrettc/6260768486/
77. S* )1') #)’" 0'r!9++.
considered, like this
http://thenextweb.com/
78. M*b#+! *r ,!"3)*p 4r"),
the key is considering the content &
how it will work across devices
80. (! BRIEF
A big retail store has asked you to come up with a Easter Hunt across London
where offers and give aways are hidden at certain locations. There will only be a
certain number of items available each day & they want to be able to notify
people when an item has been found.
The site/app should support finding offers nearby, and location should be a key
The following should also be included:
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
81. 01
BESPOKE MOBILE SITE
VS. RESPONSIVE VS. AN APP
The client has come to you with the Easter hunt idea and are asking for your
advice on what they should be doing.
W1') w*-+, .*- r!0*&&!%, #% )!r&" *f &*b#+! pr!"!%0! & w1.?
A bespoke mobile site, responsive site, an app or a combination?
Consider:
HOW WOULD MOST PEOPLE ACCESS IT?
• Direct traffic vs. shared links?
WHAT DO YOU NEED IT TO DO?
• Device specific capabilities needed?
• Is offline reading/ usage required?
www.flickr.com/photos/pinkpurse/5355919491
WHAT ARE THE OBJECTIVES & PRACTICALITIES?
• The budget
• The current technical platform
• Could an app be re-used later
• The marketing value of an app
82. 02
CONTENT STACKING STRATEGY
Together the client and you have decided to go with a responsive site, which can
also form the basis for their app presence. Now it’s time to get to work.
F*r )1! 1*&! p'$! *%+. ,* ' r*-$1 "3!)01 *f w1') )1! p'$! "1*-+,
0*%)'#% & 1*w )1! 0*%)!%) "1*-+, b! pr#*r#)#"!,.
U"#%$ 0*%)!%) ")'03#%$ &!)1*,*+*$. ,!4%! 1*w )1! 0*%)!%) "1*-+,
b! pr#*r#)#"!, *% ,!"3)*p & &*b#+!.
The client’s requirements were:
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
83. D!4%! your content stacking strategy
across devices & orientations
Mobile
Desktop/ tablet
1
Logo
1
Logo
2
Header
4
Bath section intro
5
Ad
3
Nav
8 Store
locator
6
Types of baths
2 Header
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
84. D*%’) 2-") work with columns
but think of the narrative of the views
www.flickr.com/photos/garrettc/6260768486/
85. 02
CONTENT STACKING STRATEGY
Together the client and you have decided to go with a responsive site, which can
also form the basis for their app presence. Now it’s time to get to work.
F*r )1! 1*&! p'$! *%+. ,* ' r*-$1 "3!)01 *f w1') )1! p'$! "1*-+,
0*%)'#% & 1*w )1! 0*%)!%) "1*-+, b! pr#*r#)#"!,.
U"#%$ 0*%)!%) ")'03#%$ &!)1*,*+*$. ,!4%! 1*w )1! 0*%)!%) "1*-+,
b! pr#*r#)#"!, *% ,!"3)*p & &*b#+!.
The client’s requirements were:
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
86. P'r) 2: Practicalities of
multiple device projects
Common challenges, content strategy, structures,
navigation patterns, testing
87. S*&! *f )1! most common
challenges with responsive design are...
www.flickr.com/photos/helga/3952984450
88. 1. K%*w#%$ where to start...
• Define your mobile strategy
• Start sketching
• And work across disciplines
www.flickr.com/photos/pinkpurse/5355919491
89. 2. H*w &'%. versions to wireframe...
• Depends on your project, budget & team as well as who’s
building it
• Focus on identifying key templates & then the modules
that make up the views
www.flickr.com/photos/jorgeq82/4732700819
90. 3. H*w )* 'ppr*'01 visual design
• Less static designs
• Focus on modules & modularity
• Continuously prototype to test how the content behaves
www.flickr.com/photos/donsolo/2136923757
91. 4. W1') "0r!!% ";!" & which resolutions?
• Use analytics as a guidance
• Ensure it works for the most common ones
• Design as device agnostic as possible
www.flickr.com/photos/dpstyles/3448453466
92. 5. H*w )* define breakpoints
• As much possible let the content be the guide
• Use breakpoints & tweakpoints & EMS instead of px
• Consult analytics for devices to identify most important
screen sizes & ensure content displays properly for those
• If all things fail, use screen sizes for mayor layout changes
www.slideshare.net/yiibu/pragmatic-responsive-design
93. 6. H*w &'%. devices to test on
• As many as possible
• Prioritise based on your audience
• Use research & analytics for guidance
www.flickr.com/photos/nomadic_lass/5598218199
94. “ 80% *f .*-r )r'ffi0 in your analytics will often
come from 20% of devices…seems a shame not to
ensure that the site looks and works especially well on
these devices.*
Source: * Source: www.slideshare.net/yiibu/pragmatic-responsive-design
www.flickr.com/photos/adactio/6153481666
95. 7. H*w )* handle images
•
•
•
•
xxx
Images & icons should be as flexible as possible
Consider load times & page weight
Look at ways for loading smaller images first
Take the image in question into consideration
97. “ M*b#+! %'v#$')#*% should be like a good friend:
there when you need them but cool enough to give you
your space. “
* Source: http://bradfrostweb.com/blog/web/responsive-nav-patterns
www.flickr.com/photos/melodramababs/2766765248
98. Br', Fr<) has written 2 excellent posts
on Responsive navigation patterns
xxx
http://bradfrostweb.com/blog/web/responsive-nav-patterns
http://bradfrostweb.com/blog/web/complex-navigation-patterns-for-responsive-design
99. L!)’" take a closer look...
www.flickr.com/photos/suttonhoo22/2070700035
100. S#&p+! navigation patterns
1) Top nav or “do nothing”
2) The toggle
3) The left nav flyout
http://bradfrostweb.com/blog/web/responsive-nav-patterns
101. Via B
ra
d Fro
st (th
T*p %'v *r “D* %*)1#%$”
keeps the navigation at the top
ank y
ou!)
PROS
Simple to implement
Less design & development
implications
CONS
Not scalable
Potential height issues
http://skinnyties.com
102. Via B
ra
d Fro
st (th
(! )*$$+!
hides navigation items in a menu
PROS
Optimises screen use
Recognised from apps
Scalable
CONS
Possible animation
performance problems
Javascript dependent
www.smashingmagazine.com
ank y
ou!)
103. Via B
ra
d Fro
st (th
(! +!= %'v >.*-)
menu items are accessed from a tray sliding in
ank y
ou!)
PROS
Space generous
Recognised nav pattern from
apps
CONS
More advanced and doesn’t
work on all devices
Images from Barack Obama via Brad Frost
104. C*&p+/ navigation patterns
1) The multi toggle
2) Right to left
3) Skip the sub-nav
4) Priority+
5) The carousel+
http://bradfrostweb.com/blog/web/complex-navigation-patterns-for-responsive-design
105. (! &-+)# )*$$+!
nested navigation grouped under a menu
Via B
ra
d Fro
st (th
PROS
Scannable
Scalable
CONS
Animation performance
Javascript dependent
http://thenextweb.com
Barack Obama - image via Stephanie Rieger
ank y
ou!)
106. Via B
ra
d Fro
st (th
R#$1) )* +!=
the next level navigation slides in right to left
ank y
ou!)
PROS
Nice looking
Follows mobile conventions
Scalable
CONS
More complex to implement
Animation performance
www.sony.com
107. Via B
ra
d Fro
st (th
S3#p )1! "-b-%'v
next level navigation is displayed on that level
PROS
Simple
Removes complexities
around sub-navigation
CONS
Re-quires page refresh &
visit for access
http://worldwildlife.org
ank y
ou!)
108. Via B
ra
d Fro
st (th
Pr#*r#).+
shows most important & hides the rest in a menu
ank y
ou!)
PROS
Simple
Supports (supposedly) most
used)
Scalable
CONS
Hides potentially important
items
www.bbc.co.uk/sport
109. Via B
ra
d Fro
st (th
(! 0'r*-"!++
carousel for main sections, sub-nav when in focus
ank y
ou!)
PROS
Easy to navigate
Suitable for touch
CONS
Doesn’t display all parent
categories at once
Less good for non-touch
devices
Not suitable for multi-level
sub-navs
Image from Intel via Brad Frost
114. L'") b-) %*) +!'"), consider navigation
across products & keep it similar
to aid familiarity
BBC Sport - mobile site
BBC Sport - desktop
BBC Sport - app
119. B'"#0 iOS
app structure
CONSISTENT ACROSS VERSIONS
NAVIGATION BAR
Enables navigation through the app
hierarchy. Holds the back button,
controls for managing screen content &
the title of the screen.
BACK BUTTON
Should always take the user one step back from where
they came from & be descriptive.
TAB BAR
Can often be customised. Holds the main sections of the
app.
‘MORE’ TAB BAR ITEM
Used to hold & provide access to all other sections of the
app that don’t fit in the tab bar.
120. B'"#0 Android
app structure
DIFFERENT BETWEEN VERSIONS:
NAVIGATION BAR
For devices that don't have the
hardware keys. Holds 'Back', 'Home'
and 'Recents'
ACTION BAR
Holds the most important action buttons for your app (3 +
overflow menu)
UP VS. BACK BUTTON
The Up button is used to navigate up one level based on
the hierarchical structure of the site.
Back is used to navigate back one step from where you
came from & as such works in reverse chronological order.
134. Fr*& testing sketches as
paper prototypes or as clickable prototypes...
www.flickr.com/photos/grinblo/8659685975
www.flickr.com/photos/waagsociety/8888907062
137. 03
APP STRUCTURE
With a better idea of the content for the Easter Hunt campaign, work also begins
on the app. Based on the content & functionality requirements as well as what
you know, consider what would be suitable to include in the app.
F*0-"#%$ *%+. *% )1! 'pp %'v#$')#*% 1*w w*-+, .*- ")r-0)-r! )1#" #f
.*- w!r! )* ,* '% #OS 'pp & '% A%,r*#, 'pp?
Look at the Tab bar items respectively Action bar items & what would go in them
as well as the ‘More’ respectively ‘Overflow menu’.
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
138. B'"#0 iOS
app structure
CONSISTENT ACROSS VERSIONS
NAVIGATION BAR
Enables navigation through the app
hierarchy. Holds the back button,
controls for managing screen content &
the title of the screen.
BACK BUTTON
Should always take the user one step back from where
they came from & be descriptive.
TAB BAR
Can often be customised. Holds the main sections of the
app.
‘MORE’ TAB BAR ITEM
Used to hold & provide access to all other sections of the
app that don’t fit in the tab bar.
139. B'"#0 Android
app structure
DIFFERENT BETWEEN VERSIONS:
NAVIGATION BAR
For devices that don't have the
hardware keys. Holds 'Back', 'Home'
and 'Recents'
ACTION BAR
Holds the most important action buttons for your app (3 +
overflow menu)
UP VS. BACK BUTTON
The Up button is used to navigate up one level based on
the hierarchical structure of the site.
Back is used to navigate back one step from where you
came from & as such works in reverse chronological order.
140. 03
APP STRUCTURE
With a better idea of the content for the Easter Hunt campaign, work also begins
on the app. Based on the content & functionality requirements as well as what
you know, consider what would be suitable to include in the app.
F*0-"#%$ *%+. *% )1! 'pp %'v#$')#*% 1*w w*-+, .*- ")r-0)-r! )1#" #f
.*- w!r! )* ,* '% #OS 'pp & '% A%,r*#, 'pp?
Look at the Tab bar items respectively Action bar items & what would go in them
as well as the ‘More’ respectively ‘Overflow menu’.
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
141. 04
SIMPLE RESPONSIVE NAVIGATION
Now that you have a good understanding of the content and the main sections,
it’s time to tackle the navigation for the responsive site.
B'"!, *% w1') .*-’v! #,!%)#4!, "* f'r, ,!4%! 1*w )1! %'v#$')#*% w#++
w*r3 f*r ,!"3)*p '%, "&'r)p1*%! '%, /p+'#% 1*w .*- 0'&! )* #)
Consider what you need, future aspects, cross device patterns and the client’s
requirements:
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
142. Via B
ra
d Fro
st (th
T*p %'v *r “D* %*)1#%$”
keeps the navigation at the top
ank y
ou!)
PROS
Simple to implement
Less design & development
implications
CONS
Not scalable
Potential height issues
http://skinnyties.com
143. Via B
ra
d Fro
st (th
(! )*$$+!
hides navigation items in a menu
PROS
Optimises screen use
Recognised from apps
Scalable
CONS
Possible animation
performance problems
Javascript dependent
www.smashingmagazine.com
ank y
ou!)
144. Via B
ra
d Fro
st (th
(! +!= %'v >.*-)
menu items are accessed from a tray sliding in
ank y
ou!)
PROS
Space generous
Recognised nav pattern from
apps
CONS
More advanced and doesn’t
work on all devices
Images from Barack Obama via Brad Frost
145. 04
SIMPLE RESPONSIVE NAVIGATION
Now that you have a good understanding of the content and the main sections,
it’s time to tackle the navigation for the responsive site.
B'"!, *% w1') .*-’v! #,!%)#4!, "* f'r, ,!4%! 1*w )1! %'v#$')#*% w#++
w*r3 f*r ,!"3)*p '%, "&'r)p1*%! '%, /p+'#% 1*w .*- 0'&! )* #)
Consider what you need, future aspects, cross device patterns and the client’s
requirements:
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
146. 05
COMPLEX RESPONSIVE NAVIGATION
The client loves the work that you’ve done so far and other cities in the UK wants
the campaign in their city too, so it’s going UK wide.
A decision has also been made to support viewing offers and give aways by store
(e.g. Marks & Spencers) and type (e.g. restaurants, fashion, entertainment).
H*w w*-+, )1#" 01'%$! .*-r %'v#$')#*% r!0*&&!%,')#*% '%, w1.?
Define the navigation for desktop and smartphone.
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
147. (! &-+)# )*$$+!
nested navigation grouped under a menu
Via B
ra
d Fro
st (th
PROS
Scannable
Scalable
CONS
Animation performance
Javascript dependent
http://thenextweb.com
Barack Obama - image via Stephanie Rieger
ank y
ou!)
148. Via B
ra
d Fro
st (th
R#$1) )* +!=
the next level navigation slides in right to left
ank y
ou!)
PROS
Nice looking
Follows mobile conventions
Scalable
CONS
More complex to implement
Animation performance
www.sony.com
149. Via B
ra
d Fro
st (th
S3#p )1! "-b-%'v
next level navigation is displayed on that level
PROS
Simple
Removes complexities
around sub-navigation
CONS
Re-quires page refresh &
visit for access
http://worldwildlife.org
ank y
ou!)
150. Via B
ra
d Fro
st (th
Pr#*r#).+
shows most important & hides the rest in a menu
ank y
ou!)
PROS
Simple
Supports (supposedly) most
used)
Scalable
CONS
Hides potentially important
items
www.bbc.co.uk/sport
151. Via B
ra
d Fro
st (th
(! 0'r*-"!++
carousel for main sections, sub-nav when in focus
ank y
ou!)
PROS
Easy to navigate
Suitable for touch
CONS
Doesn’t display all parent
categories at once
Less good for non-touch
devices
Not suitable for multi-level
sub-navs
Image from Intel via Brad Frost
152. 05
COMPLEX RESPONSIVE NAVIGATION
The client loves the work that you’ve done so far and other cities in the UK wants
the campaign in their city too, so it’s going UK wide.
A decision has also been made to support viewing offers and give aways by store
(e.g. Marks & Spencers) and type (e.g. restaurants, fashion, entertainment).
H*w w*-+, )1#" 01'%$! .*-r %'v#$')#*% r!0*&&!%,')#*% '%, w1.?
Define the navigation for desktop and smartphone.
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
153. P'r) 3: Adapting to input,
orientations & the future
Touch across devices, device orientation, mobile context,
device agnostic design
154. “T*,'.’" p*p-+'r ,!v#0!" 'r! %*) )*&*rr*w'" so
building something which works on any device is better
than building something which works on
today's devices“
- C*&b#%!, w#"! w*r," fr*& @*%!/)r'p5!+ & @)r!%)w'+)*%
www.flickr.com/photos/lastquest/1472794031
159. “ T*-01 has landed on the desktop. “
- J<1 C+'r3
www.flickr.com/photos/patdavid/9391602153
160. ‘N!w r-+!: every desktop design has to go
finger-friendly’*
* Source: http://globalmoxie.com/blog/desktop-touch-design.shtml
www.flickr.com/photos/66327170@N07/7296381856
162. “ T*-01 "0r!!% +'p)*p "'+!" have jumped 52% in
the last quarter. 5 years from now you will not be able to
buy a Windows computer without a touch screen. ”*
* Source: http://www.lukew.com/ff/entry.asp?1750
Screenshot from www.currys.co.uk
163. W! "1*-+, consider touch across all devices
& screen sizes. Not just smartphones & tablets
www.flickr.com/photos/adactio/6153481666
165. 49% *f -"!r" hold their phone in one hand,
but how they hold it differs
www.flickr.com/photos/jorgeq82/4732700819
166. ONE HAND (R: 66% L: 33%)
O)1!r v'r#')#*%"
based on 1,333 observations
during 2 months
72%
28%
CRADLING (L: 79% R: 21%)
90%
10%
TWO HANDS
Source & images from UX Matters - www.uxmatters.com/mt/archives/2013/02/how-do-users-really-hold-mobile-devices.php
167. H*+,#%$ our devices
is not a static stage. It changes
Source & images from UX Matters - www.uxmatters.com/mt/archives/2013/02/how-do-users-really-hold-mobile-devices.php
168. “ D!"#$%#%$ f*r )*-01 means designing for
fingers, yes, but to be more specific, you’re really
designing for thumbs. ”
- J<1 C+'r3
Image courtesy of Shutterstock
171. O-r 0-rr!%) 'ppr*'01 to navigation
is based on the mouse as input
Source: Luke W - www.lukew.com/ff/entry.asp?1649
172. F*r 1.br#," we tend to
rest arms & grab bottom corners
www.flickr.com/photos/intelfreepress/6837427202
173. C*%"#,!r reach & obscuring content
& adjust navigation accordingly
From...
...towards
Source: Luke W - www.lukew.com/ff/entry.asp?1649
174. “ L**3#%$ ') the Polar interface on a laptop can be a
bit disconcerting because we’ve essentially left the
middle of the page “blank”. ”
- L-3! W
Screenshot from http://polarb.com/polls/tags/mobiledesign
175. B'"!, *% the context & use case,
posture, grip & orientation varies
www.flickr.com/photos/chicitoloco/8468592748/in/photostream
www.flickr.com/photos/edduddiee/4307943164
180. M*b#+! 0*%)/) ≠ &*b#+! -"! 0'"!
The latter is about the task, the former about
the total sum of the user’s mobile experience
www.flickr.com/photos/icedsoul/2486885051
181. (! 0*%)/) differs based on
situation, attitudes & preferences
www.flickr.com/photos/hoyvinmayvin/5873697252
182. (! "'&! 0*%)/) doesn’t
equal the same situation
www.flickr.com/photos/hoyvinmayvin/5873139941
183. O)1!r '"p!0)" to consider
for the mobile context are...
www.flickr.com/photos/icedsoul/2486885051
192. R!&!&b!r 1*w we can’t
successfully tell what devices users are using
www.flickr.com/photos/adactio/6153481666
193. (! w!b is after all about content.
Not what device we are using
Image courtesy of Shutterstock
194. “ G!) .*-r 0*%)!%) to go anywhere,
because it’s going to go everywhere. ”
- Br', Fr<)
www.flickr.com/photos/mirafoto/494444094
195. A#& )* make it more future proof
by moving away from specific devices
www.flickr.com/photos/byte/8282578241
196. U"! %')-r'+ breakpoints based on
content layout rather than focusing on devices
www.flickr.com/photos/sharynmorrow/127184319
197. L**3 ') what’s suitable for your content
& best practice for layout principles
www.flickr.com/photos/visualpunch/7351572896
198. I)’" %*) without challenges,
but challenges are meant to be overcome
Image courtesy of Shutterstock
199. “ B. ,!f'-+) the web has no optimal width, optimal
height, optimal font-size or optimal anything really. ”
- E,w'r, O’R#*r,'%
www.flickr.com/photos/nikio/3899114449
200. “ (! w!b has always been fluid; we’ve just wasted a
good number of years forcing fixed pixels onto an
inherently responsive framework. ”
- E++#*) J S)*03"
www.flickr.com/photos/soundslogical/4255801733
202. W*r3 w#)1 breakpoints & tweakpoints,
focus on content layout & EMS instead of px
www.slideshare.net/yiibu/pragmatic-responsive-design
203. (! "'&! with columns,
opt for fluid as much possible
http://foundation.zurb.com/docs/layout.php
204. (#" brings us back to
the importance of modularity
www.flickr.com/photos/donsolo/2136923757/
205. L!"" 'b*-) p'$!" & more focus on
the building blocks that makes up those views
www.flickr.com/photos/boltofblue/4418442567
206. N* &*r! is it
about beautiful page designs...
www.flickr.com/photos/miuenski/3127285991
207. ...b-) 'b*-) v#!w" that will look different
across browsers, screen sizes & devices
www.flickr.com/photos/jorgeq82/4732700819
www.flickr.com/photos/adactio/6153481666
208. (! &*r! you reuse, the less modules
there will be to design, define and develop
www.flickr.com/photos/boltofblue/4418442567
217. D!4%! your content stacking strategy
across devices & orientations
Mobile
Desktop/ tablet
1
Logo
1
Logo
2
Header
4
Bath section intro
5
Ad
3
Nav
8 Store
locator
6
Types of baths
2 Header
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
218. D!4%! display variations as well as
the elements they are made up of
Desktop/ Tablet
Desktop/ tablet
1
Logo
Mobile
Mobile
2
Header
4
Bath section intro
1
Logo
5
Ad
3
Nav
8 Store
locator
6
Types of baths
2 Header
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
219. I"*+')! !+!&!%)" that need to be able to break
out to meet your content stacking strategy
Desktop/ Tablet
Desktop/ tablet
1
Logo
Mobile
Mobile
2
Header
4
Bath section intro
1
Logo
5
Ad
3
Nav
8 Store
locator
6
Types of baths
2 Header
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
220. A,'p) )* the device & screen in question;
both order & priority as well as interactions,
how much to show & how
www.flickr.com/photos/katherinekenny
221. Desktop/ Tablet
Desktop/ tablet
1
Logo
Mobile
Mobile
2
Header
1
Logo
2 Header
L#))+! b. +#))+! you build up a module library
of defined components for your views,
across devices & orientations
4
Bath section intro
5
Ad
3
Nav
8 Store
locator
6
Types of baths
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
222. “ W#)1 )1*-"'%," and thousands of pages on the
Crayola site, it wasn’t efficient to wireframe every
single page and state. We created a system of
components that could be assembled in different
configurations to accommodate the unique content
needed for each type of page. ”
- D'%#!+ M'++
Screenshot: www.crayola.co.uk/
223. H*w w! 'ppr*'01 #) depends
on your project, budget and time frame
& if it’s being built externally
www.flickr.com/photos/75905404@N00/7126146307
224. W1') w! 0'%%*) ,* is take
a waterfall approach with responsive design
where we hand over from to the other
www.flickr.com/photos/bingisser/154452815
230. 06
MODULAR, DEVICE AGNOSTIC DESIGN
The client have asked you to look at doing their new responsive site with
breakpoints based on content rather than devices. For that we need to really
understand the content and how it’s going to flow
I,!%)#f. )1! &'#% 0*%)!%) )?!" '0r<" )1! "#)!’" p'$!" '%, "3!)01 *-)
1*w )1!. 'r! $*#%$ )* b! ,#"p+'.!, '%, ','p)!, '0r<" "0r!!% ";!".
Think about natural breakpoints and good practice for display of content as well
as how to reuse as much as possible.
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
232. D!4%! your content stacking strategy
across devices & orientations
Mobile
Desktop/ tablet
1
Logo
1
Logo
2
Header
4
Bath section intro
5
Ad
3
Nav
8 Store
locator
6
Types of baths
2 Header
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
233. D!4%! display variations as well as
the elements they are made up of
Desktop/ Tablet
Desktop/ tablet
1
Logo
Mobile
Mobile
2
Header
4
Bath section intro
1
Logo
5
Ad
3
Nav
8 Store
locator
6
Types of baths
2 Header
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
234. I"*+')! !+!&!%)" that need to be able to break
out to meet your content stacking strategy
Desktop/ Tablet
Desktop/ tablet
1
Logo
Mobile
Mobile
2
Header
4
Bath section intro
1
Logo
5
Ad
3
Nav
8 Store
locator
6
Types of baths
2 Header
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
235. A,'p) )* the device & screen in question;
both order & priority as well as interactions,
how much to show & how
www.flickr.com/photos/katherinekenny
236. Desktop/ Tablet
Desktop/ tablet
1
Logo
Mobile
Mobile
2
Header
1
Logo
2 Header
L#))+! b. +#))+! you build up a module library
of defined components for your views,
across devices & orientations
4
Bath section intro
5
Ad
3
Nav
8 Store
locator
6
Types of baths
3
Nav
4
Bath
section
intro
5
Ad
7
Related
products
6
Types of baths
9 Tools
10
Footer
7
Related products
8 Store
locator
9 Tools
10
Footer
237. 06
MODULAR, DEVICE AGNOSTIC DESIGN
The client have asked you to look at doing their new responsive site with
breakpoints based on content rather than devices. For that we need to really
understand the content and how it’s going to flow
I,!%)#f. )1! &'#% 0*%)!%) )?!" '0r<" )1! "#)!’" p'$!" '%, "3!)01 *-)
1*w )1!. 'r! $*#%$ )* b! ,#"p+'.!, '%, ','p)!, '0r<" "0r!!% ";!".
Think about natural breakpoints and good practice for display of content as well
as how to reuse as much as possible.
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
238. 07
ADAPTING TO DEVICE ORIENTATION
The client has asked you to consider how the content is going to adapt based on
device orientation, i.e. from portrait to landscape.
P#03 *%! *f .*-r p'$!" '%, ,#"0-"" 'ppr*'01!" f*r 1*w )1! 0*%)!%)
0*-+, ','p) b'"!, *% ,!v#0! *r#!%)')#*%.
Consider desktop, tablet and smartphone
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
241. (!r! 'r! three main approaches
for adapting to orientation
SCALE
RE-POSITION
REVEAL/ HIDE
242. 07
ADAPTING TO DEVICE ORIENTATION
The client has asked you to consider how the content is going to adapt based on
device orientation, i.e. from portrait to landscape.
P#03 *%! *f .*-r p'$!" '%, ,#"0-"" 'ppr*'01!" f*r 1*w )1! 0*%)!%)
0*-+, ','p) b'"!, *% ,!v#0! *r#!%)')#*%.
Consider desktop, tablet and smartphone
•
•
•
•
About page
List of offers
Product pages
Notifications
www.flickr.com/photos/pinkpurse/5355919491
•
•
•
Share (on Facebook & Twitter)
Login & registration
Overview of number of found & not found item
244. A%. "0r!!% should be
your starting point
www.flickr.com/photos/byte/8282578241
245. “ Ev!r. r!"p*%"#v! ,!"#$% pr*2!0) is also
a content strategy project. ”
- K'r!% M0Gr'%!
Image courtesy of Shutterstock
246. (!r! #" %* right way
& the following is just
one way of approaching it
www.flickr.com/photos/jtravism/2417205289
247. S)!p" f*r responsive & modular design
1. Define target audiences, goals & needs (user & business)
2. Identify key user journeys
3. Identify key pages
4. Identify the content & functional requirements for each key page
5. Across all pages identify common content module types, e.g. featured product
6. Re-visit, list & prioritise the content for each page
7. From this Identify the variations that are needed for each content module type
8. Lay out the content modules across key pages (mobile or desktop first)
9. Work through layout and content stacking strategy across devices
10. Define templates for the content module types (variations & across devices)
11. Iteratively work through your pages, test & adjust modules & variations as needed
www.flickr.com/photos/poetatum/3335900523
248. I)’" %*) 2-") about the
smaller screens but also the big ones
www.flickr.com/photos/jolives/2889944573/