By Mehdi HassanCan you design a mobile app without being a designer?
Yes, you can design a mobile app without being a designer, up to a point. Non-designers can do the work that matters most early on: deciding what the app does, mapping how people get through it, writing the words and testing whether it makes sense. Where most DIY apps fall short is the visual system, consistency across screens and build-ready detail.
This guide gives you a realistic path through the first part and shows you where it stops paying to do it yourself. For the full professional process, including handoff and store screenshots, start with our complete guide to mobile app design. This article is the founder's version: fewer tools, fewer deliverables and honest stopping points.
What do you need before you start designing an app?
You need three things before opening any design tool: a clear user, one core job and a list of what you're not building. Without them, every screen becomes a debate, and you'll design features that don't matter while the important flow stays vague.
- A specific user: "freelance designers tracking invoices", not "small businesses".
- One core job: the single task that makes the app worth opening, written as a sentence.
- A cut list: every feature you've thought about, marked now or later. Most should be later.
- A platform decision: native app, PWA or web app. If you're unsure, read our comparison of native apps, PWAs and responsive web apps first.
How to design a mobile app step by step
Here's the path we'd give any founder designing their first app. Each step has a cheap tool and a clear output, and none of them requires design training.
Write the core job and the cut list
One page in a doc: the user, the moment they open the app, the core job and what version one excludes. Share it with one person who'll tell you the truth.
Map the user flow on paper
Draw boxes for each screen from opening the app to finishing the core job, with arrows between them. Add sign-up, the first-run experience and the most likely error. Aim for the fewest boxes possible.
Write the words for each screen
Screen titles, button labels, the onboarding promise, permission explanations and empty-state messages. If you can't explain a screen in words, its design won't fix it.
Sketch each screen
Rough boxes on paper or in FigJam: what's on the screen, in what order, and what the main action is. Put the main action where a thumb can reach it.
Build wireframes in Figma
Use Apple's iOS kit or Google's Material Design kit from the Figma Community. Build in greys, using their standard components, so you focus on structure.
Link a clickable prototype
Connect the screens in Figma's prototype mode so the core flow works end to end, then open it on a phone with Figma's mobile app.
Test with real people
Give a handful of target users the task, hand them the phone and stay quiet. Write down every hesitation and wrong tap, then fix and repeat.
For a deeper look at the first-run experience, our guide to mobile onboarding screens shows how to get users to value fast. For deciding between a tab bar, a drawer or no navigation at all, see mobile navigation patterns compared.
What tools should a non-designer use to design an app?
Use as few tools as possible: paper for flows and sketches, Figma for wireframes and prototypes, and the official platform UI kits for components. Learning one tool well beats trying five, and Figma's free plan is enough to wireframe and prototype a first version.
Job | Tool | Why it suits beginners |
|---|---|---|
Brief and copy | Any doc | Words first, no design skill needed |
User flows | Paper or FigJam | Fast to change, no styling to distract you |
Wireframes | Figma with iOS or Material kits | Real platform components, drag and drop |
Prototype | Figma prototype mode and mobile app | Test on a real phone without code |
Inspiration | Apps you already use | Study how they solve the same problem |
AI tools | AI app builders and Figma Make | Quick working demos, useful for testing ideas |
AI tools can turn prompts or sketches into working demos, which is useful for testing ideas. Treat them as prototypes. They don't replace the thinking in steps one to three, and an app built on a fuzzy flow stays fuzzy however fast it was generated.
What mistakes do non-designers make when designing apps?
The most common mistakes come from designing screens before decisions. They're all fixable, and most cost nothing to avoid if you catch them early.
- Too many features in version one. Every feature adds screens, states and settings. Cut harder than feels comfortable.
- Inventing custom controls. Users already know the standard switch, picker and share sheet. Read iOS vs Android design guidelines before redesigning them.
- Designing only the happy path. No empty states, no errors, no offline behavior. These are the screens new users see first.
- Tiny tap targets. Controls that look fine on a monitor are hard to hit with a thumb. Test on a phone.
- Placeholder copy. Lorem ipsum hides whether a screen makes sense. Use your real words from step three.
When should you hire a designer instead of doing it yourself?
Hire a designer once your flow is validated and the remaining work is about quality, consistency and build-readiness. That's the point where your time becomes more expensive than theirs, and where mistakes start costing developer hours instead of sketching time.
Signal | Keep going yourself | Bring in help |
|---|---|---|
Flow | Still changing after each test | Users complete the core job without help |
Screens | A handful of wireframes | Dozens of screens that need to look consistent |
Goal | Validating the idea | Raising money, launching publicly or hiring developers |
Developers | Not started | About to start and asking for specs and states |
Brand | No brand yet, and that's fine | The app needs to look credible in a crowded store |
Hypothetical example: where a founder hands over
For example, suppose a founder is building a meal-planning app. She writes the brief, maps the flow on paper, wireframes a handful of screens with the iOS kit and tests them with friends of friends. The first round shows people expect to plan a week, not a single day, so she reworks the flow and tests again until people complete it easily.
At that point she has a validated flow, real copy and a prototype. What's left is a visual identity, a component system, states for every screen, store screenshots and files a developer can build from. That's the moment to hire, and because the thinking is done, the designer's time goes into quality instead of discovery.
What hiring costs depends on scope and who you hire. Our mobile app design cost guide breaks down typical ranges. If you want direction before committing to a full design, our fixed-price $3,000 brand and design sprint gives you a brand refresh and ten product explorations in Figma, which suits founders who've done the steps above and want to see what their app could look like.
What comes after the design is done?
After design comes the build, and the handoff decides how much of your design survives it. Developers need every state, the rules for different phone sizes, and assets in the right formats. The framework they choose affects this too, so read our React Native vs Flutter verdict before you hire developers.
Then comes the store: an icon, screenshots and listing copy that sell the core job in a few seconds. Keep testing after launch too. The first real users will find problems no prototype test did, and a team that can design and build fixes quickly will matter more than a perfect first release. Before you hire anyone for that next stage, our guide to hiring a web design agency covers the questions that apply to app partners as well.
