Contents
UX research for apps means finding out systematically, before development starts, who your users are, what problems they have and how they deal with them today. Even a handful of interviews and a simple usability test uncover assumptions that would otherwise have to be corrected expensively after launch. This guide shows suitable methods, a lean process and common mistakes.
Why UX research before development saves so much money
Every app rests on assumptions: that users have a certain problem, that they want to solve it on a smartphone, that they understand certain terms and expect flows in a certain order. If those assumptions are wrong, even perfect code will not help. A change to the concept costs a few hours; the same change after development often costs weeks.
UX research is not a luxury reserved for large corporations. Founders and mid-sized companies benefit too when they talk to five to eight real users before the first sprint. The effort is manageable, and the insight gained is usually substantial.
The key methods at a glance
| Method | What you learn | Effort | When to use it |
|---|---|---|---|
| User interviews | Problems, motivations, current workarounds | Low to medium | At the very start |
| Contextual observation | How tasks are done in the real working environment | Medium | For workflow apps (field service, trades, care) |
| Online survey | Distribution of needs and preferences across larger groups | Low | After interviews, to quantify hypotheses |
| Competitor analysis | Existing solutions, store reviews, gaps | Low | In parallel with interviews |
| Usability test with prototype | Whether users understand flows and can complete tasks | Medium | After first drafts, before development |
| Analytics of existing products | Actual behaviour on a website or a predecessor app | Low | When a digital offering already exists |
For most app projects, a combination of interviews, competitor analysis and a usability test is enough. Surveys make sense when you want to extrapolate results to a larger audience – but they do not replace conversations, because they only answer questions you already know to ask.
A lean process: UX research in five steps
- Define research questions: write down three to five questions you need to answer. For example: "How do technicians document their jobs today?" or "What stops customers from booking online?"
- Recruit participants: find five to eight people who truly match the target group – existing customers, employees, contacts from associations or professional groups. Friends and family tend to be too kind.
- Conduct interviews: 30 to 45 minutes each, open questions, concrete past situations rather than hypothetical wishes. Note verbatim quotes.
- Synthesise findings: group observations into patterns, derive personas or jobs-to-be-done, and prioritise the most important problems.
- Validate with a prototype: translate the findings into a clickable prototype and let users complete typical tasks with it. Wherever they get stuck, the concept needs sharpening.
How to turn research results into a testable prototype is covered in our article prototyping: why a clickable prototype pays off.
Good interview questions – and ones to avoid
The quality of your results depends heavily on your questions. People are bad at predicting their future behaviour but good at telling stories about concrete experiences.
Good questions:
- "Tell me about the last time you had to … How did you go about it?"
- "What was the most tedious part?"
- "Which tools do you use for this today – paper, Excel, other apps?"
- "What happens when something goes wrong?"
Questions to avoid:
- "Would you use an app that …?" – almost everyone politely says yes.
- "How much would you pay for it?" – hypothetical prices say little.
- "Do you like this feature?" – leading and unrelated to actual behaviour.
Supporting UX research with AI – with care
AI tools can speed up research work: drafting interview guides, summarising transcripts, clustering statements by theme or analysing competitors' app store reviews. They do not replace conversations with real people, though. Synthetic "AI users" produce plausible but invented answers and often just confirm your own assumptions. Also keep data protection in mind: interview recordings and transcripts contain personal data. Obtain consent and only use tools whose data processing is GDPR-compliant.
Common UX research mistakes
- Talking only to internal stakeholders: sales and management know customers, but they are not the users.
- Seeking confirmation instead of learning: if you defend your idea, you will miss critical signals.
- Starting too late: research after the design is finished often serves only as justification.
- Not documenting results: without a short, shared summary, insights get lost in daily project work.
- Treating research as a one-off: after launch, conversations, analytics and feedback continue to provide valuable input – for instance for better onboarding.
Budget and integration into the app project
UX research does not have to be a large project of its own. A few days for interviews, analysis and a prototype test are often enough. The effort naturally fits into the concept and design phase; for an overview of typical design budgets, see UI/UX design costs for apps. If you first want to clarify more fundamentally which problems your target group wants solved at all, product discovery is the next step.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
UX research is the cheapest insurance against an app nobody needs. With clear research questions, five to eight good interviews and a usability test on a prototype, you go into development with solid insights. If you would like to build your app on that basis, our offer wizard gets you a free analysis with a fixed-price offer.
Frequently Asked Questions
How many users do I need for UX research?
For qualitative interviews and usability tests, five to eight people per target group are usually enough, because important patterns tend to repeat after that. For quantitative statements you need a survey with considerably more participants.
Can I do UX research myself?
Yes, founders and product owners can run simple interviews and usability tests themselves. What matters are open questions, genuine target-group representatives and an honest analysis.
What is the difference between UX research and market research?
Market research mainly examines market size, willingness to pay and competition. UX research focuses on how people complete tasks and how a product must be designed so they understand it and enjoy using it.