A five-year-old is sitting with a tablet, dragging coloured blocks into a row. After each one she looks up: Is that right? Another block, another look up. Twenty minutes later the puzzle is finished and there is a small animation, and if you ask her what she just did she says, "I did the puzzle." She could not tell you why the character turned left. She was reading your face, not the screen.
Her seven-year-old brother does the same puzzle in four minutes, gets one wrong, says "oh, it needs to turn first," and fixes it without looking at anyone. Same activity, same family, same amount of adult help offered. One of them was ready and one of them was doing something else that happened to look similar.
Readiness is not an age. It is a small stack of very ordinary skills, and you can check for all of them at your kitchen table in about ten minutes.
The four things that have to be in place first
Almost every children's coding tool, whatever it is built on, quietly assumes four abilities. When one of them is missing, the child is not learning to code badly — they are not able to engage with the activity at all, and the session becomes a guessing game.
| Prerequisite | How to check it in two minutes | Usually in place around |
|---|---|---|
| Follows a three-step instruction, unprompted, in order | "Put your cup in the sink, get your shoes, and wait by the door." Say it once. Do not repeat it. | 4 to 5 for familiar steps; later for unfamiliar ones |
| Enough motor control for the interface | Can they drag a small icon onto a target and let go where they meant to? Ten tries, count the misses. | 3 to 4 on a touchscreen; often 6+ for accurate mouse work |
| Enough reading for the interface, in the interface's language | Ask them to read the buttons aloud. If they are guessing from icons, that is your answer. | Around 6 to 7 in a first language; considerably later in a second |
| Can be told "no" by a machine without it becoming personal | Watch them lose a simple game. Do they try again, or do they leave the room? | Very variable; commonly steadier by 5 to 7 |
The third one matters far more outside English-speaking countries than most tool makers acknowledge. A child in Jakarta or Lisbon or Cairo who reads perfectly well in their own language may be facing an English menu bar, and the reading load stops being about reading and starts being about vocabulary they have never met. That child is ready. The interface is the obstacle.
What ready actually looks like
Forget the marketing checklists and watch for these, which are all things you can see from across the room:
- They predict before they press. "This one will make him go up." Even a wrong prediction is the signal — it means they believe the screen follows rules.
- They work for five or more minutes without an adult within reach. Not silently and not perfectly. Just not turning around every ten seconds.
- They notice a mistake before you say anything. A small "oops" and a hand reaching to change something.
- They can narrate it afterwards. Roughly, in their own words, badly. "He went the wrong way so I moved that one."
- They come back to it a second day without being asked. This is the strongest signal of the five, and the easiest to overlook.
You do not need all five. Three of them, on more than one occasion, is plenty to carry on.
What "too early" looks like in practice
It rarely looks like failure. It usually looks like a child completing things while learning nothing, which is why it can go on for months.
- Random tapping with a success rate. They try everything quickly until something works, then move on. The puzzle is solved; the child treats it as luck, because for them it was.
- Every step needs an adult. Not "help me with this bit" — a check-in before each individual action.
- Real distress at being wrong. Tears, "I'm stupid at this," pushing the tablet away. A wrong answer should be mildly annoying, not wounding.
- No account of what happened. Ask what they did and you get a shrug or a description of the reward animation.
- You are doing it. The hover-and-solve, where you point at the right block often enough that the child's job becomes reading your finger.
The cost of pushing through this is not lost time. It is that the child learns an association: this thing makes me feel stupid and makes the grown-up impatient. That association is much harder to undo later than any amount of missed head start.
Not ready, or a badly matched tool?
These look identical from the outside, and parents very often conclude "my child isn't ready" when the honest answer is "this particular product does not suit this particular child." Change one variable at a time:
- Read the words aloud for them. If the whole thing unlocks, it was never a thinking problem. It was a reading or language problem.
- Swap the input. Touchscreen instead of mouse, or a mouse instead of a trackpad. Some children who look hopeless are simply losing the drag.
- Turn off timers, scores and streaks if the tool allows it. A meaningful number of otherwise ready children fold completely under a visible countdown.
- Drop two difficulty levels. If they are fluent and cheerful at the easier level, you had a difficulty mismatch, not a readiness problem.
- Ask the same kind of question away from the screen. "Tell me exactly how to get from here to the front door." If they can plan out loud but not on the screen, the screen is the problem.
Two more tells. If the child handles other apps of similar complexity without trouble, it is the tool. And if the frustration begins at the same moment every single time — always the drag, always the menu, always the timed round — that is a design mismatch, not a developmental one. Genuine unreadiness is diffuse. It is spread across the whole session, not concentrated in one recurring five seconds.
When a child bounces off it
Stop the session before it turns sour, say something unremarkable like "let's do something else," and then leave it properly alone. Eight to twelve weeks is a reasonable gap. Retrying every weekend is the common mistake; it converts a neutral non-event into a running argument, and children remember the argument.
Better than a calendar date is a trigger. Try again after something has changed: reading has taken off, they have started a new school year, they have got noticeably better at board games with rules. When you do retry, do not announce it as a return. Just have it available.
In the meantime, the prerequisites grow perfectly well through ordinary life — these are not coding in disguise, they are the skills underneath it:
- Cooking from a recipe, where the order genuinely matters and skipping a step is visible in the result.
- Board games with rules the child has to apply themselves, including the ones that say "if this, then that."
- Building from printed instructions, which is mostly the skill of not jumping ahead.
- Games where losing is normal and frequent, which is how tolerance for being wrong is actually built.
Does starting at four beat starting at eight?
Honestly, in almost all cases, no.
An eight-year-old starting from zero arrives with reading, more working memory, a longer attention span, and the ability to hold a plan in mind while carrying it out. In practice they cover in a few weeks what a four-year-old covered in a year, and the four-year head start disappears. There is no evidence of a closing window here of the kind that exists for first-language acquisition. Coding is not like that.
What early exposure can give, when it is genuinely enjoyable, is familiarity and the absence of fear — a child who has never thought of this as a hard, serious, adult subject. That is worth something. It is not a head start, and it evaporates entirely if the early sessions were tense.
So the trade is lopsided. Starting early when the child is ready and enjoying it costs nothing. Starting early when they are not costs you the child's willingness to try again, which is the only thing that actually matters at this stage. Whatever you use — Kid Genius World included — the readiness question comes before the tool question, and it is answered by watching your own child for ten minutes, not by a recommended age on a box.