FTUE — First Time User Experience — is a set of metrics and practices that measure how new users interact with your app during their first session. It directly affects D1 retention: the percentage of users who come back the next day.
A weak FTUE doesn't just hurt Day 1 numbers. It undermines everything downstream — D7 retention, paying conversion, and LTV. No amount of re-engagement campaigns fixes a broken first impression. This glossary entry covers what to measure in FTUE analysis, how to diagnose drop-off points, and what to fix first.
What Is FTUE?
When a user opens your app for the first time, they make a fast judgment: is this worth my time? If the answer isn't obvious within the first session, they leave — and most won't come back.
FTUE is the aggregate of everything that shapes the first session: the onboarding flow, the tutorial, the first core action, and the moment — or its absence — when the user understands what makes your product valuable.
A strong FTUE doesn't mean a long tutorial. It means users reach their "aha moment" fast: the first solved puzzle, the first completed task, the first time the app does something useful. That moment is what drives D1 retention.
What Metrics Define FTUE?
FTUE isn't a single number — it's a cluster of metrics that together show how well your first session is working.
D0 Retention — the percentage of users who open the app more than once on the day of installation. A low D0 suggests users aren't finding enough value to stay past the initial launch.
D1 Retention — the percentage of users who return the day after installation. This is the primary FTUE health metric. Industry average for mobile games sits around 25–40%. For apps, 20–30% is a reasonable baseline.
Tutorial completion rate — how many users finish the onboarding flow. A sharp drop at a specific step tells you exactly where friction is. That step is your first priority.
Session depth on Day 0 — how far users get in their first session. If most users drop before reaching the core feature, they never experienced what makes your product worth returning to.
How to Analyze FTUE
Start with D1 retention. If it's below benchmark, the problem is in the first session — and the first session almost always means the tutorial or onboarding flow.
Step 1: Build a tutorial funnel. Map every step of your onboarding as a funnel event. Look for the step with the largest drop-off — that's your bottleneck. In devtodev, you can build this funnel without writing SQL and filter it by device type, acquisition channel, or country to see if the problem is universal or specific to a segment.
Step 2: Check session depth on Day 0. If users complete the tutorial but don't return on Day 1, the tutorial isn't the problem — the core loop is. Users finished onboarding but didn't experience enough value to come back. Look at what actions high-retention users take in their first session that low-retention users don't.
Step 3: Find the aha moment. Compare the behavior of users who returned on Day 1 vs. those who didn't. What did returners do that others skipped? That action — completing a level, uploading a file, connecting an account — is your aha moment. Make sure every new user reaches it in the first session.
Step 4: Watch D7 and D28. D1 is the entry point, but FTUE quality shows up in downstream metrics too. A strong D1 with weak D7 means users came back once but didn't find a reason to stay. That's an engagement loop problem, not an onboarding problem — but it starts in the first session.
How to Improve FTUE
Fix bugs before anything else. New users notice friction that long-time users have learned to ignore. A crash, a slow load, or a confusing UI element on Day 0 will kill D1 retention faster than any content issue. Run a dedicated new-user test session after every release.
Cut onboarding length. The longer the tutorial, the more drop-off points. Every mandatory step that doesn't directly show value is a risk. Audit each tutorial step: if removing it doesn't hurt comprehension, remove it.
Delay sign-up. Asking users to create an account before they've had any experience is one of the most common FTUE mistakes. Let users reach the aha moment first. Sign-up after value delivery converts significantly better.
Show value, don't explain it. Telling users your app is useful is less effective than making them feel it. Design the first session around doing, not reading. The first action should produce a visible result — a solved level, a generated output, a completed profile.
Personalize from the start. A brief onboarding questionnaire (2–3 questions max) lets you tailor the first session to the user's goal. Users who see relevant content on Day 0 retain significantly better than those who get a generic flow.
Learn more about A/B testing in LiveOps →
Takeaways
- FTUE measures the quality of a user's first session — and directly determines D1 retention, which sets the ceiling for all downstream metrics.
- The key FTUE metrics are D0 retention, D1 retention, tutorial completion rate, and session depth on Day 0.
- Start the diagnosis with a tutorial funnel. The step with the biggest drop-off is your first priority.
- Find your aha moment by comparing Day 1 returners vs. non-returners. Make sure every new user reaches it.
- Fix bugs first, cut onboarding length second, delay sign-up third.
- D1 benchmark: 25–40% for mobile games, 20–30% for apps. Below that, the first session needs work.
Find drop-off points in your onboarding funnel and see exactly where new users leave. Explore devtodev →