What Should a 9-Year-Old Be Coding in 2026?

Last updated: June 2026

A 9-year-old in 2026 should be coding in Scratch, with most kids landing somewhere between basic animations and their first real games with if-statements. A small group of 9-year-olds with prior experience are ready to dip into Python. None of them are building "real apps" in two months, no matter what a coding school's website says.

This article gives you a realistic month-by-month picture of what a 9-year-old should actually be building, what tools fit, what to ignore, and what to do if your kid is "behind" or "ahead." Across 200+ kids I have taught, the 9-year-old window is one of the most rewarding ages, but also one where bad expectations cause the most damage.

Key Takeaways

• A 9-year-old beginner should start in Scratch, not Python, not Roblox, not Minecraft modding. The block environment is the right fit for the brain at this age.
• After 3 months of weekly 1-on-1 Scratch lessons, a 9-year-old should be making animated multi-sprite scenes. After 6 months, simple games with if-statements and variables.
• A 9-year-old with 6+ months of Scratch and "the spark" (logic curiosity, not just game enthusiasm) can start peeking at Python.
• 9-year-olds vary enormously. The right next step depends on the kid, not the calendar age.
• Coding schools that promise your 9-year-old will build "real apps" in 2 months are not telling the truth. By 9, the realistic ceiling is a polished mini-game.

Table of Contents

• The honest baseline for a typical 9-year-old
• Months 1 to 3: what a 9-year-old beginner is building
• Months 3 to 6: where if-statements appear
• Months 6 to 12: real games and the Python question
• What 9-year-olds should NOT be doing
• What to do if your 9-year-old is ahead or behind
• Frequently Asked Questions

The honest baseline for a typical 9-year-old

Before any month-by-month plan, two realities to settle.

Reality one: a 9-year-old's brain is in the sweet spot for visual, block-based coding. They can read fluently, they can remember what they did last week, they can plan a project over multiple sessions. They are also still mostly thinking in pictures and stories, not in abstractions. That is exactly what Scratch was built for. MIT's Lifelong Kindergarten group designed Scratch (scratch.mit.edu/about) explicitly for the 8 to 16 range, with the sweet spot landing around 9.

Reality two: the answer to "what should my 9-year-old be coding" depends on how long they have been at it. For example, a 9-year-old who started last week is in a totally different place from a 9-year-old who has been coding since they were 7. Both are normal. Therefore, the plan below splits by how much experience the kid has.

For the full picture across the 8 to 10 window, see the deeper checklist in Kids Coding Milestones Ages 8-10: A Real Tutor's Checklist.

Months 1 to 3: what a 9-year-old beginner is building

A 9-year-old starting from zero, with weekly 1-on-1 Scratch lessons, should land in roughly this place after three months:

• Comfortable opening Scratch, picking sprites, saving and reloading projects
• Moving sprites with arrow keys and the "when key pressed" event
• Building 1 to 2 sprite scenes with dialogue using the "say" block
• Switching costumes to make simple animation (walking, mouth opening)
• Showing a finished mini-project to a parent voluntarily, that is the engagement signal

What they should NOT be doing yet: if-statements, variables, loops, broadcasts. Those come later. However, if a tutor is forcing those concepts on a 9-year-old in month 1 because the curriculum says so, the kid will pattern-match without understanding. That comes back to bite later.

What it looks like in practice: by month 3, a typical 9-year-old beginner has built a simple animated story (think: a character walking across a beach, saying hi, a sun rising in the background). It looks small. It is the right thing. The skill being built is operational, not conceptual.

Months 3 to 6: where if-statements appear

The back half of the first 6 months is when the conceptual work starts. A 9-year-old in this window should:

• Use their first if-statement, usually around month 4 or 5. Often a "if touching sprite" check in a chase game.
• Add their first variable, usually a score or a lives counter.
• Use the "forever" loop and the "repeat" loop with intent (not just because the tutor said to).
• Plan a project ahead of time, even loosely. "I want a game where the cat chases the mouse and you get a point when you catch it."
• Start trying things on their own when something breaks, before raising a hand.

The proudest 9-year-old moment in this window is usually their first complete game. Two sprites, an if-statement, a score variable. Looks tiny. It is exactly the right level. A 9-year-old who can build this without the tutor doing the typing has crossed a real threshold.

I had a 9-year-old last quarter who built a basketball game in Scratch around month 5. He was sports-obsessed. We swapped out every default example for one about points, shots, and rebounds. He went from glazing over in month 2 to begging for extra sessions in month 6. That swap is the entire technique. For more on the interest-swapping pedagogy specifically, see The 30-Second Trick That Makes Kids Care About Code.

Months 6 to 12: real games and the Python question

In the back half of year one, a 9-year-old should be:

• Building 3+ sprite games with collisions, scoring, lives, and a win/lose condition
• Using nested if-statements (an if inside another if) with some understanding
• Using broadcasts to coordinate behavior between sprites
• Recovering from broken projects without giving up
• Asking questions like "is there a way to do this faster" or "could I make this work for any number of enemies, not just 3"

That last question is the one that signals readiness for the Python conversation. When a 9-year-old starts asking abstraction questions ("for any number," "every time," "no matter what"), they are showing what I call the spark. That is when text-based coding becomes possible.

The spark is not a calendar event. Some 9-year-olds show it at month 6 of Scratch. Some show it at month 18. Some 11-year-olds never show it because they have only ever been in Scratch tutorials, not Scratch projects. The spark comes from the kid, not the clock.

