If you have looked at the price of a “coding robot” for toddlers recently, you will know why this article exists. Somewhere between the £90 programmable caterpillar and the £250 build-your-own-computer kit, a lot of parents quietly decide that coding is something their child will pick up at school, and close the tab.
The thing is, you do not need any of it. The skills that matter at three, four and five are the thinking skills underneath the code, and those can be taught with a cereal box, a bit of masking tape and the phone you already own. Here is how to do it without spending a fortune, and where a small amount of money goes furthest if you do decide to spend it.
What “coding” means for a four-year-old
Nobody is suggesting a preschooler learns Python. At this age, coding means three things: putting steps in order (sequencing), noticing when something happens again and again (patterns and loops), and working out what went wrong when it does not work (debugging). Children who are comfortable with those ideas find the real thing far easier when it turns up in Year 1, which in England it does, because computing has been part of the national curriculum from the very first year of primary school since 2014.
So the goal is not a head start on syntax. It is a child who already thinks like a problem solver by the time a teacher hands them a floor robot.
Completely free: the kitchen-floor version
The cheapest coding lesson in the world is a grid of masking tape on the floor and a teddy. Your child gives the teddy instructions, one step at a time: forward, forward, turn left, forward. You move the teddy exactly as told, including when the instruction is wrong and teddy walks into the sofa. That moment, when they laugh and say “no, I meant the other way,” is debugging. It costs nothing and it is the single most useful activity on this list.
Once they have the idea, add arrows drawn on scrap paper so they can lay out a whole “program” before running it. Then hide a biscuit somewhere on the grid and ask them to write the route. You have just taught algorithms.
Other free favourites: getting them to give you step-by-step instructions to make a jam sandwich, and following them literally (spreading jam on the outside of the loaf is a lesson they will remember). Sorting the washing by colour then size teaches conditions. Clapping patterns and asking “what comes next” teaches loops. None of it involves a screen.
Free on a screen: what is actually worth the download
When you are ready for an app, start with the free ones. ScratchJr, developed by MIT and Tufts, is free on tablets and lets children aged five to seven snap picture blocks together to make characters move and talk. Hour of Code activities, run by Code.org, are free and browser-based, with plenty of options for early readers. Your local library may also run a free Code Club, and many primary schools open theirs to younger siblings.
The limitation with free tools is that they tend to be a collection of activities rather than a path. Your child will do the same three things for a month and then drift. That is fine for a first taste. It is less fine if they have caught the bug and want more.
Where a little money goes a long way
This is where a lot of parents get it wrong. The instinct is to buy a physical kit, because it looks like a proper present and comes in a box. But a £100 robot does one thing, and most of them are in the loft by the second birthday after purchase.
A subscription to a structured coding platform, by contrast, grows with the child and usually costs less than a single week of holiday club. The ones worth paying for share a few features: a proper progression from pictures to real typed code, hints built into the lessons so you are not the tech support, and a parent view so you can see what they have done without hovering.
For the very youngest, look for a course built for children who cannot read yet. CodeMonkey Jr., for example, is a block-based course for ages four and up in which children guide a monkey to bananas by arranging picture blocks, and it sits on the same platform as the later courses, so when they are eight and ready for typed code there is nothing new to buy or learn. Most platforms of this kind offer a free trial, so try before you commit, and check whether a yearly plan works out cheaper than monthly, because it almost always does.
One more money-saving tip: if a grandparent is asking what to get for a birthday, a year’s subscription is a far better answer than another plastic toy, and several platforms sell gift subscriptions for exactly this reason.
Things not to buy (yet)
A child’s laptop. A shared family tablet or an old phone with the SIM removed is plenty until they are well into primary school.
Any kit aimed at “ages 8+” for a four-year-old. You will end up building it yourself while they watch, which teaches them that coding is something grown-ups do.
Anything with a monthly fee for a subject your child has not yet shown any interest in. Do the free version first. If they ask for more, then spend.
Keeping it cheap and keeping it going
Short and often beats long and rare. Ten minutes of teddy programming after tea, a few times a week, does more than an hour on Sunday.
Let them be the teacher. Ask your child to explain to you (or to the dog) how the program works. Explaining is where the learning sets.
Mix screen and no-screen. If they did an app today, do the tape grid tomorrow. The ideas are the same, and the switch stops it feeling like just more screen time.
And do not turn it into homework. The moment it becomes something they have to do, it stops being play, and at this age play is the whole point.
Coding, it turns out, is one of the few early-years skills where the expensive version is not the better version. The masking tape is the better version. Save your money for the wellies.
