Moving beyond screen-size thinking to designing for where, when, and why someone is using your product.
The Limits of Mobile-First
Mobile-first design was a necessary corrective. When it emerged in the early 2010s, teams were building desktop experiences and then awkwardly cramming them onto small screens. Starting with the smallest screen forced better prioritization and simpler interactions. It was the right framework for its time.
But the world has changed. People now move fluidly between devices throughout the day. They start a task on their phone, continue it on a laptop, and finish it on a tablet. They use the same product in completely different contexts: quickly on a phone while commuting, deeply on a desktop while working, casually on a tablet while on the couch.
Mobile-first addressed screen size. But screen size was never really the point. The point was always context — the circumstances in which someone is using your product. And context is far more nuanced than “big screen” versus “small screen.”
What Context Actually Means
Context is the combination of where someone is, what they’re trying to accomplish, how much time and attention they have, and what device they happen to be using. A person checking a project management tool on their phone might be in one of several completely different contexts: quickly checking a notification while walking, doing a focused review during a commute, or demonstrating something to a colleague. Each context implies different design needs, and all three happen on the same device.
Similarly, someone on a desktop might be doing deep focused work, or they might be in a meeting quickly pulling up information while half-listening. Same screen size, completely different contexts.
When we design for screen size, we make assumptions about context that are often wrong. We assume small screens mean quick, simple tasks. We assume large screens mean deep, complex work. But people use phones for hours of focused reading and use desktops for 10-second lookups. Screen size is a poor proxy for intent.
Designing for Context
Context-first design starts with understanding the core scenarios in which your product is used, regardless of device. Map out the key use cases: what are the three or four primary things people come to your product to do? For each, consider the range of contexts in which it might happen.
Then design experiences that adapt to intent, not just viewport width. A responsive layout is the bare minimum. What you really want is an experience that supports quick interactions when the user is in a hurry AND deep engagement when they have time — on any device.
This often means building multiple entry points to the same content. A dashboard that shows summary metrics for the quick-check context and provides drill-down paths for the deep-dive context. A feed that supports both skimming and careful reading. Navigation that works for both “I know exactly where I’m going” and “I’m exploring.”
It also means being smarter about defaults and surfacing. If your analytics show that most phone users primarily check notifications and status updates, make those the most prominent elements of the mobile experience. If desktop users spend most of their time creating and editing, optimize the desktop experience for those workflows. This isn’t about making the mobile version simpler — it’s about making every version more relevant.
Cross-Device Continuity
Perhaps the most important implication of context-first thinking is cross-device continuity. If users move between devices throughout the day, the transitions between those devices should be seamless.
This means syncing state in real time. It means designing for handoff moments — the point where a user switches from phone to laptop or vice versa. It means ensuring that the mental model of your product is consistent across contexts, even if the specific interface differs.
The products that will win the next decade aren’t the ones with the best mobile experience or the best desktop experience. They’re the ones that provide the best experience for the way people actually use technology: fluidly, across contexts, throughout the day.