Send this survey right after a test, while memory is fresh. It is short on purpose: twelve questions, most of them quick to answer. Each question has a reason, so you can cut what you will not use.
Copy-paste template
Thanks for testing [App name] build [n]. This takes about [5-8] minutes.
About you and the setup
1. Which device and OS version did you use?
2. How much of the test did you finish? (all / most / some / little)
Tasks
3. Which task did you complete without trouble?
4. Which task was hardest, and what made it hard?
5. Was there a moment you did not know what to do next? Where?
Quality
6. Did anything crash, freeze, look broken or feel slow? What were you doing?
7. Was any text, button or icon unclear? Which one?
Trust and intent
8. In your own words: what does this app do and who is it for?
9. Did anything make you hesitate to enter data or grant a permission? What?
10. Would you use this app again? Why or why not?
Wrap up
11. What is the one thing you would change first?
12. Anything else we should know?
Why each question is asked
- Device and OS: a bug report without these cannot be reproduced.
- How much finished: separates "found nothing" from "did not get far".
- Easy task: shows what already works; protect it.
- Hardest task: points to the likeliest usability problem.
- Lost moment: finds unclear navigation that testers rarely call a bug.
- Crashes and slowness: captures technical problems with context.
- Unclear labels: cheap copy fixes.
- Own-words summary: tests whether the app explains itself. A wrong answer is a finding.
- Hesitation: surfaces trust and permission issues.
- Use again, and why: intent is a signal, but only the "why" is useful. It is not a promise.
- One change: forces a priority.
- Anything else: catches what you did not think to ask.
How to adapt it
- Cut to the questions you will act on. Seven answered questions beat twelve skipped ones.
- Match the tasks to your own task list. Replace 3 to 5 with the actual task names from your tester task list.
- Keep it private and unrated. Ask for feedback to you, not for store ratings.
- Read open answers in groups. Count how many testers mention the same thing; do not average opinions.
For how testers should write good feedback, see how to give useful app feedback. Related: usability test script and the hub mobile app testing checklists.
Want structured, private feedback on your app? Start free.