My kid finished Scratch. What now?

This is the most common stuck point, and the answer is usually not 'a new app.' First, check they have actually built something ambitious in Scratch, not just followed tutorials. A real, finished project (a game with a score, levels, a win state) teaches far more than moving on early. When they are genuinely ready, the next step is a first text language, usually Python, or a physical board like micro:bit that bridges blocks and code. See our guide on moving from blocks to real code.

Do I need to know how to code to help?

No. Your job is not to teach syntax, it is to keep the project alive. Ask 'what are you trying to make it do?' and 'what did you try?' when they are stuck. Free tools like Scratch and Code.org are designed for kids to self-teach. Your curiosity and encouragement matter more than your technical knowledge.

Is my kid too old to start?

Almost certainly not. There is no penalty for starting at 11, 13 or 15. Older beginners often move faster because they can type, read fluently and stick with a harder problem. An older kid can usually skip the youngest tools and start closer to Scratch or even a text language if they are motivated.

Free or paid: does it matter which tool I pick?

The free tools (Scratch, Code.org, Khan Academy, Python tutorials) are not the budget option, they are genuinely among the best available, built by universities and non-profits. Start there. Paid apps and classes are worth considering only when your kid hits a specific wall the free path is not getting them over.

How to Get My Kid Into Coding: An Age-by-Age Starter Map

A free, age-by-age path into coding for kids: which tool to start with at each stage, what comes after Scratch, and when to move to real code.

TinkerWell Editorial27 June 20265 min read

The short answer

Match the tool to the age and start free. ScratchJr from about 5 to 7, Scratch and Code.org from 7 to 11, then a first text language like Python from around 11 or 12. The single biggest mistake is treating it as a curriculum to finish. Pick one project your kid actually wants to make, give them the matching tool, and let curiosity pull them through. You can do the whole early path without spending a cent.

The hardest part of getting a kid into coding is not finding a tool. There are hundreds. The hard part is picking the right one for where your kid actually is, and not turning the whole thing into homework they resent.

So here is a simple, free path. It is organised by age, but treat the ages as rough guides, not rules. The real driver is your kid's interest and a project they want to finish. Everything below can be done at no cost.

Start with the right question

Before any tool, get clear on one thing: what does your kid want to make? A game? An animation of their drawing? A quiz about their favourite thing? A gadget that lights up?

This matters because coding taught as "learn these commands" is dull, and coding taught as "let us build the thing you imagined" is compelling. The tool is just the means. A kid with a project they care about will push through frustration that would make a kid doing exercises quit. So start with the project, then pick the tool that fits it.

The age-by-age map

Age	Start here	Why it fits	Cost
5–7	ScratchJr (tablet app)	Picture blocks, no reading required; kids animate characters and tell stories	Free
7–11	Scratch + Code.org courses	Drag-and-drop blocks remove typing and syntax errors, so kids focus on logic and ideas	Free
10–12	A finished, ambitious Scratch project, then micro:bit (MakeCode)	Bridges blocks to the real world and toward text code	Free software + low-cost board
11–14	Python via free tutorials	The friendliest first text language; reads almost like English	Free
13+	Python projects, web basics (HTML/CSS/JavaScript), or CodeCombat	Real languages on real projects; build something they would actually use	Mostly free

Ages 5 to 7: ScratchJr and unplugged play

At this age the goal is the idea of coding, not coding itself: that you give a sequence of instructions and a thing happens. ScratchJr lets a child make a character move and talk with picture blocks, no reading needed. Just as valuable are "unplugged" games where your kid gives you step-by-step instructions to, say, make a jam sandwich, and you follow them literally (buttering the bag because they did not say "open it" teaches precision better than any app). Keep it playful. There is no progress to track.

Ages 7 to 11: Scratch and Code.org

This is the sweet spot for starting properly, and the two best tools are free. Scratch, made by MIT, lets kids build real games and animations by snapping blocks together, so they learn loops, conditions and variables without fighting syntax. Code.org offers structured, guided courses (the "Hour of Code" activities are a gentle on-ramp) that build skills step by step.

A good rhythm: use Code.org for guided structure when your kid wants to be led, and Scratch for open-ended building when they have their own idea. Resist the urge to rush them off Scratch. A child who builds an ambitious, finished game in Scratch has learned more than one who skimmed three tools.

