In this guide
"It doesn't work." "The design feels off." "Slow." Feedback like this is common, and it is rarely the tester's fault. They noticed a problem, but nobody told them what a useful report looks like. You can fix that with a few good questions.
What makes feedback actionable
Four things turn a remark into something you can work on:
- Where. Which screen or step.
- What they did. The steps before the problem.
- Expected vs actual. What they thought would happen and what happened.
- Context. Device, system version, app version, connection.
You do not need all four every time, but "where" and "expected vs actual" cover most cases.
One reply template
Thanks, that's useful to know. To fix it I need a bit more: - Which screen were you on? - What did you tap or type just before? - What did you expect to happen, and what happened instead? - A screenshot would help if you can.
Even a short answer to one of these is great.
Keep it short, friendly and with a clear thanks. Four questions are the limit; more reads like an interrogation.
Reply scripts for common vague statements
"It's slow."
Which action felt slow: opening the app, a particular screen, or after a tap? Roughly how long did you wait? Wi-Fi or mobile data?
"Confusing."
What did you try to do when it got confusing? What did you expect to find, and where did you look first?
"It doesn't work."
What did you try? What happened: an error message, nothing, or something else? If there was a message, what did it say?
"I don't like the design."
Which screen? What bothers you: colours, size of text, spacing, or finding things? What would you change first?
"It crashed."
At which step? Did it close by itself or freeze? Does it happen every time? Which phone and system version?
"Missing feature."
What were you trying to get done when you noticed it? How do you do that today without the app?
The last question matters: it turns a wish into a problem, which you can solve in more than one way.
Prevent vague feedback before it starts
- Give a task. "Create an account and add your first item" yields more than "try the app".
- Give a structure. A form with a few fields beats a free text box. A bug report template is a good start.
- Show an example of a good report. People copy what they see.
- Share the guidance with testers. The article how to write app feedback a developer can act on is written for testers and you can link it.
When to stop asking
Ask once, maybe twice. If the tester does not answer, keep the original note with what you know and move on. Chasing people damages the relationship; see testers do not respond.
Related
- Overview: App testing problems and fixes
- Testers do not respond: how to get feedback
- Contradictory tester feedback: how to decide
On AppReviewX, feedback is structured and stays private between you and the tester. One feedback you write earns one credit. Start free