Most mobile players never return after their first session. That makes the first level of a game, not the last, its most important one. During prototyping we spend most of our time on that opening half-minute.
A first move instead of a tutorial
Opening screens that explain the rules in text go unread. Instead we design the first level so that there is only one correct move. When the player makes it, they have learned the rule and feel they discovered it themselves. Later levels work the same way: a new rule arrives through a situation that calls for it, not a sentence that explains it.
What the first 30 seconds need
- A response on the first tap: sound, vibration, motion.
- A first win within ten seconds.
- A first small challenge within twenty.
- A moment at second thirty that makes them say “one more”.
These timings are a rhythm, not a strict rule: first a response, then a win, then a small obstacle, then the wish to carry on. If the order breaks, say the challenge comes before the win, the player quits without knowing what they did wrong.
The response to the first tap
When the player first touches the screen, something should happen under their finger: the object moves, squashes slightly, a short sound plays, the phone gives a faint buzz. That response tells the player “the game heard you”. If it comes late or not at all, the player taps again, then decides the game is broken.
We watch three details. Many people keep their phone on silent, so the motion must carry the message without sound. Right and wrong moves should get different responses, but a wrong move should not punish: the object wobbles and settles back, nothing more. Vibration should be brief and possible to switch off in the settings.
Pacing difficulty in the first levels
The first level teaches a single rule. The second repeats that rule in a different arrangement; here the player enjoys using what they have just learned. The third adds something new. Each level gets one new idea; when two arrive together, the player cannot tell which one tripped them up.
The first failure should come after the player understands the rules, and it should be cheap: one tap back into the same level, with no waiting screen or long animation. Losing teaches; waiting makes people close the game.
What to hold back
The store, daily rewards, account linking and ads. All of these make sense only after the player likes the game. Shown in the first session, they ask for something before the player has seen any value. Each has its right moment:
- The store: once there is something the player might want, a few levels in.
- Daily rewards: at the end of the first session or the start of the second, as a reason to come back.
- Ads: first the kind the player chooses to watch in return for a reward; ads that interrupt play only after the first session.
- Account linking: once the player has progress they would not want to lose.
A good first level is designed to be understood, not to be won.
How to run a five-person test
Hand the prototype to five people with no explanation and just watch. Note where they hesitate; that's the spot to fix. We run the test in this order:
- 1
Find five people who have never seen the game and are not on the team.
- 2
Hand over the phone and say only “play”; don't describe the game.
- 3
Don't help. If they ask a question, answer with “what would you do?”
- 4
Note where the finger stops, where it taps wrongly and when the person looks up at you.
- 5
When the first round ends, stay quiet and wait: do they start a second unprompted?
- 6
At the end, ask one question: what were you supposed to do in this game?
What we look at
Two things: the hesitations, and a second round that nobody asked for. “I liked it” is not a measure; people also say it to be kind. What the finger does is more honest than what the mouth says.
After each test we remove the biggest hesitation and give the game to new people. Someone who has seen the game once cannot play it for the first time again, so every round needs fresh faces.
Common mistakes
- A long text tutorial: three screens of rules to read. Players skip them and still don't know what to do in the first level.
- Sign-up before play: asking for an email or an account is asking for something before giving the player anything.
- Too many buttons on the first screen: store, settings, leaderboard, events… The opening screen needs one obvious button: play.
This is why we start a game with a playable prototype, not with artwork or a revenue model. If the first thirty seconds are not fun, a prototype makes that easy to see and change; once levels, art and a store are added, the same change costs far more.
