I’ll admit it: when I built the frontend for [poketto.me, I focused mostly on desktop browsers—except for the reading experience, which was always meant to be mobile-first. But optimizing the rest of the UI for smaller screens later on? A real hassle—and one that could’ve been avoided had I truly embraced mobile-first design from the start.
Here are a few key lessons the hard way taught me:
š± *Thumb-friendly design matters* The Rule of Thumbs is real:
Design for *single-handed use*
Increase button sizes and tappable areas
Avoid placing key controls in hard-to-reach corners
š§ *Navigation needs rethinking* Android users expect the back button to work. On the web, that’s less of a thing—but on mobile, poor back navigation breaks flow. Make sure your app handles this gracefully.
š *UI layout doesn’t scale automatically*
My original layout had a left-hand sidebar menu—totally fine on desktop, completely unworkable on mobile.
Quick fix: I crammed key menu items into the top bar for phones. But what happens when you have more than 3–4? Back to the drawing board...
In short: retrofitting a desktop-first app for mobile works, but it’s clunky. Designing with mobile in mind from day one? Worth the effort.