2. Goals
1. Strategy - Mobile maturity opportunities
2. Execution - Types of mobile app implementation
3. Questions to ask prior to technology selection
4. Other considerations
2
6. Design Approach 1
Baseline mWeb Native AndroidNative iOS
6
Product Strategy - Accelerate
UX Tactics - Mobile Focus
Technical Implementation - Hybrid Apps – Web
Re-usable across all platforms
7. Design Approach 2
Baseline mWeb Hybrid Mixed
Android
Hybrid Mixed
iOS
Re-usable across all platforms Not re-usable
7
Product Strategy – Mobile Friendly
UX Tactics - Transform
Technical Implementation - Hybrid Apps – Mixed
8. Design Approach 3
Baseline mWeb Native AndroidNative iOS
Not re-usableRe-usable for iOS & Android Web
8
Product Strategy – Mobile First
UX Tactics – Mobile First
Technical Implementation – Native Apps
9. Other User Experience Considerations
“When people want a quick hit/lookup, they go to
the Web. When they have a recurring use, they
turn to an app.” – Luke Wroblewski
• If you decide to evolve to mobile first: browser,
iOS and Android should have different
experiences.
• http://elekslabs.com/2012/12/android-vs-ios-user-experience.html
• http://depts.washington.edu/ux/2013/04/when-designing-for-
android-forget-ios/
9
10. Discussion Points
Short Term vs. Future
1. Does your product need the smoothest UI and fastest
performance to warrant native app dev costs?
2. Do you want to the same exact experience across mobile
web experience & native apps?:
• Short Term: Yes or No | Long Term: Yes or No?
3. Do you want take advantage of annual refreshes from iOS
and Android?
• Short Term: Yes or No | Long Term: Yes or No?
10
11. Conclusions
There are many different mobile flavors to
implement.
Listen to your users, determine your product
needs, and pick appropriate tools to meet your
business and user experience goals.
11