
For most kids, Python is what comes after Scratch. It keeps the logic your child already knows (loops, conditions, variables) but moves it into real, typed code, which is the biggest jump most kids will make in their coding journey so far. Python isn't the only option though. Some kids are better suited to web development, robotics, or game design as their next step, depending on what they actually enjoyed about Scratch.
If you're not sure which direction fits your child, the short version is this: if they loved the logic and problem-solving, Python is the natural next stop. If they loved the visuals and the finished product more than the coding itself, web development or Roblox game design might hold their attention longer. You can see the full list of options at Young Crafts Academy if you want to compare all of them side by side.
This guide walks through the signs your child is ready to move on, the main paths available after Scratch, and how Nepali parents are sequencing these subjects as their kids move through school.
There's also no strict deadline attached to any of this. Some children move from Scratch into their next subject within six months. Others stay in Scratch for a year or two and arrive at Python, web development, or robotics with a much deeper foundation to build on. Both paths work. What matters is matching the next step to where your child actually is, not to a timeline set by what a neighbor's child or a classmate is doing.
How to Tell Your Child Has Outgrown Scratch
Scratch has a natural ceiling. It's a brilliant first language, but it isn't built for the kind of projects an older, more confident coder eventually wants to make. Here are the signs a child has reached that ceiling.
They've built several games or animations and they're starting to repeat the same ideas
They ask why Scratch can't do something specific, like save data between sessions or connect to the internet
They've worked through most of the beginner project ideas and want something harder
They're curious about "real" code after seeing it in videos, games, or apps
They're 9 or older and reading and typing comfortably
If your child has already worked through a good chunk of our best Scratch project ideas for beginners and is asking for something new, that's usually the clearest signal it's time to move forward.
It's worth separating boredom from mastery here. A child who's bored because they've stopped trying new project types is different from a child who's bored because Scratch genuinely can't do what they want anymore. The first case usually just needs a fresh project idea. The second case is the real signal to move on to something new.
What Comes After Scratch: The Main Options
Scratch actually opens several doors, not just one. Here's how the main next steps compare.
Next step | What it teaches | Best fit for kids who loved | Typical starting age |
Python | Real programming syntax, data, functions | The logic and puzzle-solving side of Scratch | 10 to 12 |
Web Development | Structure (HTML), style (CSS), and behavior (JavaScript) | Building things they can show people, like a webpage | 10 and up |
Robotics | Programming logic applied to physical hardware | Making things move or react in the real world | 9 and up |
Roblox Game Development | Lua scripting inside a game engine | The game-building side of Scratch, taken further | 10 and up |
More advanced Scratch | Complex logic, custom blocks, cloud variables | Kids not quite ready to leave visual blocks yet | Any age, if not ready to move on |
A few things stand out once you lay these options side by side. Python is the only one that's purely text-based programming with no visual or hardware component, which is exactly why it demands the most typing and the most patience with syntax errors. Web development sits in an interesting middle ground: it involves real code, but a page a child can see and share tends to keep motivation higher than Python's more abstract early exercises. Robotics and Roblox both keep a strong visual, hands-on feel closer to what Scratch already offered, just applied to a different kind of project.
None of these are wrong choices. They're just different directions built on the same foundation, and a child can switch between them without losing what they've already learned. If your child has been asking what Scratch actually is under the hood, what Scratch actually is as a coding tool is a useful place to start that conversation before choosing a next step.
It also helps to separate what a child says they want from what they actually enjoyed building. A child who says "I want to make an app" might really mean they want to make something people can use, which points toward web development just as easily as Python. Watching which Scratch projects they came back to on their own, rather than which ones they were told to finish, is usually a better guide than asking them directly.
Why Python Is the Most Common Next Step
Most kids move from Scratch into Python, and there's a clear reason for it. Python's syntax is simple compared to most text-based languages, and it uses the same core concepts as Scratch: loops, conditionals, and variables. A child isn't learning new logic from zero. They're learning to type out logic they already understand.
Nepal's own school curriculum backs this up. The government's Curriculum Development Centre has added block-based programming to the grade 9 syllabus and Python specifically to grade 10, which puts this exact transition on the same timeline many schools already follow.
What Python is, and why it makes sense to learn after Scratch, is covered in full in an earlier post, including what a child's first month of Python typically looks like.
A child's first few weeks in Python usually feel less immediately rewarding than Scratch did, and that's worth preparing for rather than being surprised by. There are no drag-and-drop blocks to lean on, and small typos (a missing colon, an indent that's off by one space) can stop a program from running entirely. Most kids push through this stage quickly once they see their first working program, but it's a real adjustment, not a straight continuation of Scratch.
When to Choose Web Development, Robotics, or Game Design Instead
Python isn't automatically the right call for every child. A few situations point toward a different next step.
Web development fits a child who cares more about how something looks and works for other people than about the code behind it. They want to make a real webpage, not just a script.
Robotics fits a child who likes seeing code affect the physical world, not just a screen. If your child's favorite part of Scratch was making a sprite move, robotics scratches a similar itch with real hardware.
Roblox game development fits a child whose favorite Scratch projects were always games, and who wants to keep building games but with more depth and a bigger audience of players.
There's no penalty for choosing one of these over Python. A child can also come back to Python later once they've spent more time in whichever subject grabbed them first.
Age plays a role here too, though it's a looser guide than most parents expect. A 9-year-old who's spent a year in Scratch and loves building things people can use is often ready for web development, even though it's usually listed as a slightly older kid's subject. A 13-year-old who's newer to coding might still be better served by Python's structured pace before jumping into a subject with three languages running at once. Interest and typing comfort matter more than the number on a birth certificate.
It's also fine for a child to try more than one option before settling on a favorite. A short stretch in robotics or Roblox game development doesn't close the door on Python later, and plenty of kids end up circling back to it once they've had a chance to explore what else is out there. Treating this as a single irreversible fork tends to add pressure that isn't really necessary.
How Long the Transition Usually Takes
Parents often ask how long it takes to actually feel ready to move on from Scratch. The honest answer is that it depends more on how much a child has built than how many months they've spent in the subject.
Time in Scratch | What usually indicates readiness |
3 to 6 months | Comfortable with basic blocks, loops, and simple games |
6 to 12 months | Has built several original projects, not just followed tutorials |
12+ months | Deep familiarity with Scratch, genuinely running out of new ideas |
Our realistic timeline for learning Scratch breaks this down stage by stage, if you want a clearer sense of where your child currently sits.
Siblings and classmates rarely move at the same pace, and that's normal rather than a sign something is wrong. A child who spends more time exploring and less time following structured lessons might take longer to reach the 12-month mark, but often arrives with a stronger grasp of why the code works, not just how to write it. That kind of understanding tends to make the jump into Python considerably smoother, even if it took a few extra months to get there.
Signs Your Child Is Ready to Move On
Putting it all together, here's a quick check before enrolling your child in whatever comes next.
They can explain what a loop or a conditional does, not just use one
They've built at least a few original projects, not only followed along with tutorials
They're reading and typing well enough to handle real code
They're asking questions Scratch genuinely can't answer
They still enjoy coding, and aren't burnt out on the subject entirely
If most of these are true, your child is ready for whatever direction fits their interests best. If only one or two are true, a bit more time in Scratch, building on the skills covered in the real benefits of Scratch coding for kids, is probably the better call before rushing into the next subject.
There's no harm in waiting a little longer either. A child who moves on before they're genuinely ready tends to get stuck early and lose confidence, which can be harder to undo than simply spending another term in Scratch. Readiness shows up in what a child builds, not in how many months have passed on a calendar.
If you're planning this out with a school year in mind, it can help to treat the switch as a decision to revisit each term rather than a one-time choice. A child who isn't ready in April might be ready by September, once a few more projects and a bit more typing confidence are behind them. Checking in periodically works better than committing to a fixed date months in advance.
This is also a good moment to ask what your child actually wants to build next, rather than deciding for them based on what seems like the logical next subject. A child who names a specific project idea, a game, a website, a robot that does something particular, usually points you toward the right next step faster than any checklist can.




