Skip to content

guide · coding_for_preschoolers

Coding and robotics for preschoolers, and what it actually is at three to six

A child who cannot read yet can still program, but not in the way the word suggests. Here is what is really being taught, how to judge a class in one visit, and an honest answer on whether starting this early helps.

14 of the 22 schools in this directory state that they accept children aged five or under, and the youngest stated starting age among them is 3. So the classes exist and there are plenty of them. The harder question is what a child that age is actually doing in one, and whether it is worth the money and the Saturday morning.

This page is written for that decision. It is not written to talk you into a class or out of one.

What coding means before a child can read

Most preschoolers cannot read fluently. That single fact settles what is possible, because typed code is out of reach and so is anything that depends on reading instructions from a screen.

What is left is the part underneath the typing, and it turns out to be the part that matters most. Programming is deciding on a sequence of steps in advance, then finding out whether the sequence did what you expected. A four year old can do that with a robot and four arrow buttons. There is no reading involved and it is genuinely the same mental move a programmer makes.

So the useful way to think about preschool coding is not that it is a small version of a real coding class. It is one specific skill, sequencing, taken out and practised on its own.

What the common tools are really for

Singapore centres reach for the same handful of things at this age. They are not interchangeable, and knowing which one a class uses tells you a lot about what your child will spend the term doing.

Screen-free floor robots

A small robot with arrow buttons on its back. The child presses a sequence, forward, forward, turn, then presses go and the robot runs the whole sequence at once. Nothing is read and nothing is typed. This is the closest thing to real programming a four year old can do, because the child has to decide the whole plan before anything happens.

Picture-block apps such as ScratchJr

Built for the age group that cannot yet read. The blocks are pictures rather than words, and they snap together into a sequence that makes a character move or speak. It is a genuine step up in complexity from a floor robot and usually suits the older end of preschool.

Building and mechanism kits

Bricks, gears, motors. Often sold under the robotics heading, and worth a moment of care, because building a motorised model is engineering rather than programming. It is valuable, and it is not the same thing. Ask whether the child ever tells the model what to do, or only assembles it.

Tablet games marketed as coding

A large category and a mixed one. Some teach sequencing honestly. Others are puzzle games with a coding label, where the child taps until something works. The test below separates them, and it takes about a minute to apply.

The one thing that separates a real class from a play session

There is a single test, and you can apply it while standing at the back of a trial lesson.

Does the child say what will happen before it happens?

A child who presses buttons, watches the robot move, laughs, and presses again is enjoying themselves and learning that actions cause effects. That is worth something at three. It is not programming.

A child who says "it will stop on the red square", presses go, and then finds out whether they were right is programming. The prediction is the whole thing. Everything else at this age is packaging.

The question that settles it in one visit: "Before the robot moves, does my child tell you where it will end up?" If the answer is no, the class is teaching cause and effect, which is fine, but it is not teaching programming.

How to tell a good preschool class

  • The child predicts before pressing go. The teacher asks where the robot will stop, and the child answers, and only then does anyone press the button. That single habit is the whole subject in miniature. It is also the first thing to disappear when a class is running behind.
  • Being wrong is part of the lesson, not a failure. The robot goes to the wrong square, the child works out which step was wrong and fixes that one step. A class that quietly corrects the sequence for the child has removed the only part that was teaching anything.
  • Sessions are short and the child is standing up. This age concentrates in short bursts and learns through their hands. A preschooler sitting at a screen for an hour is not a sign of a serious programme, it is a sign of one designed for older children and sold downward.
  • The centre can say what changes between four and six. Two years is an enormous gap at this age. If the four year olds and the six year olds are doing recognisably the same activity, the class has been built for one age and stretched to fill the others.
  • You are told what your child cannot do yet. A centre being straight with you about the ceiling at this age is a better sign than one implying there is no ceiling.

Does starting at four beat starting at seven

This is the question most parents are really asking, so here is our straight answer: for coding specifically, mostly no.

A seven year old reads, counts reliably, and sits with a problem for longer. Those three things are exactly what the early material needs, and a child who has them covers in a few months what a four year old covers in two years. Starting at four does not put a child two years ahead. It puts them through the same doorway more slowly.

That does not make an early class pointless, and we are not saying do not enrol. A preschooler who enjoys a floor robot on a Saturday is having a good time doing something with more thinking in it than most alternatives, and enjoying it early makes a child more willing to come back to it later. Those are real reasons.

They are just different reasons from the one usually being sold. Buy it because your child enjoys it, not because it buys them a lead. If the budget is tight, the honest advice is that this is the age to spend the least, and that a set of picture blocks or a floor robot at home does most of what a term of classes does.

What to do at home instead, or as well

Almost all of this works without a centre, and it works in ten minute stretches rather than hour long ones.

Give instructions in sequences and let your child give them back. Four steps to the kitchen, said before anyone walks. Ask what happens if we swap step two and step three, then try it and find out together. Get it wrong on purpose sometimes and let them catch it, because spotting the broken step is the skill, not following the correct one.

When your child can hold four or five steps in their head and predict the result, they are ready for a floor robot or picture blocks, and later for Scratch, which is where the path actually opens up. Our guide to the programmes sets out what suits which age after that.

Things you may be told that are worth questioning

  • "Starting early gives your child a head start in coding." Be careful with this one, because it is the sentence the whole category is sold on. A child who starts at seven, when reading and counting are steady, moves through the early material far faster than a four year old does. Whatever head start exists is smaller and shorter-lived than it sounds, and nothing done at four is still an advantage at twelve.
  • "It builds logical thinking and helps with maths." Sequencing genuinely is a thinking skill and practising it is not wasted. Where to be cautious is the leap from that to measurable gains in school subjects. If a centre offers that claim, ask what it is based on. It is usually offered without a source.
  • "This prepares them for the school curriculum." It does not, because there is nothing at this age to prepare for. Compulsory schooling in Singapore begins at Primary 1, and the Computing syllabuses that specify actual programming are secondary and pre-university. For a four year old that is roughly a decade away.
  • "Our robotics programme is for ages three and up." 13 of the schools in this directory that accept children aged five or under list robotics, so the offer is real and common. What varies is the content. At three the session is usually building and pressing, at six it can be genuine sequencing. The age on the brochure tells you who may enrol, not what is taught.

In short

Coding at three to six is one skill, sequencing, practised with robots and pictures instead of words. A good class has the child predicting before pressing, treats mistakes as the lesson, and is honest about the ceiling. A weaker one has the child pressing buttons and watching.

Starting early is a fine thing to do for enjoyment and a weak thing to buy as an advantage. If your child likes it, that is reason enough. If they do not, nothing has been lost, and seven is a better starting line than the brochures admit.

Schools stating they take children aged five or under

Read straight from the directory, with each school's own stated age range. It is not a ranking and it is not an endorsement. Confirm the age range with the school, since what a centre accepts and what it teaches at the youngest end are often different.

Looking for a class for a preschooler?

14 of the 22 schools listed here state that they take children aged five or under. Ask each one the prediction question before you book a term.

Browse the full directory