Here's what usually happens. A parent finds a coding platform, sits down with their kid, and watches them stare at an empty screen for ten minutes before giving up. Then the parent wonders if coding is just not their kid's thing.
It usually is. The blank screen is the problem.
Start with a project, not a tool
Most coding platforms hand a kid a set of tools and say: go make something. That's a hard ask. Adults freeze in front of blank pages too. Kids need a concrete thing to build before the tools make any sense.
So before you open anything, ask your kid what they would quiz their friends on. Pokémon? Soccer stats? Their favorite singer? Whatever the answer is, that's the project. Build that specific thing. The topic gives them a reason to push through the hard parts.
Keep sessions short
Twenty minutes of a kid actually making something beats two hours of clicking around feeling lost. Pick one small goal per session. "Today we're going to get the first question to show up on screen." That's a win. Next session, build on it.
Kids are also a lot more willing to come back when the session ends before they're frustrated, not after.
Resist fixing things immediately
When a kid gets stuck, the instinct is to jump in. Try waiting a minute first. Ask them what they think is going wrong. Half the time they'll figure it out themselves, and that moment sticks in a way that an explanation never does.
The goal is a finished thing
A quiz their friends can actually play. A game they can send to their grandparents. Something with a link. Not a lesson completed, not a badge earned. A real thing they made. That's what makes them want to come back.
If you want something that handles the guiding part for you, that's what we built Codli for. A kid picks a topic they love and builds a real quiz game with an AI tutor walking them through it. No blank canvas.