Boba Tale — Tutorial That Builds Confidence and Cravings

Boba Tale is a cozy shop-management game where players run a boba café in a kawaii world. However, the game launched without onboarding, leaving new players unsure how to play and causing early drop-off.

I designed a structured onboarding experience to teach core mechanics, build player confidence, and support early retention—while preserving the game’s playful tone.

The game had warmth, personality, and a world worth staying in. What it didn't have was a way to welcome players into it.

No early guidance. New players had no direction and often quit before completing their first successful order — before they could fall in love with the game.

Unclear upgrade value. Without context, players didn't understand how upgrades or IAPs supported progression — making purchase moments feel arbitrary instead of helpful.

A tone that couldn't be sacrificed. Any tutorial needed to teach quickly without becoming a lecture. In a kawaii world, even the instructions have to feel like part of the fun.

Mapped the first-session experience I traced the journey from launch to first completed order, identifying exactly where confusion entered and where players were most likely to drop off. The goal was to know when to step in — and when to get out of the way.

Designed guided microcopy Short, actionable prompts over long explanations. Every line of tutorial text was written to answer one question at a time, in context, without pulling players out of the experience.

Built trust through tone Warm, encouraging language aligned with the kawaii aesthetic — progress reinforced with positive feedback, not corrective instruction. The voice had to feel like a friendly café owner, not a user manual.

Implemented lightweight onboarding patterns Guidance broken into micro-interactions. Repeatable tooltips instead of one-time info dumps. Messages that were quick, relevant, and visually unobtrusive — so the onboarding felt like the game, not a layer on top of it.

With 27% of negative reviews tied directly to missing first-session guidance (per developer data), a well-designed onboarding system targets the game's most documented pain point. This approach is expected to:

Increase tutorial completion rates

Reduce early drop-off before first successful order

Help players recognize upgrade value before purchase prompts appear

Convert frustrated first impressions into retained players

Onboarding isn't just the start of gameplay — it's the start of a relationship. When players feel lost in the first five minutes, they don't give the game a second chance. They leave a one-star review.

UX writing that teaches gradually, speaks warmly, and respects the player's time can turn that first session from a friction point into a hook.

This project started with a real problem: a developer watching players leave before they'd even settled in. The stat made it concrete — 27% of the criticism came down to one fixable thing.

Designing the onboarding meant asking what players needed to know, in what order, and how to say it in a voice that felt like Boba Tale — not like documentation. That balance between clarity and charm is where I find the most interesting UX writing problems.