How to get honest feedback on your app (not just "looks great!")
Friends say "looks great". Strangers just leave. Here is how indie developers get honest, specific feedback on an app or game, and what to do with it.
· 4 min read

Short answer: honest feedback comes from people who have no reason to be polite, who actually use the app, and who are asked specific questions. Watch a few people use it without helping, ask "what worked, what could be better, what broke" instead of "do you like it?", and put your app where strangers who enjoy trying new things can review it. Then show that you act on what you hear, because that is what makes people keep telling you the truth.
Why is most early feedback useless?
Three things get in the way:
- Politeness. Friends and family want to support you, so "looks great!" is the default answer. It feels good and tells you nothing.
- Vague questions. "What do you think?" invites vague answers. People don't know what you need to hear.
- Silent churn. Most people who don't like an app don't complain. They close it and never come back. You only see a number go down.
The fix for all three is the same: more strangers, better questions and less effort for the person giving feedback.
Who should I ask?
Mix three groups, because each tells you something different:
- Two or three people you can watch. Sit next to them (or share a screen) and give them one task, like "sign up and create your first project". Don't explain anything. Where they hesitate is where your app is confusing. Five sessions like this find most of the big problems.
- Your target users. People who have the problem your app solves. Find them in communities about that topic, not in developer communities. A fitness app needs people who train, not people who code.
- Strangers who like trying new apps. They have no stake in your feelings and compare you with everything else they've tried. Discovery communities and launch boards are full of them. On TrueLaunch, for example, every review asks the same three questions, so the feedback arrives structured instead of as a single star.
What should I ask?
Replace "do you like it?" with questions that have useful answers:
| Instead of | Ask |
|---|---|
| Do you like it? | What worked well for you? |
| Any feedback? | What could be better, and why? |
| Did it work? | Did anything break? What were you doing when it happened? |
| Would you use it? | What would make you open it again tomorrow? |
| Is it easy? | Where did you get stuck or have to guess? |
Ask for the device and OS version when people report bugs, and ask for steps to reproduce. "It crashed" is a clue; "it crashed when I rotated the phone on the settings screen, Pixel 7, Android 15" is a fix.
How do I make it easy to give feedback?
- Keep it short. Three questions get answered. Fifteen get abandoned.
- Ask at the right moment. Right after someone finishes a task or a level, not on first launch.
- Offer a private channel inside the app. A "Send feedback" link that opens an email or a short form catches problems before they become public complaints.
- Reply to everyone. A short "thanks, fixed in 1.2" turns a tester into a fan and makes them tell you more next time.
How do I handle negative feedback?
Treat a harsh review as free consulting. Look for the problem behind the tone:
- If one person says something, note it.
- If three people say the same thing, it's real. Fix it or explain clearly why it's that way.
- Reply calmly and specifically, and say what you changed. Other people read your replies and judge the app by them.
What should I never do?
- Never ask for a specific star rating, and never ask for a store rating in exchange for anything: features, coins, a giveaway or a review of their app. Google Play and the App Store both forbid incentivized ratings, and they can remove ratings or apps that break the rule.
- Never trade ratings with other developers ("I'll rate yours 5 stars if you rate mine"). Rating swaps tell you nothing and put both apps at risk.
- Don't argue with reviewers in public. Fix things and let the update answer for you.
Next steps
Pick one task, watch three people try it this week, and write down every place they got stuck. At the same time, list your app on TrueLaunch to get structured reviews from people you don't know. If you are on Android and still need testers for Google Play, start with our guide to getting 12 testers for closed testing.
Frequently asked questions
How many people do I need to ask for feedback?
For finding usability problems, five people watched one by one find most of the big issues. For opinions about what to build next, you want more, ideally from your target users rather than friends.
Is it okay to ask users for an App Store or Google Play review?
You can ask neutrally, for example with the official in-app review prompt, but never ask for a specific rating and never offer anything in return. Incentivized ratings break both stores' policies.
Where can I get feedback from strangers?
Communities about your app's topic, launch boards and app discovery sites. On TrueLaunch, people review apps and games by answering what worked, what could be better and which bugs they found.