For a decade, we've been told 'mobile-first' is the only way to build products. Start with mobile, scale up to desktop. Design for the smallest screen first. Mobile users are the majority. I've heard it all. And for many products, it's absolutely right. But for some products, mobile-first is a disaster.
Not every product belongs on mobile
When Mobile-First Doesn't Work
I learned this lesson painfully while building a wealth management dashboard for high-net-worth individuals. We started mobile-first because 'that's what you do.' We designed beautiful, elegant mobile screens with carefully prioritized information. We launched. Usage was abysmal.
Why? Because our users—HNIs and UHNIs managing seven-figure portfolios—don't manage their wealth on their phones. They want big screens. Multiple windows. The ability to compare three different reports side by side. Detailed charts they can actually read. A mobile screen, no matter how well designed, can't deliver that experience.
"Mobile-first works when mobility is the primary value proposition. It fails when power and complexity are what users need."
The Three Questions to Ask Before Going Mobile-First
1. What is the core task?
If the core task is quick, frequent, and contextual (check the weather, order food, book a ride), mobile makes sense. If the core task is deep, analytical, or requires sustained focus (financial analysis, complex data entry, content creation), desktop makes sense.
- Mobile-first: Tasks that take <2 minutes and happen throughout the day
- Desktop-first: Tasks that take >10 minutes and require focus
- Mobile-first: Tasks that benefit from location or camera access
- Desktop-first: Tasks that require multiple apps or documents open simultaneously
2. Where do users actually do the work?
Don't guess. Look at your analytics. When do users access your product? From what devices? For how long? We assumed our wealth management users would want mobile access 'for convenience.' The data showed they logged in from desktop, during work hours, for 20+ minute sessions. They were treating it like work, not like checking social media.
Professional tools live on professional screens
3. What is the information density requirement?
Some products require high information density. Trading platforms. Analytics dashboards. CRM systems. Code editors. These products fail on mobile not because of bad design, but because the fundamental value proposition requires seeing a lot of information at once. No amount of clever progressive disclosure or 'simplified mobile view' can fix this.
When We Rebuilt Desktop-First
After the mobile-first failure, we rebuilt the wealth management dashboard desktop-first. We designed for large screens, multiple panels, rich data visualization. We added keyboard shortcuts for power users. We made it feel like Bloomberg Terminal, not Instagram.
Then—and only then—we built a mobile companion app. Not a simplified version of the desktop app. A complementary app focused on what users actually wanted to do on mobile: Quick portfolio checks. Alerts. Read-only views for when they're away from their desk.
- Desktop engagement: 5x higher after redesign
- Session duration: 3x longer
- User satisfaction: Jumped from 6.2 to 8.7/10
- Mobile app: 40% adoption for quick checks, exactly as designed
The Real Lesson
Mobile-first isn't wrong. It's context-dependent. The dogma is wrong. Blindly following 'mobile-first' without understanding your users and their tasks is wrong. Build for the context where your product delivers the most value. Sometimes that's mobile. Sometimes that's desktop. Sometimes it's both, but with different feature sets for each.
"Design for the device where your users do their most important work. Everything else is secondary."