← Back to Native mobile foundation team
See how it helps
Mobile user journeys
Plans end-to-end mobile tasks around real context, one-handed ergonomics and recovery from incomplete steps.
mobile-ux-flows
Team members using this skill
When is it useful?
Use when a flow works screen by screen but fails as a complete task.
What does it help you do?
- Prioritizes the user's goal and likely conditions of use.
- Places frequent actions within comfortable reach and avoids hidden gestures.
- Covers entry, completion, cancellation and error recovery together.
Try asking this
Design a one-handed expense-submission journey from receipt capture to confirmation with an interrupted-upload recovery path. Capture a receipt on the move, interrupt upload and resume later. Preserve entered amounts and make clear whether the expense is a draft or submitted.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Mobile UX & User Flows
Design mobile experiences around real-world context—short attention spans, one-handed reach, varying screen sizes, interruptions and clear progression toward the user's goal.
1. Context of use and task prioritization
- Start every flow by identifying who the user is, where and how often they perform the task, and what single primary outcome defines success on each screen.
- Never treat a mobile app as a shrunken desktop website. Strip secondary clutter and rank content so the primary task and next step are immediately obvious without horizontal scrolling or hunting through nested menus.
- Design for both first-time users (who need clear orientation and low-friction first value) and returning users (who need fast repeat execution, saved context and recent items).
2. Ergonomics and one-handed thumb reach
- Place frequent primary actions and navigation in the comfortable bottom/middle thumb zone; keep destructive or irreversible actions separated from primary tap areas and guard them with clear confirmation or undo.
- Account for small phones, large phones, foldables and tablets: avoid fixed pixel heights that break when content wraps or the virtual keyboard appears.
3. End-to-end flow completeness
- Map the entire journey, not just the happy path:
- Entry points: tab tap, deep link, push notification, widget or share sheet.
- Primary progression: each step shows where the user is, what is required now, and what happens next.
- Back, cancel and exit: what happens to entered data when the user steps back or closes a modal (preserve draft, auto-save, or confirm discard).
- Interruption and resume: phone call, app switch, lock screen or OS backgrounding mid-flow—never lose user input silently.
- Completion and recovery: unmistakable confirmation of what succeeded, or an actionable recovery path on failure.
Before you finish
- Every screen in the flow has one clear primary purpose and next action within easy thumb reach.
- Entry points, back/cancel behavior, draft preservation and completion states are defined.
- Both new-user orientation and returning-user speed are accounted for.
Included files 1
SKILL.md