Mobile navigation brief
Define mobile navigation that keeps frequent tasks close and behaves predictably across devices and entry points.
Mobile apps · 45 min · Advanced · 21 questions
Structure
Which frequent tasks need persistent navigation?
Which occasional destinations can sit deeper?
Which destinations belong in tabs?
Which tasks need stacked navigation?
When is a navigation drawer appropriate?
Which tasks should open in a sheet?
How will navigation labels stay clear?
Adaptive layouts
How should navigation adapt to tablets?
How should navigation adapt to landscape orientation?
How should navigation work with large text?
How should navigation work in split view?
Back and entry behavior
What should the system Back action do?
What should a header Back button do?
When should swipe-back be available?
Where should users return after closing a modal?
Where should deep links land when prerequisites are missing?
Which navigation state should the app restore?
Accessible navigation
How will the app communicate the current location?
Where should focus move after navigation?
Which navigation shortcuts should work by keyboard?
What reading order should a screen reader follow?
How to use this brief
Use this brief as a bank of questions for the conversation. Choose what is relevant, mark covered questions as you go, and skip anything that has already been answered.
Use this brief when...
Use when you need to define mobile navigation that keeps frequent tasks close and behaves predictably across devices and entry points.
Best used as: Live call · Async intake
- Category
- Mobile apps
- Discussion time
- 45 minutes
- Depth
- Advanced
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Live callAsync intake
- Design roles
- Product designerUX/UI designer
- Audience
- Product designersUX and UI designersDesign leads
- Platforms
- MobileiOSAndroid
- Company type
- B2CB2B
- Product stage
- GrowthMature product
- Tags
- mobile-appsmobile-navigationsystems-and-platformsnavigation-redesignapp-architecture