Direct answer
Good mobile app design keeps the person's context in view: a sub-task opens as a sheet or menu over the current screen instead of a new full screen, and every screen has a planned answer for what back does.

Mobile app design: what to know
Each rule is listed with its source at the end of this page, read on November 12, 2026.
- Before you push a new full screen, ask whether the task can live as a layer on the current screen: a bottom sheet, a contextual menu, inline expansion or a popover.
- Keep full screens for a genuinely new context, a task that needs the whole viewport (camera, map, video), or a parent screen that would be misleading if it stayed visible.
- Give a bottom sheet detents, such as compact, medium and full height, so it takes only the height its content needs.
- A sheet should follow the finger one to one while it is dragged, settle from the drag's velocity and distance, and stay interruptible while it animates.
- Use a grab handle instead of a close button on a sheet, and let the whole sheet be draggable, not only the handle.
- Decide what back does before you build each screen: push goes deeper, replace moves on, and sign-in, finished onboarding and a completed purchase are one-way doors.
- Back is blocked in two cases only: an irreversible request in flight, and unsaved work in a modal, where you ask before discarding it.
- Tabs are peers: switching tabs never slides, each tab keeps its own stack, and tapping the active tab returns to its root.
- Use a bottom tab bar for three to five peer destinations, because the thumb reaches the bottom of a phone, not the top.
- At tablet width, turn bottom sheets into side sheets or popovers, and push navigation into a split view.
- Ask for an app review at a pause the person chose, such as the first launch after a major update, never in the middle of a task.
Layer or full screen: what to use on a phone
| Surface | Use it for | Rule that matters most |
|---|---|---|
Bottom sheet | Use it for Filters, share targets, compact forms, previews | Rule that matters most Detents, and dismissal that feels like returning |
Contextual menu | Use it for Actions on one row, card or message | Rule that matters most Keep the action next to its target |
Inline expansion | Use it for Detail that belongs to a list item | Rule that matters most The list keeps its scroll position |
Popover | Use it for Short content tied to a trigger, mostly on tablet | Rule that matters most An arrow anchors it to its source |
Full screen | Use it for A new object or mode, or a task that needs the whole viewport | Rule that matters most Never the default for a sub-task |
Put Mobile app design into practice
- List the screens and write, for each one, whether it is a push, a replace, a sheet, a modal or a tab root.
- Write what back does from every screen, including the iOS edge swipe and the Android system back.
- Turn every sub-task of a screen into a sheet, menu, inline expansion or popover before you add a full screen.
- Pick three to five tabs for the top-level destinations.
- Test sheets and back behavior on a real device, not only in a simulator screenshot.
Mobile app design in four steps
The four steps, in the order you take them.

- Step 1: Plan the screen list
- Step 2: Decide what back does
- Step 3: Layer the sub-tasks
- Step 4: Test on a device
Caveats to keep in mind
- A sheet that ignores drag velocity or blocks input while it animates feels like a modal in disguise.
- A back press that reopens sign-in or finished onboarding is a defect, not a feature.
- A modal sheet still owes the person a dialog's focus rules: move focus in, trap it, and return it to the trigger on close.
- A custom review prompt that asks for stars breaks Apple's App Review Guidelines (5.6.1).
Steal this workflow
Run this guide in your own assistant. The prompt carries the guide link and the workflow summary, so the assistant can adapt it to your project.
Read the guide "Mobile app design: sheets, back behavior and navigation that feel native" at https://better-design.com/blog/mobile-app-design and help me apply it to my project.
Good mobile app design keeps the person's context in view: a sub-task opens as a sheet or menu over the current screen instead of a new full screen, and every screen has a planned answer for what back does.
Start by asking what I am building and which tools I use. Then walk me through the workflow step by step, adapted to my answers.Claude and ChatGPT open with the prompt filled in. Gemini copies the prompt to your clipboard first, so paste it when the app opens.
Questions
What makes a mobile app feel native?
It keeps context visible. Sub-tasks open as sheets, menus or popovers over the current screen, sheets follow the finger and settle from velocity, and back behaves predictably on every screen.
How many tabs should a mobile app have?
Three to five. Past five, people can no longer reach a tab from memory, so the fifth is often a More tab.
Can a coding agent apply these mobile app design rules?
Yes. Put these rules in the agent's instructions before it builds, then ask it to check the rendered screen against each one.
Where these rules come from
Each fact comes from Better Design's mobile guidance, the same guidance its MCP server gives coding agents, read on November 12, 2026.
Related
Build the interface in your own code instead
A coding agent such as Claude Code, Cursor or Codex can build these screens in your own code. Better Design gives that agent a design system, interface principles and review rules, so the result follows rules like these and looks designed.