# The 6-Step UX Design Process for Mobile *Published:* 2026-02-05 *Author:* Steven Jacob The UX design process for mobile apps has settled into a six-step pattern that most product teams recognize, even if the tools have rotated. Figma is still dominant, FigJam handles most discovery synthesis, and AI-assisted research synthesis (Dovetail, EnjoyHQ, Glean) has compressed what used to take a week of card-sorting into a two-day sprint. The structural change is that designers are now in the prototyping loop earlier and farther. Below is the current six-step process, with the tooling and the practical thresholds well-run teams hold themselves to. ### TL;DR **The pick:** Discovery (one to two weeks), Definition (one week), Ideation (one to two weeks), Prototype (two to four weeks), Test (one to two weeks), Handoff (one week). A typical mobile UX engagement runs eight to twelve weeks end to end. **Runner-up:** If your timeline is under six weeks, compress Discovery and Definition into a single week and lean on AI-assisted research synthesis to keep quality reasonable. **Skip if:** Skip the full six-step process for feature work on an existing product. Three steps (Definition, Prototype, Test) usually suffice; full Discovery is for greenfield or major redesigns only. Step 1: Discovery and user research ----------------------------------- Start with five to eight one-on-one user interviews, ideally with people in your target segment who are not yet customers. Record everything (with consent), transcribe automatically with Otter or Granola, and synthesize with Dovetail or a comparable AI-assisted tool. Discovery also includes a competitive teardown: install the three main competitor apps, screen-record the core user flow, and analyze decisions about navigation, state handling, and error recovery. The teardown often surfaces solved problems your team would otherwise re-solve. Step 2: Definition and problem framing -------------------------------------- Synthesize discovery findings into three to five key user problems, each with a clear behavioral signal (what users do, not what they say). Convert each into a problem statement that names the user, the situation, and the unmet need without prescribing a solution. Lock the success metric for the design phase at this point: a measurable improvement in a specific behavior on a specific surface. Vague metrics (engagement, satisfaction) drive vague designs. Step 3: Ideation and information architecture --------------------------------------------- Run a structured ideation session (a half-day workshop with engineering, product, and design plus one or two friendly users if possible). The 2026 default workshop format is Crazy Eights or Six-to-One sketching, followed by silent dot-voting and a structured critique round. Convert the chosen direction into an information architecture diagram and a navigation flow. Validate the IA with a tree test (Optimal Workshop, Lyssna) before you start moving pixels in Figma. Step 4: Prototyping in Figma plus Compose or SwiftUI handoff ------------------------------------------------------------ Build low-fidelity wireframes first for fast iteration, then move to high-fidelity once the structure is settled. Figma’s auto-layout, variables, and component libraries make high-fidelity production-ready prototypes practical. For interactive prototypes that need real behavior (typing flows, scroll physics, gestures), drop into Compose or SwiftUI sandbox directly. The cost of building a real interactive prototype has come down materially with AI-assisted code generation. Step 5: Usability testing and validation ---------------------------------------- Run unmoderated tests on Maze, UserTesting, or Playbook with five to eight participants per round. Two rounds of testing on the same prototype, with iteration in between, beats a single round of ten. Test on real devices, not just the desktop browser. Mobile prototypes behave differently on actual phones; gesture conflicts, font rendering, and thumb-zone issues only surface on hardware. Step 6: Handoff and design system integration --------------------------------------------- Handoff means design tokens, not just specs. Figma variables map to Compose Material 3 theme tokens or SwiftUI design tokens; the handoff conversation is about which token applies, not which hex value. Document the interaction states (default, hover, focus, pressed, disabled, loading, error) for every component, including motion timing and easing. The 2026 default is to ship a Lottie or Compose animation specification alongside the design file. The setup, step by step ----------------------- 1. 1#### Discovery: interview five to eight users, teardown competitors One to two weeks. Synthesize with AI-assisted research tools. 2. 2#### Definition: three to five problem statements, one success metric One week. Lock the metric before moving on. 3. 3#### Ideation: workshop plus tree-tested IA One to two weeks. Validate before pixels move. 4. 4#### Prototype: low-fi to high-fi in Figma, real code for interactive prototypes Two to four weeks. Use the design system from day one. 5. 5#### Test: two rounds of unmoderated testing on real devices One to two weeks. Iterate between rounds. 6. 6#### Handoff: design tokens, interaction states, motion specs One week. Ship the design system integration alongside the static designs. FAQ --- ### How big is a typical mobile UX engagement? For a focused engagement: one product designer, one researcher (full-time for discovery, part-time after), and one design engineer for handoff. Add a content designer for copy-heavy products. ### Should we hire a dedicated researcher? Above 50 employees, yes. Below that, designers run their own research with AI-assisted synthesis tools. The discipline matters more than the role title. ### How do we balance design quality with shipping speed? Run the full six steps on greenfield work and major redesigns. Compress to three (Definition, Prototype, Test) for feature work. The full process is overhead you do not need for a label change. ### What about accessibility in the design process? Accessibility is part of every step, not a final review. Color contrast, touch target size, screen-reader navigation, and reduced-motion alternatives should be in the design from the first wireframe. Bottom line ----------- The six-step UX process is more compressed, more AI-assisted, and more directly connected to code than it was three years ago. Teams that run it deliberately ship better products faster than teams that skip steps to save time. The full eight to twelve weeks is the right investment for greenfield work; feature work can run the focused three-step variant and still benefit from the discipline. #### How we put this guide together The picks and steps in this guide reflect what works on current Android builds. Our editors test apps on Pixel 8a and Galaxy S24 hardware running Android 15 and Android 16, cross-check against vendor documentation, and update each guide when behavior changes. ### Related on BestForAndroid - [How to Recover Data from a Broken Android Phone: A Safe Step-by-Step Process](https://bestforandroid.com/tips/recover-data-from-broken-android-phone/) - [How AI Is Transforming Mobile App Development](https://bestforandroid.com/dev/ai-transforming-mobile-dev/) - [Things You Should Know About Apps on Your Mobile Phone](https://bestforandroid.com/things-you-should-know-about-apps/) - [Remove Ransomware From an Android Phone (Step by Step)](https://bestforandroid.com/remove-ransomware-from-android-phone/)