The mobile-first mindset most designers fake
Everyone claims to design mobile-first. Very few actually do. Here is how to tell the difference, and why it decides whether your site works for the 70% of visitors on a phone.
Ask any web designer if they design mobile-first and the answer is always yes. Look at their actual process and the answer is almost always no. What most designers do is design desktop-first in Figma at 1440 pixels wide, then squash the result into a phone-shaped frame at the end and call it responsive. The output looks passable on a phone but was never conceived for one, and it shows in every decision: hero images that get cropped in awkward places, navigation that collapses into a menu icon nobody taps, buttons that were spaced for a mouse cursor and now sit two millimeters apart under a thumb.
Genuine mobile-first design starts on a 375-pixel-wide artboard and stays there until every core flow works. Only once the phone version is fully resolved does the designer scale up to tablet and desktop, treating the larger breakpoints as opportunities to add breathing room rather than opportunities to cram in more. This inversion matters because the constraints of a phone force honest decisions: you cannot hide behind three columns of feature cards or a five-item mega menu when you only have one column and a thumb. You have to pick what matters and cut the rest.
The tells that a site was not really designed mobile-first are everywhere once you know what to look for. Tap targets smaller than 44 pixels. Body copy under 16 pixels that forces the reader to pinch-zoom. Hero images with a face or a logo that gets cropped out on portrait orientation. Sticky headers that eat 20% of the viewport. Modals that cannot be dismissed with a swipe. Forms that trigger the wrong keyboard type for the field (an email input should show the email keyboard, a phone input the number pad). Each of these is a small paper cut; together they are the reason a site "feels janky on mobile" without anyone being able to point to a single bug.
The 70% number is not a rhetorical flourish. For most local service businesses and consumer brands, mobile traffic is now 65% to 80% of total sessions, and the mobile-to-desktop conversion gap is the single largest source of leaked revenue on a small business site. If your desktop converts at 4% and your mobile at 1.2%, you do not have a traffic problem — you have a mobile experience problem, and every dollar you spend on ads is being taxed by it.
Fix it by auditing your own site on a real, mid-range Android phone (not the latest iPhone on office Wi-Fi) and completing every important flow — landing, browsing, contact, checkout — with your thumb, standing up, in bright daylight. Every time you have to squint, pinch, wait, or backtrack, write it down. That list is your mobile-first roadmap. Ship the fixes in priority order and watch the conversion gap close. The designers who genuinely work mobile-first do this test on every project, before launch, without being asked. The ones who fake it never test on a real phone at all.
Written by NeoWebCre Studio
Start your project