How people actually hold phones
Phones are held in many ways. Some people cradle the device in one hand and tap with that thumb. Others hold it in one hand and use the index finger of the other. Some use two thumbs, especially when the phone is turned sideways. Posture also changes through the day: someone may use two hands at a desk and one hand on a crowded bus.
Because of this, no single grip is “the” correct one, and designers who assume a particular posture end up excluding people. Left-handed and right-handed users, people with large or small hands, and people with limited dexterity all reach different parts of the screen. The goal is not to optimize for one hand shape but to make the most common actions comfortable for as many grips as possible.
The reach zones
A useful mental model divides the screen into areas of easy, moderate and hard reach for a thumb. With a one-handed grip, the area near the bottom center and the side the thumb rests on is generally easiest. The top corner on the opposite side is typically the hardest and may require shifting the phone or using the second hand.
The exact zones depend on screen size and hand size, and phones have become taller and larger over time, so the top of the screen is harder to reach than it once was. Treat any reach diagram as a rough guide rather than a measurement. Watching real people hold real phones is more informative than any chart.
Where to put things
Frequent actions near the bottom
Controls used often, such as navigation tabs, a primary action button, or a message input, tend to work well in the lower part of the screen. This is one reason bottom tab bars are common, a trade-off that is compared with other navigation patterns elsewhere.
Rare or risky actions farther away
Actions that are destructive or seldom needed, such as deleting an account, can sit in places that are slightly harder to reach, or behind a confirmation. Making something a little harder to tap by accident is a feature when the action cannot be undone.
Content up top, controls below
Reading material and information are mostly looked at, not touched, so the upper part of the screen suits content. Keeping controls out of the top corners is often sensible, although a title bar with a back button is a long-standing convention that people expect.
Avoid forcing grip changes
If a task needs a tap in the top corner followed by a tap at the bottom, the user must shift their hand repeatedly. Review the main flows and look for places where the hand has to travel back and forth, then rearrange so related actions sit near each other.
Touch target size
Reach is only half the problem. Targets also need to be big enough to hit. Platform guidelines generally recommend minimum touch sizes in the region of 44 points on iOS and 48 density-independent pixels on Android, though you should check the current guidance for the platforms you build for. A button can look small while having a larger invisible tap area around it, which is a good way to keep the design clean without making it fiddly.
Also leave space between targets. Two small, tightly packed buttons invite accidental taps, and an accidental tap on the wrong one is more irritating than a slightly larger layout. Spacing matters even more for people with tremors, larger fingers, or limited motor control. That is one of the many everyday accessibility features that benefits all users, including those who are simply walking or holding a bag.
Gestures and edges
Swipes and edge gestures can reduce the need to stretch, but they come with cautions.
- Gestures are invisible, so people may never discover them. Provide a visible alternative for anything important.
- System gestures, such as swiping from the screen edges to go back or return home, can conflict with your own. Avoid placing important controls right at the edges.
- Fast, imprecise swipes cause accidents. Allow undo for gestures that delete or move things.
Screen size and orientation
Large phones and tablets change the picture. On a large device, controls at the bottom corners may be the easiest to reach, while the center of the screen can be far from both hands. On a folding or tablet-size screen, consider splitting content so important controls remain close to where hands rest.
Landscape orientation has its own reach pattern, with thumbs resting at the left and right sides. If your app supports landscape, check where controls fall in that posture, and do not assume portrait positions still work.
Cases and screen protectors change grip slightly too, and many people hold a phone differently when it is in a stand or a car mount. When using map apps or similar tools while on the move, large and well-spaced controls help prevent distraction, and interfaces that require little attention are safer.
Testing reach
You can learn a lot without special tools.
- Print or draw your screens at actual device size and hold them as you would a phone.
- Ask people with different hand sizes to complete a key task using only one hand.
- Watch for hesitation, grip shifts, and accidental taps, and note which hand they use.
- Try the app while standing, sitting, and walking.
- Include left-handed people in your tests.
Early sketches are a cheap place to try this, since paper wireframes can be held at real size long before any code exists. Later, testing on smaller phones as well as large ones, as part of older device testing, shows whether layouts still fit.
Comfort is part of the experience
Constant stretching and awkward grips are tiring, and they may add to hand and wrist discomfort over long sessions. People who feel pain should rest and consider speaking with a health professional, a point also touched on in discussions of posture and screen use. For designers, the practical message is simple: put what people use most where their thumbs already are, make targets generous, and test with several kinds of hands.