Why We Added a Skip Button (And What You Did With It)
We shipped a skip button on the tutorial because a few players asked for it on the idea board. We figured some veterans would click it, but we expected most new players to stick with the guided walkthrough. Instead, 80% of new players skipped it within the first week. That number surprised us, and it forced us to ask why.
The tutorial we had was a long sequence of pop-ups and scripted moves. It explained every mechanic in detail, from reload to sprint, before letting you touch a real match. We thought more information meant easier onboarding. But players were voting with their clicks, and they were telling us the tutorial was a wall, not a door.
We also noticed a pattern in the data. Players who skipped the tutorial played more matches in their first session than those who completed it. They died more, sure, but they also stayed longer. That made us reconsider what the tutorial was actually for. Maybe it wasn't about teaching every button, but about getting you into a real game as fast as possible.
The skip button was a small change, but it revealed a huge gap between what we thought new players wanted and what they actually did. It also showed us that our assumptions were worth less than even a single match of real play. So we started watching those first matches closely, and that changed everything.
We learned more from those first matches than from any survey we could have written. This isn't a knock on surveys, because they have their place. But a survey asks what players think they want. A real match shows what they actually do, and that's a far better teacher.
What 500 First Matches Taught Us (Without a Single Question)
We pulled footage from the first matches of 300 players who skipped the tutorial and compared it to 200 who didn't. We watched for hours, and the differences were stark. Skippers died more in the first minute, but they also found the objective faster. They experimented with weapons they picked up instead of waiting for a prompt. They moved with intent, even when they didn't know where they were going.
Players who went through the tutorial were more cautious. They stayed in cover longer, they checked corners more, and they died less early. But they also took longer to start shooting at enemies. They were waiting for the next instruction, and that hesitation cost them in a game that's all about speed. The best teacher turned out to be a live match, not a script.
We also noticed that skippers asked fewer questions in chat. They just played, failed, and tried again. That's exactly the kind of behavior we want, because it means the game itself is teaching them. A tutorial can explain the controls, but only a real match can explain the flow, the tension, and the fun.
The data showed that skipping actually improved long-term retention. Players who skipped were more likely to come back for a second session. We think that's because they had a genuine first experience, not a rehearsed one. They had a story to tell, even if that story ended with them dying to a sniper they never saw.
This isn't to say the tutorial is useless. It just means the tutorial's job is different from what we thought. It shouldn't be a full course. It should be a fast check-in that says, 'Here's the goal, here's the shooter, now go.' The real learning happens in the chaos of a match, and that's where we decided to put our effort.
The New Onboarding: A 30-Second Video You Can Mute
So we cut the tutorial down to a 30-second video. It shows the core loop: pick a loadout, find the enemy, shoot, capture the point. There is no interactive prompt, no forced button presses. You can mute it or skip it entirely, and we won't take it personally. We also added a practice range for players who want to test weapons without the pressure of a match.
The video is there for players who want a quick primer. But we know most players won't watch it. They'll click 'skip' and jump straight into their first match, and that's fine. We built the matchmaking to pair new players together for their first few games, so they're not thrown against veterans who have been playing for months.
That first match is now the real tutorial. We added visual hints that fade out after a few seconds, like 'Press F to sprint' or 'Hold right-click to aim'. They appear only when the context is right, not in a block at the start. This way, players learn by doing, and they never feel like they're being lectured.
The result is that new players get into a real match in under 60 seconds from clicking 'Play'. That's the whole point of a free browser game, to get you into the action fast. Our previous tutorial took five minutes and still left players confused about what to do in a live game. The new approach is honest about what onboarding really is, a quick push out of the nest.
We've seen a 15% increase in players who finish their first match, and a 10% increase in players who come back for a second session. Those numbers came from watching what you did, not from asking you what you wanted. And that's the lesson we want to share with other indie devs: your players will tell you what they need, but only if you're willing to listen to their clicks, not just their words.
What This Means for Your Game (and Why Surveys Aren't Enough)
If you're making a game, you might be tempted to create a detailed tutorial that covers every mechanic. We did that, and it didn't work. The skip button revealed that players wanted to learn by playing, not by reading. A survey might have told us they wanted a skip button, but it wouldn't have shown us how they actually played with it.
Surveys are still useful for measuring brand perception, but they can't capture behavioral nuance. A brand perception survey template can tell you if players think your game is 'fun' or 'hard', but it can't tell you why they quit after three minutes. For that, you need to watch them play, and you need to build the game around what they do, not what they say.
A brand customer experience strategy that relies solely on surveys is missing the point. The best customer experience is one where you remove friction without being asked. Our players didn't ask for a shorter tutorial; they voted with their skip clicks. We just had to notice it and act on it.
We're not saying surveys are useless. A well-designed brand tracking survey can give you directional data over time. But for onboarding, behavioral data is king. If you have the chance to watch players, do it. You'll see things you never imagined, like the fact that players will happily ignore a tutorial they think is too long.
So if you're building a tutorial, keep it short, let players skip it, and watch what they do next. That's the indie game development tutorial we wish we had read before we built our own. It would have saved us months of guesswork and given players a better first experience right out of the gate.