Mobile-First Is Table Stakes — What Comes After
Mobile-first design is no longer a differentiator — it's a baseline requirement. The question now is what design thinking should replace it as the
When mobile-first design thinking emerged as a discipline in the early 2010s, it was a genuinely disruptive reorientation: start with the constraints of the smallest screen and the most demanding network conditions, and scale up from there. The discipline it imposed produced better products.
A decade later, mobile-first is table stakes. Every serious product team designs mobile-first. The question is what the next reorientation looks like.
Context-First Design
The successor to mobile-first, I'd argue, is context-first: designing not for a device type, but for the specific context in which a product will be used. On the An Post Money project, context-first thinking meant distinguishing between the 'check my balance on the way to the shop' context (fast, glanceable, single-purpose) and the 'review my spending this month' context (deliberate, analytical, multi-step).
On the ESB RTV Platform, the primary context was an operational control room — large monitors, multiple screens, a high-pressure environment where decisions needed to be made in seconds. Mobile-first thinking would have been actively counterproductive; the design needed to leverage the screen real estate and information density that a large display provided.
Offline-First Design
The TCD student app introduced me to a design constraint that's underweighted in most product thinking: offline reliability. University campuses have notoriously patchy network coverage in lecture halls, underground labs, and older buildings. A student who can't see their timetable because the app requires a network connection is a student with a broken experience.
Offline-first design — caching critical data locally, designing graceful degradation for network-dependent features, and being explicit with users about what requires connectivity — produces significantly more reliable experiences in the real-world environments where most mobile products are actually used.
Voice and Ambient Computing
The next frontier in product design is ambient computing — interfaces that don't require a device to be held, looked at, or interacted with deliberately. Voice interfaces, smart displays, and wearable computing are no longer speculative; they're in use at scale.
What this means for product design practice is a further shift away from visual hierarchy and interaction pattern thinking, towards conversational flow and information architecture that works across modalities. The product teams that are building these competencies now will be significantly better positioned for the next decade of product design.
