There are a number of options when going mobile, and it's not slowing down. Why choose one over the other? What are the strengths and pitfalls? What's right for your customers and users? We'll go over each option, with examples of how you can come to the right strategy around your mobile offerings.
33. CONTEXT
I’m at home I’m on the road I’m at work
When you’re at home your usage could be different from
when you’re on the road, or at work. Or as research
shows - in some cases, like shopping - you could be
browsing anywhere and expect the same experience.
34.
35.
36.
37.
38. *COUCHING
A number of people are reaching for their phone instead of
going to their desks, or using their laptops (or even tablets!)
when at home on the couch. Where before, we may have made
a specific mobile version, with specific mobile tasks or
content, today phones are good enough, and many times
people expect the same content no matter where they are or
what device they’re using.
40. How do you
create feature
parity across
devices?
41. *SNACKING
Remember before smartphones? Waiting in line, waiting for a
meeting to start, waiting to pick up our kids, in a drive-thru? Now
this is a prime opportunity for short bursts of online activity. I need
to pay a bill. What’s on TV tonight? Where are my friends? Does the
local store have that dress on sale today? I’m shopping for new
insurance. All happening on-the-go, wherever you have the time.
42. How do you
create content
that can be
consumed
quickly?
43. Questions to ask?
Does your experience need to work in
different contexts?
A User’s Location? Time of day? Different devices?
44. “Tell me about how you use your devices
at different times of the day?”
Morning Afternoon Night
45. “Tell me about how you use your devices
at different times of the day?”
Morning Afternoon Night
67. CONTENT
Will your content scale to mobile? Do you have legacy
content you need to reformat or even rethink? Are
your images legible at smaller sizes, are your videos
compressed well enough, are your workflows able to
move to a smaller screen?
76. CONCEPT
What is the best way to create usable, enjoyable, fast
experiences for your users or customers? Do you need
new services? Does it make sense for all your features?
Do you need new mobile specific features?
Are your features, UI, workflows ready for mobile?
77.
78.
79.
80.
81.
82.
83. “Agile methods like Scrum and
XP both rely on a close and
collaborative relationship and
continual interaction with the
customer – the people who are
paying for the software and who
are going to use the system.”
2001
http://swreflections.blogspot.com/2012/02/agiles-customer-problem.html
102. I’m ready.
What’s next?
■ Do I go native?
■ What about Hybrid solutions?
■ Can I just go web?
103. NATIVE.
Why Native?
■ Most fluid/fast experience
■ Easier to move to new iOS versions
■ Not dependent on 3rd party APIs
■ More likely to get App Store attention
■ Can use new phone features faster
104. HYBRID.
Why Hybrid?
■ Less burden on native resources
■ More reuse across properties
■ Use native where it makes sense / use web
where it makes sense
■ Reuse some current skill-sets
105. HYBRID CAN MEAN…
■ Written in JS, but compiled to native Android & iOS
(ex. titanium)
■ Written in C#, but compiled to native Android & iOS
(ex. xamarin)
■ Written in HTML/JS but wrapped in native, with some
hooks to native functionality (ex. phonegap)
■ Written in native iOS and Android, but with some
screens or flows rendered in HTML (ex. using webview)
106. Native Component
Native Component
Web Content
(webview)
Native Component
“…we doubled down on
native navigation, while
reaffirming our webview-core
architecture. In the jump to
our 3 [Generation] app, we’re
taking our productivity spoils
and spending them where
they can make a difference.”
https://signalvnoise.com/posts/3743-hybrid-sweet-spot-native-navigation-web-content
107. WEB.
Why Web?
■ Reuse your current base of web developers
■ Have a product reason to have the same
experience on a .com
■ Already have a web property
■ Accessed from a URL
■ Reuse across web / app
■ Responsive or Adaptive
109. RESPONSIVE
Responsive is where you have all the same features of
your current site but via breakpoints it “responds”
down to different devices.
Why Responsive?
■ Customers expect the same content and features
■ One set of templates to maintain
■ Works across a number of devices
110. OUR RESPONSIVE APPROACH
OUR APPROACH
■ The biggest mental shift in design/dev for responsive is learning to think fluidly.
■ The question "How many pixels wide?" is now a red herring.
■ Instead, you have to think proportionally, and in percentages.
OUR TOOLS
■ Sass (and Compass) have been invaluable. / http://sass-lang.com / http://compass-style.org
■ It allows you to have small, topical (S)CSS files, and combine them into larger files that (don't)
have media queries.
■ This approach has allowed us to support older versions of Internet Explorer (prior to IE9) as
well as modern browsers that do understand media queries.
■ Also, just for front-end templating, Middleman (or Serve) is helpful. It handles Sass
compilation, as well as JavaScript minification and concatenation. / http://
middlemanapp.com / http://get-serve.com
OUR STACK
■ Irrelevant. Except that Sass (and Compass) require Ruby to compile.
■ Any server-side stack should be able to support a responsive approach.
111. RESPONSIVE IS BECOMING MORE MATURE
A number of good, solid frameworks (if needed)
http://getbootstrap.com/
http://foundation.zurb.com/
A number of good 3rd party solutions (if needed)
http://www.highcharts.com/
* We tend NOT to use large frameworks,
but lighter smaller components as
needed.
112. Google: Bad User Experience For Mobile Users
May Lead To Ranking Issues
“Because at Google we are aiming to provide a
great user experience on any device, we're making
a big push to ensure the search results we deliver
reflect this principle.”
https://www.seroundtable.com/google-user-experience-ranking-19278.html
114. ADAPTIVE
Adaptive is where you have custom templates per
device type you want to target. This works best when
you have specific features or interactions you want
across different devices.
Why Adaptive?
■ Custom experience per device / time / location
■ You don’t have the frontend skill-set for Responsive
■ You already have a m.dot site
115. ADAPTIVE
How do I know what our user’s needs are,
and if they’re different?
Qualitative Quantitative
116. ADAPTIVE
ex. “Via observation we found out that your users will
only use alerts and limited content when on the go.”
ex. “Via data we’ve found that tablet usage increases
200% after work hours, we need to make sure all our
features work well on tablets.”
134. Be thoughtful about your breakpoints and how
it works with your content.
1 2
135. Tools
OUR TOOLS
■ Sass (and Compass) have been invaluable. / http://sass-lang.com / http://compass-style.org
■ It allows you to have small, topical (S)CSS files, and combine them into larger files that (don't)
have media queries.
■ This approach has allowed us to support older versions of Internet Explorer (prior to IE9) as
well as modern browsers that do understand media queries.
■ Also, just for front-end templating, Middleman (or Serve) is helpful. It handles Sass
compilation, as well as JavaScript minification and concatenation. / http://
middlemanapp.com / http://get-serve.com