Article7 min readUpdated
Thumb Zone Design: Where to Put Buttons on Mobile Apps
Thumb zone design explained with real screens: where one-handed users can reach, how big tap targets should be, and where to place key buttons.
A delivery rider is holding a phone in his left hand at a traffic signal. His right hand is on the handlebar. He needs to tap "Accept order", and the button is at the top right of the screen. His thumb cannot reach it. He lifts the phone, shifts his grip, and nearly drops it.
This is the problem that thumb zone design solves. A thumb zone is the part of the screen your thumb can reach comfortably while you hold the phone with one hand. Good mobile design puts the controls people use most inside that zone.
What is the thumb zone on a phone?
The thumb zone is a curved area at the bottom and middle of the screen, shaped by how far the thumb can swing from where the hand holds the phone. Phones have grown large, so the top of the screen is now outside that area for most people.
Designers often split the screen into three rough areas:
- Easy: the lower third and the centre, near where the thumb rests.
- Stretch: the middle band on the far side from the thumb, and the upper middle.
- Hard: the top corners, especially the corner on the side opposite the holding hand.
These areas are a guide, not a rule. A right-handed person has the hard corner at the top left. A left-handed person has the hard corner at the top right. Hands are also different sizes, and people hold phones in different ways. Some use both thumbs. Some cradle the phone and tap with one finger.
So I do not design for one perfect hand. I design so that the main task works in the easy area, and nothing important lives only in the hard area.
Why does one-handed phone use matter in India?
One-handed use matters because people in India often use the phone while doing something else. They hold a bag on a bus, carry a tiffin, ride a two-wheeler at a signal, or stand in a queue. Most Indian internet traffic is on mobile, and many people use large Android phones with 6 inch or bigger screens.
Think of a vegetable seller checking an order on his phone while his other hand weighs tomatoes. Or a parent holding a child and paying a school fee through UPI. The app must work with one thumb, in poor light, often with a distracted mind.
For related context on the people you are designing for, see designing apps for Indian users and designing for low-end phones and slow networks.
How big should a tap target be?
A comfortable tap target is roughly 44 to 48 points square, which is about the width of an adult fingertip. This is general guidance that many platform guidelines share. Smaller targets cause missed taps and wrong taps.
Size is only half the answer. Spacing matters as much. Two buttons that are each 48 points wide but touch each other still cause errors.
| Element | Do | Do not |
|---|---|---|
| Icon button | 44 to 48 points of touch area, even if the icon is 24 points | A 20 point icon with no extra touch area |
| Text link in a list | Make the whole row tappable | Make only the small word "Edit" tappable |
| Two buttons side by side | At least 8 points of space between them | Buttons that touch each other |
| Delete and Save | Keep them far apart, give Delete less weight | Place Delete right beside Save |
The visible icon can stay small and neat. The touch area around it can be larger and invisible. Developers can set this padding, so mention it in your handoff notes. My Figma developer handoff checklist covers how to pass that detail on.
Where should I place buttons on mobile?
Place the main action at the bottom of the screen, and place secondary or rare actions higher up. The bottom is easy to reach, and a fixed bottom bar also stays visible while the page scrolls.
Here is how this looks on real screens:
- Checkout: a full-width "Pay ₹499" button fixed at the bottom, above the keyboard area. Do not put "Pay" at the top of the page.
- Booking flow: "Continue" at the bottom, with a small "Back" arrow at the top left, because going back is less frequent.
- Chat: the message box sits at the bottom, because it is the main action.
- Lists with filters: a "Filter" button floating or fixed at the bottom, so the user does not reach to the top bar every time.
Top-of-screen controls are fine for things that are used rarely or should not be tapped by accident. Screen titles, a settings icon and a notification bell can stay there.
If your app has tabs, a bottom navigation bar already follows this rule. I explain the trade-offs in mobile app navigation patterns. For button wording and style, see call to action button design.
What is reachability, and what can you do about the top of the screen?
Reachability means how easily a thumb can get to a control. Some phones have a system feature that pulls the screen down for one hand, but you should not rely on it. Most users do not know about it or never turn it on.
When something important must sit at the top, choose one of these fixes:
- Move the action down. A "Save" button in a top bar can become a full-width button at the bottom.
- Add a second way. Keep the top icon, and also allow a swipe or a bottom button for the same action.
- Use a bottom sheet. Options that open from the bottom are easier to reach than a menu from the top right.
- Shorten the screen. If the page is short, fewer things sit far from the thumb.
I also look at the area where the thumb travels. A button in the far bottom corner, right at the screen edge, can be hard to press because of the curved glass and the phone case. Keep a margin of about 16 points from the edge for key buttons.
What should I avoid?
Avoid placing destructive or costly actions in the easiest spot without protection. The easiest area is also where accidental taps happen. An "Order now" button that sits right where the thumb rests while scrolling will get tapped by mistake.
Common problems I see:
- A floating button that covers the last item in a list.
- A bottom bar plus a floating button plus a cookie banner, all stacked in the same area.
- Tiny close icons in the top corner of a pop-up.
- A bottom button hidden behind the keyboard on a form.
- Text links packed close together in a footer.
For forms, a sticky bottom button must stay visible above the keyboard. See form design best practices for the details.
Also remember accessibility. People with tremors, large hands or limited movement need bigger targets and more space. This helps everyone, but it is essential for some users. My guide on accessibility in app and web design goes further.
How do I test thumb reach on my own app?
Test by holding a real phone, with one hand, and doing the main task. Do not test only on a laptop screen in Figma. A design looks reachable on a large monitor and fails in the hand.
A simple method:
- Pick the three most common tasks in the app.
- Hold a mid-range Android phone in your right hand and complete each task with only that thumb.
- Repeat with the left hand.
- Mark every tap that needed a stretch or a grip change.
- Move those controls lower, or make them bigger.
Ask five people to try the same thing and watch their hands. You will see grips you did not expect. A low-cost way to run this is in usability testing on a small budget.
When I design mobile app interfaces, I check reach on real devices before handoff. If you want a reach check on your own screens, you can get in touch.
Frequently asked questions
Is the thumb zone the same for left-handed users?
+
No. The easy area mirrors for left-handed users, so their hard corner is the top right. Design the main task so it works well for both hands.
Should every button be at the bottom of the screen?
+
No. Put the most common action at the bottom. Rare or risky actions can stay higher so they are not tapped by accident.
What is the minimum touch target size for mobile?
+
A common guideline is roughly 44 to 48 points square, with some space between neighbouring targets. The visible icon can be smaller than the touch area.
Does thumb zone design apply to tablets?
+
Only in part. Tablets are held with two hands or placed on a table, so reach to the corners matters differently. Large phones are where thumb reach matters most.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.