Why Your FTUE Is Losing 40% of Players

Most games front-load complexity. Here's how I approach first-session design to maximize D1 retention without dumbing down the game.

The first three minutes of your game are worth more than the next three months of content updates.

I don't say that to be dramatic. I've watched the data. Across every casual title I've worked on — zombie shooters, Vietnamese-themed games, action titles targeting US and Tier 1 markets — the single biggest retention cliff is always in the first session. Players open the game, play for a few minutes, close it, and a staggering number never come back.

The industry average for casual games sits around 35–45% D1 retention. That means on a good day, more than half your players quit after one session. And in almost every case I've investigated, the problem wasn't that the game was bad. The problem was that the first-time user experience told the player the game was bad — even when it wasn't.

The FTUE is not a tutorial

This is the first mistake I see in almost every game I consult on. The team treats the FTUE as a tutorial — a sequence where you teach the player how to tap buttons, explain every UI element, and walk them through their first fight or match or level.

The player doesn't want a tutorial. The player wants a reason to care.

Think about the last time someone recommended you a TV show. You didn't need someone to explain what a remote control does. You needed a good first episode. You needed a hook — something that made you want to find out what happens next.

Your FTUE is your pilot episode. It needs to do three things in the first session:

1. Deliver a moment of genuine fun within 60 seconds. Not a cutscene. Not a text box. An actual gameplay moment where the player feels something — power, humor, curiosity, satisfaction.

2. Establish one clear loop. Not three systems, not the full economy. One loop they understand: do the thing, get the reward, do the thing again but harder.

3. Create an open question. End the first session with something unresolved. An upgrade they haven't unlocked. A boss they glimpsed but can't fight yet. A countdown timer to something. The player needs a reason to come back, not just a memory of something they already did.

That's it. Everything else can wait.

Stop front-loading complexity

I've redesigned FTUEs where the first session included: a name-input screen, a faction choice, a 45-second cinematic, a UI walkthrough pointing at 8 different buttons, a forced tutorial fight, a second tutorial explaining upgrades, a gacha pull explanation, an energy system tutorial, and a daily login popup. All in the first five minutes.

The player hasn't even played the game yet and they've already made 12 decisions they don't care about.

Here's my rule: every system you introduce in the first session is one more reason for the player to quit. Not because the systems are bad, but because the player has no context for why they should care about them yet.

When I redesign an FTUE, I strip out everything that isn't directly related to the core gameplay loop. All those secondary systems — guilds, gacha, daily missions, social features, the shop — they get introduced organically over the first 3–7 days as the player discovers they need them.

The upgrade system? Don't explain it in minute two. Let the player hit a level where their current gear isn't enough, and then surface the upgrade screen. Now they understand what it's for because they felt the need first.

The shop? Don't show it on the first session. Show it when the player wants something they can't earn yet. Now it's a solution, not a wall of options.

I call this need-first design: never introduce a system before the player has felt the need for it.

The data tells you exactly where they leave

Here's where being a game designer and a data analyst at the same time pays off. Most GDs design the FTUE based on intuition and playtesting with their team. Their team already knows the game, so they can't experience confusion. That's not testing — that's confirmation bias.

When I design an FTUE, I log every step. Every screen transition, every button tap, every moment where the player could potentially quit. Then I look at funnel data: what percentage of new users reached step 3? Step 5? Step 10? Where's the sharpest drop?

At VNG, I found that one of our titles lost 22% of new players between the faction-selection screen and the first actual gameplay moment. Twenty-two percent of people opened the game, saw a screen asking them to choose between three factions they knew nothing about, and left. The fix was simple: remove the choice, auto-assign a faction, and let players change it later when they actually cared. D1 retention jumped.

That's a design insight, but it came from a data pipeline, not a brainstorm.

I run the same analysis at Corochti now. Every FTUE change gets A/B tested with statistical significance (Mann-Whitney U, not just eyeballing averages). If the change improves D1 retention by a statistically meaningful amount, it ships. If it doesn't, it gets reverted. No opinions, no "I think players prefer this" — just evidence.

Pacing is the invisible skill

Good FTUE pacing is something players never notice. Bad pacing is the only thing they notice.

The pattern I use:

0–30 seconds: The game loads and the player is doing something immediately. No splash screens, no loading bars if avoidable, minimal branding. If your game is a shooter, they should be shooting within 30 seconds. If it's a puzzle, they should be solving within 30 seconds.

30–90 seconds: First small win. The player completes something and gets clear positive feedback — a score, an animation, a reward, a level-up. This is the moment that determines whether they keep playing. Make it feel good. Sound, screen shake, particle effects — whatever your genre calls for.

2–5 minutes: The core loop clicks. The player understands: I fight, I earn, I upgrade, I fight harder. Or: I match, I clear, I unlock, I match harder. They shouldn't need to think about what to do next — the game should pull them forward naturally.

5–10 minutes: Introduce one secondary system. Just one. Whichever one creates the strongest "oh, that's cool" moment. Save the rest.

End of first session: Leave them wanting more. A teaser, an unlock timer, a cliffhanger. The player should close the game thinking about it, not feeling like they've seen everything.

Monetization in the FTUE: don't

One of the things I do differently from most monetization specialists: I keep the first session almost completely ad-free and IAP-free.

I've seen games show a rewarded video in the first two minutes. I've seen games pop up a starter pack offer before the player has completed their first level. Every time I've tested removing early monetization touchpoints, D1 retention improved. Every single time.

The math is simple: a player who comes back tomorrow is worth more than a player who watches one ad today and never returns. The first session is about retention, not revenue. You have 30 days to monetize them — you have 60 seconds to keep them.

At Corochti, I designed the ad system with a first-session delay: no ads at all in the first session. After that, the pacing kicks in — but the player has already decided they like the game before they ever see an ad. That's why we can run aggressive IV/RV pacing later without killing D30 retention.

The FTUE is never done

Every title I work on gets FTUE revisits at least quarterly. Player expectations change. The market evolves. A mechanic that felt fresh six months ago might feel generic now.

I look at three numbers:

• Step-through rate: What percentage of new users complete the full FTUE sequence? Any step below 85% completion gets investigated.
• Time-to-first-session-end: How long is the average first session? Too short means you're not hooking them. Too long might mean they're confused and wandering.
• D1 retention by FTUE completion: Do players who complete the full FTUE sequence retain significantly better than those who drop off mid-sequence? If yes, the FTUE is working and the problem is getting people through it. If no, the FTUE itself might be the problem.

These three numbers tell me whether to optimize the existing flow or rethink it entirely.

The takeaway

Your game's long-term success is decided in its shortest moment. Every system you introduce too early, every popup that interrupts the first win, every decision you force before the player cares — it's a leak in a funnel that no amount of LiveOps or content updates can fix downstream.

Design the FTUE like a first date: be interesting, don't show all your cards, and make them want a second one.

This is the second in a series about game design, data, and monetization in F2P mobile games. I'm Du Che Anh — Product Owner & Lead Game Designer at Corochti Studio, previously at VNG Corporation. If you're shipping a game and your D1 numbers don't look right, I've probably seen the same problem. anhdc@corochti.vn