From arrow cards to Scratch

There is a reasonably well-worn path from a floor robot to writing code, and each step exists because the previous one has run out of room rather than because a child has reached an age. Moving early is the common mistake and it usually ends the interest.

Here is the sequence and the signals.

Step one: physical sequences

Arrow cards or buttons, a grid mat, and programs of five to fifteen steps. The idea being learned is that a plan made in advance produces a predictable result, and that a wrong result can be traced back to a step.

This is where nearly everybody should start, including older children who have never programmed.

The signal to move on

The child writes programs longer than the robot can store, or starts asking whether it can repeat something rather than entering it again. Both mean the concept has landed and the tool is now the limit.

Boredom is not the signal; frustration with the tool is.

Step two: loops and conditions

Repeat blocks, and then “if something happens, do this”. Conditions are a genuine step up because the program is no longer a fixed sequence — it behaves differently depending on the world.

Robots with sensors are what make this concrete: follow a line, stop at an obstacle, turn at a colour.

Step three: block programming on a screen

Scratch and its relatives put the same ideas on a screen with drag-and-drop blocks. The advantage is that programs can be far longer and can be saved; the cost is that a device is now required and the immediacy is reduced.

Moving here before conditions are understood usually produces a child who enjoys the animations and does not write programs.

Why blocks rather than typing

Blocks remove syntax errors entirely. A child working in text spends the first month fighting missing brackets and misspelled keywords, which teaches nothing about programming and is thoroughly demoralising.

Blocks let the structure be learned before the typing.

Step four: blocks driving real hardware

This is where the kits on our middle shelf sit — a controller with motors and sensors, programmed in a block environment. It keeps the physical feedback of the floor robot and adds the program length of a screen.

For many children this is where it stops being a toy and becomes an interest.

Step five: text, usually Python

The transition to text is easiest when the child already knows what they want the program to do and is only learning how to say it. Kits that support both blocks and Python on the same hardware make this step much gentler, because the program does the same thing before and after.

Where a kit supports both, we note it on the listing.

How long each step takes

Months rather than weeks, and it is extremely uneven. A child can spend a year happily on floor robots and then move through blocks in a fortnight. Nothing about that is a problem.

Pushing the pace is the reliable way to end the interest.

The role of an adult

Mostly to resist. The strongest temptation is to fix the program before it runs, and that removes the only part that teaches anything. Asking “what do you think it will do?” before pressing go is worth more than any explanation.

The same applies at every step on this list.

What to do between steps

Challenges rather than new kit. Get the robot to draw a square, to visit three points in order, to solve a maze somebody else built. A kit with an activity guide is worth a great deal here.

Buying the next thing is usually premature.

Where hardware helps and where it does not

Physical robots keep the feedback immediate and are excellent for the first three steps. After that, a screen and a keyboard genuinely are the right tool, and additional hardware is a preference rather than a need.

The kits worth buying at that stage are the ones that add sensors and motors, not the ones that add characters.

Where to look

Screen-free coding robots for steps one and two, app and remote robots for step three, and robot building kits and coding learning kits for four and five.

The counter is happy to talk through where a specific child is — the number is on the contact page.

When a child stops and does not come back

Interest in this area is rarely lost gradually; it usually stops at a specific obstacle. The common ones are a step taken too early, a kit whose setup defeated everybody, and a period where an adult started correcting programs before they ran. Each of those is recoverable, and the recovery is nearly always to go back a step rather than forward.

A child who stalled on block programming will often happily return to a floor robot and build something genuinely ambitious with it, and that rebuilds the confidence the screen took away. There is no rule that says progression is one-directional, and the children who end up going furthest are frequently the ones who were allowed to go back for a while.