Every device that can access your site matters. Desktop users, tablet users, and mobile users all have different needs, different contexts, and different reasons for visiting. I build responsive sites that treat all screen sizes with equal importance Source 2 .
Why equal priority matters
"Mobile-first" suggests mobile is most important. But that is not how people use websites:
- Different devices, different contexts: People use desktops for research, tablets for browsing, phones for quick checks. Each context matters.
- Different users, different devices: Some people prefer desktop, some prefer mobile. Your site should work well for both.
- Same user, different devices: People might research on desktop, then check details on mobile later. The experience should be consistent.
- All devices need performance: Fast sites matter on every device, not just mobile Source 1 .
How I approach cross-device design
Instead of starting with one device and adapting, I design and build for all devices together:
- Design for all screen sizes: Layouts, typography, and interactions work well on desktop, tablet, and mobile from the start.
- Test on real devices: Not just browser resizing, but actual phones, tablets, and desktops.
- Performance for all: Fast-loading pages, optimised images, and efficient code that works well on every device.
- Accessibility across devices: Keyboard navigation, screen readers, and touch interactions all work properly.
What you get
- Responsive layouts: Sites that adapt smoothly to any screen size, without feeling like a mobile site stretched to desktop or a desktop site squeezed to mobile.
- Consistent experience: Same content, same functionality, same quality on every device.
- Performance everywhere: Fast-loading pages on desktop, tablet, and mobile Source 1 .
- Proper testing: Sites tested on real devices, not just browser developer tools.
Why not mobile-first?
Mobile-first puts mobile in people's heads as the most important device. But:
- It creates hierarchy: If mobile is "first", other devices feel secondary.
- It limits design: Starting with mobile constraints can limit what works well on larger screens.
- It misses context: Desktop users have different needs than mobile users. Both matter equally.
Cross-device design treats all devices as equally important. Desktop, tablet, and mobile all get the same attention, the same quality, and the same performance.
Who this suits
- Businesses whose users access sites on different devices for different reasons.
- Sites where desktop users research and mobile users take action (or vice versa).
- Any site where you want consistent quality across all devices.
How work runs
- Design for all devices: Layouts and interactions designed to work well on desktop, tablet, and mobile.
- Build responsively: Code that adapts smoothly to any screen size.
- Test on real devices: Testing on actual phones, tablets, and desktops, not just browser resizing.
- Optimise for all: Performance, accessibility, and usability that works well on every device.
For more on responsive design, see responsive design: why all devices matter equally.
Sources
- [1] web.dev. Web Vitals. Back to article
- [2] web.dev. Why does speed matter?. Back to article
- [3] Google Search Central. Search Console. Page Experience report. Back to article