With so many users on mobile, I've always been told to design for the small screen first. However, our B2B dashboard is used almost exclusively on desktop. Is "Mobile First" still the gold standard for enterprise software, or should we focus on the complex data density of desktop and then "gracefully degrade" for mobile users? What are your experiences with these methodologies?
3 answers
"Mobile First" is a philosophy of prioritization, not just screen size. It forces you to decide what is truly essential. However, for B2B enterprise software, "Desktop First" is often more practical because your users' primary context is an office environment with large monitors. If you try to force a complex data grid into a mobile-first mindset, you might end up over-simplifying the desktop experience and hurting productivity. In my last project, we designed for 1440p first to handle the data density, but we used a rigid 8pt grid system that made it much easier to collapse those columns into a card-based layout for the mobile version later.
Do you find that your stakeholders are more easily convinced by seeing the desktop version first, or does showing the mobile version help them focus on the core features?
I prefer "Content First." Identify the most important data point for the user, and make sure that is prominent regardless of whether they are on a phone or a 32-inch monitor.
Content is king! If you prioritize the data the user is looking for, the screen size becomes a secondary implementation detail rather than a design hurdle.
Jeffrey, stakeholders almost always want to see the desktop version first because it looks "more complete" to them. But I often show them a mobile wireframe during the discovery phase to kill off unnecessary features. It's a great "BS detector." If a feature isn't important enough to make it onto the limited real estate of a mobile screen, we really have to question if it belongs on the desktop version at all, or if it's just adding clutter to the interface.