In this guide
Building an app takes weeks or months. A few conversations first can save you from building the wrong one. This page shows what to ask, what to show, and who can answer what.
What developers can judge, and what only target users can
| Question | Developers | Target users |
|---|---|---|
| Is the flow clear and logical? | Yes | Yes |
| Is the scope realistic to build? | Yes | No |
| Does the prototype look broken or inconsistent? | Yes | Yes |
| Does this solve a real problem for me? | Only if they are the audience | Yes |
| Would I switch from what I use today? | Only if they are the audience | Yes |
| Would I pay? | Unreliable | Unreliable, but closer |
Developers are good at flow, feasibility and clarity. For "do people want this", you need people from the audience you are building for. Be clear about which question you are asking whom.
What to show
You do not need working code.
- A clickable prototype from a design tool, with the main flow only.
- Or a few annotated screens and a one-paragraph description.
- Show one flow, not every screen.
Question set for idea validation
Use these in a short chat or form. Ask about behaviour, not opinions about your idea.
Problem 1. How do you handle this today? 2. What is the most annoying part? 3. When did you last run into it?
Concept 4. In your own words, what does this app do? 5. Who would use it? 6. What would you expect to happen after this tap? (point at a screen)
Alternatives 7. What would make you keep using what you have now? 8. What is missing from this idea?
Next step 9. If this existed in a month, what would you want to see first?
Avoid leading questions like "Wouldn't this be great?" and do not ask people to promise to pay or download. Those answers are polite, not true.
What to do with the answers
- Count how many describe the same problem unprompted.
- Note where people misread the prototype; that is your design work.
- Decide: build, change direction or drop. All three are good outcomes of a cheap test.
With AppReviewX
Developers give each other private, structured feedback. It works well for flow and clarity on a prototype or early build. It does not replace talking to your actual target users. 1 feedback = 1 credit; new accounts start at 0 credits.
Start free and put your first flow in front of people.
Related: App testing for developers · Feedback on a mobile game · Feedback on a subscription app