Just last month, a 9-year-old student of mine looked up from a Scratch maze game and asked, "is there a way to make the walls smarter so they chase me back?" That single question, unprompted, told me he was ready for Python. We started Turtle the following week. Meanwhile, another student the same age who had been with me longer still wasn't asking that kind of question, and forcing Python on him would have been a mistake.

If your 9-year-old has shown the spark and a tutor has assessed them honestly, the right next move is a careful, slow start in Python with Turtle graphics. Visual output, simple syntax, a real language. For the full readiness checklist, see When Should Kids Switch from Scratch to Python? A Tutor's Guide.

What 9-year-olds should NOT be doing

A short list, but an important one. These are the things I see kids being pushed into at 9 that consistently backfire.

Building "real apps" in 2 months. This is the line some coding schools sell to parents. It is not real. A 9-year-old at month 2 is still working on basic Scratch. They are not building mobile apps that go on the App Store. Parents have come to me burned by exactly this. They signed up elsewhere, paid for months, got nothing concrete after 8 weeks, and felt lied to. The schools that overpromise this are not telling the truth. For more on this specifically, see If a Coding School Promised Your 9-Year-Old Would Build Apps in 2 Months.

Multiple languages at once. I see 9-year-olds who have "tried" Scratch, Python, JavaScript, and Roblox in the same year. As a result, they are fluent in none of them. Depth beats breadth at this age. Pick one tool, stick with it, build real projects.

Heavy text-based syntax. A 9-year-old beginner does not need to be typing Python. They need to be building things they care about with as little syntax overhead as possible. Pushing text-based coding too early produces kids who hate coding by age 10.

Self-paced apps as a primary path. Apps like Code.org or Khan Academy are fine as supplements, but a 9-year-old learning alone in front of an app rarely builds the recall, debugging instinct, or project completion skills that a real teacher produces. For more on the apps vs classes question, see Coding Apps vs Coding Classes: What Parents Should Know.

Activity	A 9-year-old should...	A 9-year-old should NOT...
Scratch	Build animated stories and games	Just complete tutorial after tutorial
Python	Start only if "the spark" shows	Be forced to type syntax early
Roblox	Play, optionally try Studio with guidance	Be sold as their main coding path
Self-paced apps	Use as light supplement	Be the only structured learning
"Building apps"	Build mini-games and scenes	Promise to ship a real app in weeks

What to do if your 9-year-old is ahead or behind

The single most common parent question I get at this age: "is my kid behind?"

If your 9-year-old has been in weekly Scratch lessons for 6 months and has not yet built a game with an if-statement and a variable, something is off. Not necessarily the kid. Usually the format, the teacher, or the curriculum. Self-paced apps, large group classes, and bored tutors all produce this exact stall. The fix is not more time. It is a format change.

If your 9-year-old is genuinely ahead, comfortable with multi-sprite Scratch games at month 4, asking abstraction questions by month 6, the right move is not to push them faster. It is to deepen their projects. A 9-year-old who builds five really polished Scratch games is better prepared for Python than a 9-year-old who blitzes through twenty half-built ones. Mastery at the current level beats rushing to the next one. For the broader signs of readiness, see Signs Your Child Is Ready for Coding Lessons.

Finally, if your 9-year-old just refuses, do not force it. Some kids are not ready at 9. Some need to be 10 or 11 before any of this lands. For more on the right starting age, see What Age Should Kids Start Coding?.

Frequently Asked Questions

Should a 9-year-old learn Python or Scratch? Almost every 9-year-old should start in Scratch. A small group with prior experience and what I call the spark (real logic curiosity, not just game enthusiasm) can dip into Python. The default is Scratch. The exception is rare, and a good tutor can assess it within one or two sessions.

How long until my 9-year-old can build a real game? A real Scratch mini-game (multi-sprite, if-statement, score, win condition) typically arrives somewhere between month 4 and month 10 of weekly 1-on-1 lessons. A real Python project arrives later, usually after another full year. A "real app" in 2 months is a marketing line, not a real timeline.

What if my 9-year-old gets frustrated and quits coding? Most 9-year-old frustration comes from one of three things: examples they do not care about, lessons going too fast, or being left alone in front of an app. All three are fixable. For specific tactics, see When Coding Makes Kids Upset: A Parent's Playbook.

Is 9 too young to start coding from zero? No. 9 is a great starting age. The brain is ready for Scratch, the reading skills are usually fluent enough to follow blocks, and the attention span fits a 45 to 60 minute weekly lesson. 9 is one of the most common starting ages for our students.

How many hours a week should a 9-year-old spend coding? One 45 to 60 minute weekly lesson with a tutor, plus light at-home tinkering when the kid is motivated. More than that at 9 is usually unproductive. Coding is a high-concentration activity. Quality of attention matters more than quantity of hours at this age.

Related Articles

• Kids Coding Milestones Ages 8-10: A Real Tutor's Checklist, the full month-by-month checklist for the broader 8 to 10 window.
• What Age Should Kids Start Coding?, if you are deciding whether to start at all.
• If a Coding School Promised Your 9-Year-Old Would Build Apps in 2 Months, why those promises are not real and what to expect instead.

The Bottom Line

A 9-year-old in 2026 should be coding in Scratch, building real projects that match their interests, and progressing at their own pace. Anything else, real apps in 2 months, multiple languages at once, heavy syntax too early, is either marketing or malpractice. The right path for a 9-year-old is unspectacular and durable.

Wondering exactly where your 9-year-old should be right now? Book a free Discovery Call and we will look at what they are building today and map the next right step.