A coding platform for kids stops working the moment it looks like one
HackerKID · GUVI · Product design, gamification, content
Show a nine-year-old a real code editor — the blinking cursor, the empty black panel, the rules they don't understand — and they poke at it once and leave. GUVI wanted to teach kids to code. My job was to make a kid want to come back tomorrow. Those are not the same problem, and the second is much harder.
Curiosity gets them in once
Most kids don't naturally enjoy coding. Curiosity opens the app the first time, but it burns off fast, and underneath it coding is abstract, slow, and full of small failures a kid feels as boredom — and boredom is a closed tab. So the first job was to make the thing not feel like a tool: a kid-friendly interface, playful and alive, where every correct step earns something and every action gets a reaction. The micro-interactions do real work — a button that bounces, a reward that pops, feedback the instant a kid does something right — so the loop of try, see something happen, try again never goes cold.
The honest version is the smart version
I didn't invent these mechanics. I borrowed them — from Duolingo, Khan Academy Kids, Scratch. The patterns that keep kids engaged are already solved; the work was adapting them to coding without turning learning into a slot machine.
The kid doesn't own the device
Then I hit a wall that had nothing to do with the kid: the phone and the laptop are the parent's, and screen time is the parent's call. So any nudge to pull a kid back doesn't reach the kid — it reaches the parent. And a parent is a completely different person to design for; the bright, bouncy, kid-facing tone reads as noise to an adult deciding whether the app is worth their kid's afternoon. The re-engagement layer needed its own calmer voice. I wasn't designing for one user. I was designing for two who don't speak the same language.
Turning the parent into growth
Parents love to show off their kids — that's not vanity, it's fuel. So I built a sharing feature: the kid makes something, the parent shows it off, the parent feels proud, the parent encourages the next thing. The bragging is the retention loop. I also built a parent-facing version to monitor usage — which sounds like a control feature but is really a trust feature. A parent who can see the learning is a parent who keeps the app installed.
Two experiences, side by side
The platform reached 600 real users — real kids coming back, with parents who stayed bought in. The thing I'm proudest of is the shape: a kid experience pure enough to feel like play, and a parent experience honest enough to earn trust, running side by side without either bleeding into the other.
Engaged with the coding, or the confetti?
I'd watch the gamification harder. There's a line where rewards stop motivating a kid to learn and start motivating them to just collect, and I'm not certain I always stayed on the right side of it. Next time I'd instrument that directly — not just "is the kid engaged," but "engaged with the coding or with the confetti."