Summary: Mobile devices now generate the majority of global web traffic and have become impossible to ignore even in B2B software. And yet, in many companies, requirements, design decisions, and testing are still primarily viewed through a desktop lens, even though awareness of mobile’s importance is clearly there.
Mobile-first has been considered a best practice in software development for years. And yet, many digital products are still primarily conceived for desktop use in day-to-day work. Mobile devices now generate the majority of global web traffic. Depending on the source, the mobile share is around 60 percent or even higher. I have personally seen companies with more than 70% mobile visitors spend a long time discussing a desktop-only feature and its priority before mobile users were even mentioned.
“We’ll do mobile-first in the second step.”
To be fair, these statistics mostly refer to consumer-facing products. But even in the B2B world, I keep seeing mobile usage severely underestimated or ignored, even though smartphones and similar devices are becoming increasingly important for secondary use cases there as well. If you are not careful, you can quickly be overtaken by competitors who have long understood the value of mobile.
So why does the mobile-first approach still feel so difficult in practice, even though we all do more and more on our phones ourselves and should really know better?
Desktop is our working mode
The most important reason is less technical than psychological: most people who build, design, or commission software work primarily on desktop themselves. Designs are created on large screens. Presentations happen on projectors or conference room displays, and developers code on multi-monitor setups in 4K resolution.
Secondary tasks such as reading emails, logging work hours, or checking server status pages often happen on mobile, but they rarely play a role during product development. Even smartphone use in private life is quickly forgotten in a work context.
We test where we build
The same pattern appears in testing. Many developers and product owners test their application mainly in the browser on desktop. Even when responsive design is considered, the final check often happens only at the end through device simulation in browser devtools.
At that point, teams are often just doing damage control, and real usage situations are easy to miss: small touch targets, hidden content, slow connections, or one-handed thumb interaction.
Desktop design is more comfortable
Another reason many teams unconsciously work desktop-first: designing for large screens is simply easier.
A desktop screen offers plenty of space. Additional information, more buttons, or complex navigation can be accommodated without much trouble. When there is uncertainty, teams often just add one more element. The available space forgives a lot of decisions.
That approach does not work on a smartphone. Limited space forces clear prioritization. What is the most important task? Which content is actually needed? Those are exactly the questions that make mobile-first more demanding, but also more valuable. Designing for small screens first forces you to focus on what matters early on. The resulting interfaces are often clearer, easier to understand, and more focused.
Too often, these difficult decisions are avoided at first. That tends to backfire later during implementation: instead of questioning the concept, teams look for visual workarounds to somehow squeeze already-defined features onto a small screen.
Mobile-first does not mean mobile-only
A common misunderstanding is to equate mobile-first with mobile-only.
Mobile-first does not mean neglecting desktop users. It simply means designing the core functionality first for the smallest and most constrained context of use. That is exactly why the approach still makes sense even when the majority of users later work on desktop.
How to put mobile-first into practice
A real cultural shift starts with small habits, not with big announcements in annual presentations.
1. Regularly shrink the browser window
It is surprising how often I notice that this quick way of simulating a mobile view is not widely known outside development teams: deliberately reducing the browser window to smartphone width. Many usability problems become visible immediately.
2. Use a dedicated mobile-sized browser
A separate browser with a permanently small window size or with device simulation enabled helps you keep a constant eye on mobile views. It’s a good idea to install a browser dedicated solely to this task and keep it separate from your main browser. This has the added benefit of allowing you to test multiple browsers simultaneously to check for compatibility.
3. Always keep a real test device nearby
Nothing replaces using a real smartphone. A dedicated test device on your desk makes it much more likely that features will be checked regularly under real conditions. If you develop locally, you can usually open the application directly on the smartphone via the development machine’s IP address, as long as both devices are on the same network.
4. Get mobile designs approved before designing desktop
As a designer, mobile focus can be enforced quite well by deliberately not designing desktop views at first. That removes the easy fallback and forces the important conceptual questions to be answered early.
Conclusion
Today, the problem is rarely a lack of awareness around mobile-first. Most teams know that a large share of web traffic comes from mobile devices and that mobile use has long been part of everyday life.
The real challenge is consistent execution. Desktop-first is simply tempting in daily work: requirements are written on laptops, designs are created on large screens, applications are tested on desktop, and meetings happen in front of large displays. That causes desktop to keep slipping back into the role of the default, often without anyone noticing.
Even in 2026, mobile-first is far more than just a buzzword. The approach helps prioritize content and functionality consistently, reduce complexity, and focus on what truly matters. In the end, that benefits not only smartphone users, but desktop users as well.
Cover photo by Pavlo Talpa on Unsplash.