Originally written based on a 2012 AnswerLab research. While the technology has evolved, the core lesson remains: behavioral context matters more than device specs. This post captures early insights that still inform how I think about cross-platform design today.
Five Lessons for Creating Great Tablet Experiences
Originally presented by Brennan Browne, AnswerLab (2012). Reflections from 2019.
When the iPad launched, it forced us to rethink what we thought we knew about device hierarchies. Tablets weren’t just bigger phones or smaller laptops. They carved out their own behavioral territory, and early research from AnswerLab revealed patterns that still inform how we think about cross-platform design today.
Three behavioral shifts that mattered:
1. Tablets replaced computer time, not phone time
Users weren’t abandoning their phones. They were trading desktop sessions for tablet time because tablets offered something desktops couldn’t: ambient computing. You could move through your home, sit with family, work from the patio. The device traveled with you without demanding the constant attention a phone requires.
The distinction wasn’t mobile vs. desktop. It was portable vs. stationary. Tablets became the “lean back” device, while phones remained “glance and go.”
2. Tablets became shared devices in single-user ecosystems
Unlike phones (deeply personal) or desktops (often stationary and solo), tablets were passed around. Families shared them. The problem? iOS didn’t support multiple user profiles. Apps like Facebook had to build user-switching into their own interfaces to accommodate this reality.
This created new design tensions: persistent login was convenient but risky. People trusted desktops with financial tasks but hesitated on tablets because they were easier to lose and harder to secure when shared. Few users set lock codes. The technology assumed individual ownership, but behavior told a different story.
3. Apps vs. web: Immersion won over habit
Most users defaulted to mobile Safari out of habit. But when they discovered well-designed native apps, the experience gap became obvious. Apps like Amazon and ESPN offered cleaner interfaces, richer interactions, and a sense of commitment. “When I’m in the NPR app, I’m in the NPR world,” one participant said.
But half-built experiences broke trust. Apps that punted users to the web for key tasks (like Target’s “view description” button) felt incomplete. Users would rather stay in Safari than toggle between contexts.
Interestingly, many users didn’t realize they were using blown-up iPhone apps on their iPads. They settled for degraded experiences without knowing a proper iPad version existed. Discovery and education were design problems, not just technical ones.
The five lessons (still relevant):
1. Treat tablets like small laptops, not big phones. Context of use matters more than screen size. Tablets invite longer sessions, richer content, and more complex interactions than phones allow.
2. Optimize for full-web experiences. If users default to Safari, your responsive web experience better be exceptional. Don’t assume everyone will download your app.
3. Prioritize content over context. Tablets are immersive devices. Users expect rich, complete content, not stripped-down summaries. Give them depth.
4. Design for shared use. Build lightweight login flows. Make switching accounts frictionless. Communicate security clearly. Amazon’s model worked: browse freely, authenticate at checkout.
5. Address security perceptions explicitly. People were (and still are) adjusting to always-on, always-authenticated app ecosystems. Make security visible and understandable, especially for sensitive tasks.
What’s changed since 2012:
Tablets have matured into productivity tools with keyboard support, multitasking, and desktop-class browsers. iPadOS now supports multiple users (kind of). But the core insight remains: device context shapes behavior more than form factor alone.
The lesson for designers: Don’t design for screen sizes. Design for contexts, postures, and the social dynamics of how devices actually get used.