How to playtest a game
The first time someone else plays your game, they'll press the wrong button within 10 seconds, walk straight past the thing you were proudest of, and die somewhere you thought was easy. That's what playtesting is for, and it works best if you keep quiet and watch.
Why you can't test your own game
You know where every enemy spawns, which button jumps and what the goal is. A new player knows none of that. They only have what's on screen, and a playtest shows you which parts of your game depend on knowledge they don't have.
Before the test
- Pick one question. "Do people understand the goal?" or "Is level 2 too hard?"
- Find the right people. Ideally someone who's never seen the game. Friends are fine, but they tend to be polite, so watch what they do more than what they say.
- Test on the device people will use. A game that feels great with arrow keys can be fiddly with a thumb stick on a phone. On HOLO X1, holos run on both, so try both.
During the test: say nothing
Hand over the game with no instructions beyond "play this." Then keep your mouth shut. When you explain something mid-game, you lose the chance to see whether the game explains it. Players at home won't have you standing next to them.
Watch for:
- The first 10 seconds. Do they move? Do they know which button does what?
- Hesitation. Long pauses usually mean confusion.
- Where they lose. Note each spot. If 3 people lose in the same place, the spot probably needs fixing.
- What they ignore. A power-up nobody picks up might be too hard to spot, or not worth the risk.
- Their face and voice. Laughs, groans and "oh no" tell you where the fun is.
- When they stop. Did they quit, or did they hit restart? That's your best single measure.
Write things down as they happen. You'll forget most of it within an hour.
After the test: ask a few open questions
Good questions don't hint at an answer:
- "What were you trying to do?"
- "What was the hardest part?"
- "Was there a moment you didn't know what to do?"
- "What would you change?"
Avoid "Did you like it?" Almost everyone says yes. Treat suggestions as clues about a problem. When a player says "add a double jump," the real message might be that a gap is too wide.
Turn what you saw into small fixes
Rank what you found by how many players hit it and how early. A problem in the first 30 seconds matters more than one at the 5-minute mark, because most players never get there. Fix one thing at a time and test again, so you know which change helped.
Common fixes for small games:
- Slow down the opening so players learn before they're tested.
- Make threats bigger or brighter so they're seen in time.
- Label the buttons. Holos on phones already show what A and B do.
- Shorten the round so a loss doesn't cost too much.
How to make a game fun and design tips for small games have more.
Playtesting on HOLO X1
Every holo is public from the moment it's built, so playtesting starts on its own. Share your holo's link with a friend using the Share button, then watch them play in the same room if you can.
Feature requests work like a running playtest log. Anyone who plays a holo can suggest a change in up to 160 characters, and other players vote on them. When a request reaches 3 votes, the console builds it into a new version automatically, and older versions stay playable from a version menu. If you see several requests asking for the same fix, that's the same signal as 3 testers dying in the same spot. How voting works explains the process.
Because every version stays playable, you can also run a quick A/B test yourself: play version 1, then the latest, and decide which one you'd rather replay.
Test a game today
Pick a holo from the directory or the arcade shelf, hand it to someone, and practice watching without talking. Or build your own from the make form and test that instead. If you're making one with your family, making a game with kids has tips for testing with younger players.