Wonderkit for 8-Year-Olds: Or Is It Time for Scratch?

At eight a kid reads the chat alone, types their own ideas and could be in Scratch instead. Which kid Wonderkit suits at this age, and which it does not.

Eight is the first age where this page has to argue against itself. Scratch, the block-based language from MIT, is usually pitched at eight and up, and an eight-year-old who enjoys puzzles may well be ready for it. So the honest first question for a parent of an eight-year-old is not "can they use Wonderkit" — they can, largely alone — but "which of these two is my kid".

The Scratch question, answered first

Watch what your kid does with a box of Lego. One kind of eight-year-old follows the instructions to the end, then takes it apart to see how the hinge worked. That kid wants to know how, and Scratch gives them that: every behaviour in the game is a block they placed, and the joy is in the placing. If that is your kid, the Scratch comparison is fair about why Scratch wins, and it is free.

The other kind of eight-year-old dumps the box out and starts narrating — there is a base, and the base has a trap, and the trap only works at night. They are not uninterested in how things work; they are more interested in what happens. Wonderkit is built for that kid. They describe the trap, it gets built, they play it, and they say what the trap should do differently.

Some kids are both, on different days, and using both tools is a reasonable answer. The two are not in competition for the same hour.

What eight-year-olds tend to ask for

Ideas we made up to show the shape of eight; no real child's creation is on this list:

• Towers on a path. Enemies walk a winding road; the kid places three kinds of tower — slow, fast, splash — and each wave is bigger. By wave five they are asking for an upgrade button, which may be the first economy they have ever designed.
• Get out of the room. A locked room, a drawer, a key under a rug, a four-digit lock and a clue written backwards on the mirror. The kid invents the clues, and the clues are harder than you expect.
• Times tables boss fight. Each correct answer is a hit; a wrong one and the boss hits back. Homework the kid volunteers for, because they chose the boss.
• A comic that changes. Four panels, a hero, a villain; tap the last panel to choose the ending and the strip redraws. A story kid's version of a game.
• Lava floor. Platforms sink when you stand on them; the floor rises; the score is how long you last. Simple to describe, hard to put down.

The thread through these is that each game has two things interacting: towers and waves, clues and locks, answers and health. At seven the ask was for lives and levels; at eight it is more often for a system, and the kid is now old enough to notice when the parts of the system do not add up.

The chat, without you in the room

An eight-year-old who reads fluently runs the conversation. The AI asks what the towers cost and what the boss's weak spot is; they answer, in their own spelling, and it copes. On the web they can tap the microphone and speak the answer instead of typing it (in Chrome, Safari and other browsers with speech input). The iOS app's chat has no microphone; replies there can be read aloud if you switch it on, and a fast reader will not want it.

Then the build runs, they play it, and they come back with a list. That loop is the whole activity, and at eight it runs without a grown-up at the keyboard for the first time. Reworking a creation costs nothing from your credits at any tier, though there is a daily fair-use ceiling on how many changes a creation can take, so "make it red, no blue, no red" is not a good use of an afternoon.

Where you still come in

Three places, none of them at the keyboard.

The scope. Eight-year-olds often ask for the game they played at a friend's house, complete. What comes out is a game in the spirit of it, one page big, with no other players joining from elsewhere and nothing saved between visits — every play starts fresh. Saying that before the build, in one sentence, spares a lot of disappointment after it. Then ask which single part they would keep if they could only have one, and build that.

The settings. Each kid's Agent settings hold the reading level the AI writes at (from Pre-K through to Grade 7+). An eight-year-old who now reads chapter books, but whose reading level was set years ago, will find the replies patronising — and nobody moves that setting but you, so check it.

The audience. Around eight, "can I put it online?" often starts. The answer is that you decide: nothing leaves the family except through the parent PIN, by a link you send or a post to the community feed. Say yes or no on the merits of the tower game, not on whether they could do it themselves, because they cannot.

When to steer them elsewhere

If your eight-year-old keeps asking how the tower decides which enemy to shoot, that is a kid asking to see the mechanism, and Wonderkit does not show it — there is no code on screen to read. Scratch would show them, and they are ready for it.

If they have started asking about Roblox Studio, that is early. The Roblox Studio comparison explains why a real engine with a scripting language belongs to kids about ten and older, and why an eight-year-old who opens it is likely to close it again.

And if they are still sounding out the AI's longer questions, the seven-year-old page is written for a kid who still wants company at the keyboard. By nine the asks change again — the game must be good, not merely exist — and the nine-year-old page is about that. Account, price and sharing, in one place: the parent's guide.