Ages 10 to 12: bridge to the real world

Around now, many kids are ready for something more, and two bridges work well. The first is a micro:bit, a small, low-cost programmable board you code with blocks (MakeCode) that does real things: light up, sense movement, react. It connects the abstract to the physical, which re-hooks kids who were cooling on screen-only code. The second bridge is simply tackling a harder Scratch project, or starting to peek at text code through MakeCode's "show me the JavaScript" view.

Ages 11 to 14: first real language

When a kid is comfortable typing and reading, and is hitting the limits of blocks, it is time for text code. Python is the standard recommendation for a reason: its syntax is clean and close to plain English, and there are excellent free tutorials. The jump from blocks to text is real and worth handling deliberately, which we cover in From Blocks to Real Code.

Ages 13 and up: build something real

Older kids do best aimed at something they would actually use or show off: a small website, a simple app, a game with their own art, a script that automates a chore. Free web basics (HTML, CSS, JavaScript) let them make things that live on the internet, which is motivating. This is also the age where using AI well becomes part of coding, planning a build, letting AI draft, then debugging it, which we cover in Teaching Your Kid to Use AI Well.

What this is actually teaching (so you can relax)

It helps to remember what the payoff is, because it lowers the pressure. The reliable benefit of all this, per a 2021 research review, is computational thinking: breaking a problem into ordered steps, being precise, and debugging when it breaks. It is not a path to genius and it is not a race. So if your kid spends a year happily making Scratch games and never touches Python, that is not a failure. They are building the exact skill that matters.

The most common mistakes

Buying before trying free. The free tools are world-class. Start there and pay only to clear a real, specific wall.
Treating it as a curriculum to finish. Finishing a course your kid does not care about teaches less than building one thing they love.
Rushing off Scratch too soon. Depth in blocks beats a shallow tour of five tools.
Hovering. When they are stuck, ask "what have you tried?" rather than fixing it. The stuck-and-recover loop is where the learning lives.
Making it a chore. The moment it feels like enforced homework, motivation, the one thing that actually carries a kid through coding, drains away.

Key takeaways

Start with a project your kid wants to make, then pick the tool that fits it.
Follow the free age-by-age path: ScratchJr (5–7), Scratch and Code.org (7–11), micro:bit and first text code (10–12), Python (11–14), real builds (13+).
The free tools are genuinely the best ones. Pay only to clear a specific wall, not to begin.
Depth beats breadth: a finished, ambitious Scratch project teaches more than a quick tour of many apps.
The payoff is computational thinking, not a brain upgrade, and it is not a race. Starting later costs nothing.

This is one part of the bigger picture in Coding, Robotics & AI for Kids: What's Worth It, and What's Hype. When your kid is ready for the next step, read From Blocks to Real Code.

Common questions

My kid finished Scratch. What now?: This is the most common stuck point, and the answer is usually not 'a new app.' First, check they have actually built something ambitious in Scratch, not just followed tutorials. A real, finished project (a game with a score, levels, a win state) teaches far more than moving on early. When they are genuinely ready, the next step is a first text language, usually Python, or a physical board like micro:bit that bridges blocks and code. See our guide on moving from blocks to real code.
Do I need to know how to code to help?: No. Your job is not to teach syntax, it is to keep the project alive. Ask 'what are you trying to make it do?' and 'what did you try?' when they are stuck. Free tools like Scratch and Code.org are designed for kids to self-teach. Your curiosity and encouragement matter more than your technical knowledge.
Is my kid too old to start?: Almost certainly not. There is no penalty for starting at 11, 13 or 15. Older beginners often move faster because they can type, read fluently and stick with a harder problem. An older kid can usually skip the youngest tools and start closer to Scratch or even a text language if they are motivated.
Free or paid: does it matter which tool I pick?: The free tools (Scratch, Code.org, Khan Academy, Python tutorials) are not the budget option, they are genuinely among the best available, built by universities and non-profits. Start there. Paid apps and classes are worth considering only when your kid hits a specific wall the free path is not getting them over.

Sources

The weekly build prompt

One short email a week: a small, concrete thing your kid can build or try this weekend, plus the occasional story of a real family who built something. No spam, no lectures.

Keep reading

Guide