July 15, 2026
Most phones today are big enough that a thumb can’t comfortably reach the whole screen one-handed. Good mobile UI respects that reality.
Put primary actions in the thumb zone. The bottom third of the screen is where a thumb rests naturally. Primary buttons belong there, not stranded at the top where they need a second hand to reach.
Bottom navigation beats hamburger menus for core actions. Anything a user does often deserves a visible, always-there icon, not a hidden menu that costs an extra tap and hides usage data from you.
Make tap targets bigger than you think. 44×44 points is the usual minimum, but on a moving bus or a distracted walk, bigger targets meaningfully cut mis-taps.
Respect the keyboard. Test every form with the keyboard actually open. It’s astonishing how often a submit button ends up hidden behind it in review.
None of this is exotic. It’s just designing for how phones are actually held, not how they look in a static mockup.
Swipe gestures should be a bonus, never the only way. A hidden swipe-to-delete action that has no visible alternative fails every discoverability heuristic there is. Apple’s own Human Interface Guidelines on gestures are explicit about this: gestures should accelerate actions users already know exist, not be the only path to them.
Sticky headers cost real screen space on small phones. A header that stays pinned while scrolling is convenient, but on a 6-inch screen it can eat 15% of the visible area permanently. Collapsing it on scroll down and revealing it on scroll up gets most of the benefit without the constant tax.
Loading states need to match the wait, not just exist. A generic spinner for a two-second wait is fine. A generic spinner for an eight-second wait feels broken. Skeleton screens that hint at the coming layout keep a longer wait from feeling like a freeze.
Test one-handed, on a real commute if you can. A UI that feels fine sitting at a desk with two hands free behaves completely differently held in one hand on a moving bus. It’s the cheapest, most revealing test available and it’s free.
Good mobile UI is mostly about respecting constraints instead of fighting them. The same instinct applies earlier in the process too, in how a wireframe gets approved before visual design even starts, which I walk through in From Wireframe to Launch: My Web Design Process.
A checkout flow reviewed on a design team’s laptops looked clean, with the primary “Place Order” button sitting comfortably in the middle of the screen. In production, on the actual device mix of real customers, mostly mid-size phones held one-handed while walking or commuting, that same button sat just outside a natural thumb reach for a meaningful share of users, and conversion on mobile lagged desktop by nearly 30%. Moving the button to a fixed position in the bottom third of the screen closed most of that gap within a week of the change going live.
The team hadn’t done anything wrong technically, the design simply hadn’t been evaluated against how phones are actually held. A desktop monitor and a design tool give zero feedback about thumb reach, because there’s no thumb involved in reviewing it.
Since then, every primary action on every mobile layout I ship gets held-in-hand tested on an actual phone before approval, not just reviewed on a screen. It takes thirty seconds and has caught a reach problem on nearly every project since.
Thumb-zone thinking does not stop at button placement, it should shape navigation architecture from the start of a project. Deciding early which three to five actions genuinely deserve permanent bottom-navigation real estate, versus which belong one tap deeper in a menu, is a product decision as much as a design one, and it is far cheaper to make correctly during planning than to retrofit after users have already formed habits around a worse layout. I have seen more than one app quietly lose engagement after a redesign moved a frequently used action out of the thumb zone to make room for something the team was more excited to promote internally, only to reverse the change months later once the usage data made the mistake obvious.
Form design deserves the same scrutiny as navigation. A multi-field signup form designed and reviewed only on desktop routinely turns into a frustrating, cramped experience on mobile, where the majority of signups for most consumer products actually happen. Reviewing every form specifically on a phone, with the on-screen keyboard actually open and covering the bottom third of the screen, catches a category of usability problems that a desktop-only review will never surface, because the constraint simply does not exist on a larger screen.
None of this requires exotic design skill, it requires remembering, consistently, that the device being designed for is held in a hand, not viewed on a stand, and letting that one fact quietly shape every layout decision that follows.
The best mobile interfaces are often invisible in the sense that nobody consciously notices the thumb-zone thinking behind them, they just find the app easy to use without being able to say exactly why. That invisibility is the actual goal, not a flashy interaction nobody asked for.
Designing for thumbs is really just designing for how people actually live, not for how a mockup looks frozen on a monitor at a fixed size.
None of these patterns are complicated once named, but they are easy to forget under deadline pressure when a design just needs to ship. Keeping a short, physical reminder, thumb zone, tap target size, keyboard visibility, taped next to a monitor has done more for consistency on my own projects than any amount of good intentions alone.
A small reminder taped to a monitor is a surprisingly effective form of discipline.
The next time a design review happens on a laptop, it is worth pausing to physically pick up a phone and hold it the way a real user would before signing off on anything meant to be used one-handed on the go.