Review the first session in three passes: comprehension, feel, and operational fit. Record the decision after each pass before discussing personal taste.
Start with the player’s first minute
Open the build without a walkthrough. The first pass should answer a simple question: can a new player understand what to do, what changed, and what the next action is?
Watch the hierarchy before judging the theme. Controls, stake information, game state, win communication, and recovery from an interruption should be understandable without relying on a presenter.
- Identify the primary action in five seconds
- Confirm the result is readable at normal phone distance
- Interrupt the session and check whether returning feels obvious
Separate feel from preference
A reviewer may dislike a color palette and still recognize strong interaction design. Keep subjective theme reaction separate from pacing, feedback, legibility, and consistency.
Ask each reviewer to describe what the game communicates rather than whether they personally like it. This produces feedback a studio can act on and makes disagreements easier to resolve.
- Theme reaction: who is this world for?
- Interaction feel: does every action receive useful feedback?
- Pacing: where does attention rise, wait, or fall?
Finish with the operating context
The last pass connects the build to the intended channel. Review the game at the smallest realistic viewport, on an ordinary connection, and alongside the surrounding lobby or terminal experience.
End with a written disposition: advance, revise, or stop. List the evidence that would change the decision. A demo review is useful when it reduces uncertainty, not when it creates a longer opinion thread.
