Article5 min readUpdated
The mobile app design process, step by step
How an app goes from idea to developer-ready design: research, user flows, wireframes, visual design, prototype and handoff, with what you should expect at each stage.
By Tithi Mondal, UI/UX Designer
Founders often picture design as someone opening Figma and making screens. The screens are the last third of the work. Here is the whole process as I run it, and what you will see at each stage.
Stage 1: Understand
Before anything is drawn, I need answers to four questions.
- Who is the user, and what are they doing today instead of using your app?
- What is the single most important thing they must be able to do?
- What does the business need: orders, signups, subscriptions?
- What exists already: brand, backend, competitors?
What you get: a short written summary and a list of open questions. Expect a call of about an hour.
Stage 2: Map the flows
A user flow is a diagram of every step between opening the app and completing a task. This is where the hard problems show up.
- What happens if the OTP does not arrive?
- Can someone browse before signing up?
- What does a brand-new user see when there is no data yet?
What you get: flow diagrams and a complete screen list. This list also fixes the scope and the quote.
Stage 3: Wireframe
Wireframes are grey-box layouts. No colour, no images, only structure and words. I start on paper because it is fast, then move the good ideas into Figma.
Reviewing wireframes feels strange at first because they look unfinished. That is the point. You judge whether each screen has the right things in the right order without being distracted by style.
What you get: wireframes for every key screen, linked so you can click through.
Stage 4: Design the interface
Now the visual work.
- Typography and colour, tested for contrast and readability
- Components: buttons, inputs, cards, navigation
- Every screen in high fidelity
- States: loading, empty, error, success
I design two or three key screens first and get your approval on the direction before applying it to everything. Changing direction after forty screens is expensive; changing it after three is not.
What you get: the full set of screens and a component library.
Stage 5: Prototype, test and hand off
The screens are linked into a prototype that behaves like the real app. Put it in front of five people who match your users and watch where they hesitate. Five is enough to find the major problems.
After fixes, developers receive:
- The Figma file with inspectable spacing, colours and type
- Exported icons and images
- Notes on behaviour that a static screen cannot show
- A point of contact for questions during the build
How long it takes
| Stage | Typical time |
|---|---|
| Understand | 2 to 3 days |
| Flows and screen list | 2 to 3 days |
| Wireframes | 4 to 6 days |
| Interface design | 7 to 10 days |
| Prototype and handoff | 2 to 4 days |
A focused first version is usually ready in two to four weeks.
The mistake that costs the most
Skipping straight to stage 4. It feels faster, and for a week it is. Then someone asks what happens when a payment fails, and ten finished screens need to be redrawn.
Planning an app? See my mobile app design service or get in touch.
Frequently asked questions
How long does it take to design a mobile app?
A focused first version usually takes two to four weeks, covering research, user flows, wireframes, interface design, prototype and handoff.
What is a wireframe?
A wireframe is a plain layout of a screen without colour or imagery. It is used to agree on structure and content before visual design begins.
How many people do I need for a usability test?
Around five people who match your target users are enough to uncover the major problems in a prototype.
- Process
- Mobile Apps