The document discusses designing and developing universal phone and tablet apps. It provides tips for increasing reuse between phone and tablet versions to reduce costs. Specifically, it recommends (1) creating a unique first screen for tablets while reusing components via popovers and modals, (2) developing a single universal app instead of separate phone and tablet apps, and (3) reusing business logic, storyboards, and autolayout to design flexible views instead of hardcoding layouts. By planning for reuse from the start, the overall cost of adding a tablet version can be reduced to around 20% more than a phone-only app.
You Can’t Ignore the Tablet-Designing & Developing Universal Apps for Phones and Tablets-Lou Miranda
1. You Can’t Ignore the Tablet:
Designing & Developing Universal
Phone & Tablet Apps
Lou Miranda
Mobility Practice Lead, Magenic
@TheNewLou
LouMiranda.com
2. My Devices and Me
iPhone 5S, iPad Air, Retina iPad mini, iPod touch, Samsung
Galaxy Player, Nexus 7, Nokia Lumia 521, Surface RT
iPhone OS 2.0, iOS 3.0-7.1
Android 1.6-4.4
PhoneGap, Titanium, Xamarin
DOS, Windows 3.0+, OS/2, Web, J2EE:
developer & architect for 20 years
Master of Science in Molecular Biology
3. 1. Do I need to have a tablet
version of my app?
2. Is it going to double the
cost of my phone app?
4. What You’ll Learn
Product Owner:
Increase user engagement & keep
costs in check
UX Designer:
Think about tablet design &
pattern reuse
Developer:
Techniques for reusing code and
components
Techniques apply to iOS, Android,
and soon Windows[Phone] 8.1
7. Discoverability
Search for an iPhone-only
app on the App Store on an
iPad
Not Found—it's invisible
User must specifically select
"iPhone Only" from the menu
Your iPhone-only app misses
the opportunity for easy
discoverability
17. Text
Worst & Best Practices
Storyboards, embedded views, Autolayout, phone vs.
tablet idioms, fragments, one model to save to cloud
18. Creating a Tablet App
Do not stretch a phone app
Waste of white space
User gets no value
Do create a unique first
screen
Use the space
But don't fill it up with junk
19. Packaging a Tablet App
Do not create 2 separate
apps
Extra download for user
2x the provisioning,
testing, deployment, &
maintenance
Do create a universal app
One binary to rule them all
20. Architecting Your App
Do not have different
data models
Don't want different
data file formats when
cloud syncing
Do reuse business logic
Model-View-Controller
21. UX Meets Code
Do not create views
anew
Don't reinvent the
wheel
Less coding, testing
Do reuse Storyboards
22. Reuse Flexibility
Do not hard code layouts
What about 1920x1080
iPhone 6? Or iPad Pro?
Do use Autolayout
Repurposing views in
popovers or modals
New devices
23. Text
What Did We Learn?
Reduce costs by planning for reuse
from Day 1
25. Learn from Other Apps
Good: Pages App
Don't add clutter
Popovers & modals
Bad: WordPress & Twitter
Giant phone
Misuse controls
Too different
26. Worst & Best Practices
Do not stretch a phone app;
Do create a unique first screen.
Do not create 2 separate apps;
Do create a universal app
Do not have different data
models (cloud sync);
Do reuse business logic
Do not create views anew;
Do reuse Storyboards
Do not hard code layouts;
Do use Autolayout
27. Does Adding a Tablet Version
Double the Cost of an App?
Think about Total Project
Costs
UX Reuse
Code & Resource Reuse
QA Reuse
Deployment &
Maintenance Reuse
Only adds about 20% to cost
2x$?!
28. You Can’t Ignore the Tablet:
Designing & Developing Universal
Phone & Tablet Apps
Lou Miranda
Mobility Practice Lead, Magenic
@TheNewLou
LouMiranda.com
Questions?