A game can run perfectly and still not be fun. A playtest has two jobs: find what is broken, and find what is boring or frustrating. Keep them apart, or bug reports will drown out design feedback.
Separate fun from bugs
| Bugs | Fun and design | |
|---|---|---|
| Question | Does it work? | Is it enjoyable? |
| Answer | Reproducible steps | Honest impressions |
| Fix | Code | Design, balance, tutorial |
| How to collect | Structured report: what, where, device | Open questions after play |
Ask testers to note bugs while they play, and ask the fun questions only after.
What to observe
- Onboarding: Do players understand the goal and controls without help? Where do they stop?
- Difficulty: Where do they fail repeatedly, and where are they never challenged?
- Session length: How long do they play at once, and why do they stop?
- Pacing: When do they get bored, and when do they feel rewarded?
- Performance: Frame drops, loading times, heat and battery on real phones.
- Controls: Touch targets, gestures, and play with one hand.
If you can, watch one tester play without helping. Your urge to explain is the signal that something is unclear.
Playtest script
Give testers this order, in plain language.
- Play for about 10 to 15 minutes. Do not read instructions first.
- Say out loud, or write, what you are trying to do.
- Note any bug right away: where, what happened, what you expected.
- Stop when you would normally quit, and write why.
- Answer the questions below.
Note sheet
| Question | Answer |
|---|---|
| In one sentence, what is the goal of the game? | |
| What was the first moment you were unsure what to do? | |
| Where did you get stuck or frustrated? | |
| Where was it too easy? | |
| What was the most fun moment? | |
| Why did you stop? | |
| Would you start another session? Why or why not? | |
| Any bugs or slowdowns? Device and OS |
Read for patterns across testers, not single opinions. One person disliking a mechanic is a note; five is a finding.
Limits
Developers are good at spotting bugs, unclear tutorials and performance issues. They are not always your target players, so treat taste-based comments, such as theme or art style, with care.
With AppReviewX
Developers give each other private, structured feedback: 1 feedback = 1 credit, with new accounts starting at 0 credits. Android games on Google Play can use test groups (12 testers, 14 days in a row); published games can use test packages.
Start free and run your first playtest.
Related: App testing for developers · Feedback on a subscription app · First app feedback for beginners