Making Loopz’s first lesson accessible to a four-year-old was the hardest design work we did. Simplicity isn’t the absence of effort. It’s the result of removing everything non-essential. We stripped cognitive load, deleted decorative clutter, and reduced the opening to a single clear idea a pre-reader can grasp without help.
The first lesson in Loopz is embarrassingly simple. Pip stands at the start of a straight path, three tiles long. The only command on offer is Step. The solution is: Step, Step, Step.
Most children finish it in under thirty seconds. By a wide margin, it is the easiest thing in the entire curriculum.
It is also, we are convinced, one of the most important things in it.
The most important lesson in Loopz is the one your child will finish in thirty seconds.
Why starting simple is harder than it looks
The temptation in educational game design is to front-load everything. You want a strong first impression. You want to show off the range of what the product can do. You want to look impressive.
That instinct is exactly wrong.
A child's first encounter with any new system should leave them feeling capable, not swamped. The moment of "oh, I get how this works" is fragile. Pile on too many elements and it simply never arrives. The child closes the app a little confused, and they do not come back.
Lesson 1 of Loopz has exactly one thing to learn: there is a character, there is a command, the command moves the character forward. That is all. Any child who can read the word "Step" and press a button can do it, and walk away feeling like they just did something clever.
Cognitive load theory, in practice
The principle underneath all of this is cognitive load theory, developed by the educational psychologist John Sweller. The core idea: working memory has a hard limit. When a learning experience demands more than that limit, learning does not slow down, it stops. Not because the child isn't bright, but because no brain can process more than working memory holds.
For a four or five-year-old meeting a new digital world, working memory is already half-spent just on the novelty. The navigation, the colours, the sounds, the unfamiliar words, all of it burns cognitive fuel before a single concept has landed.
So World 1, Garden Path, is built with something close to radical simplicity. One character. One path. One command. No distractions. Every choice in the visual design pushes attention toward the one thing that matters: the relationship between the block you place and the movement that follows.
What we removed
The first prototype of Garden Path had more going on: background scenery, animated clouds, little creatures wandering the edges. It was charming. And in playtesting, children ignored the puzzle completely and tapped the decorations for minutes on end.
So we took almost all of it out. The path is clean now. The goal is plainly visible. Pip looks up at you with curious, waiting eyes. There is nothing to press except the blocks.
This was painful. Deleting things you lovingly made always is. But the jump in attention and completion was immediate. Children who had been wandering off suddenly finished the level.
Good design for young children is mostly subtraction. The hard part isn't deciding what to add. It's having the discipline to take things away.
One new idea per world
Garden Path teaches sequencing. Nothing else. There is no looping in World 1, no decision-making, no obstacles to fiddle with. The whole world exists to build a single mental model: to reach a goal, you plan the right sequence of steps in advance and run them in order.
That rule, one new idea per world, runs through the entire curriculum. The worlds that follow each add a single new concept, loops, patterns, state change, decision-making, conditionals, introduced one at a time and never two at once. Each world assumes mastery of everything before it.
Holding that line, resisting the urge to cram in more, trusting that a child who truly owns sequencing will pick up loops faster for having waited, is a constant act of discipline.
Testing with real children
We playtested World 1 with children from four to seven. The most valuable thing we learned was not what confused them. It was what delighted them.
One five-year-old, after finishing Lesson 3, a slightly longer path with a turn in it, looked up from the screen with an expression we have been chasing in every lesson since. Pure, uncomplicated pride.
"I made him do it."
That sentence is, in four words, the entire design brief for Loopz. The child is the one who made it happen. Not the app, not the animation. The child, who had a plan, ran it, and watched it work.
Everything we have built since has been in service of that one moment.
Common questions
Can a 4-year-old really learn to code?
They can learn the thinking behind it. A four-year-old can’t read syntax, but they can follow a sequence, predict what a step does, and fix a simple mistake. World 1 is built around exactly those pre-reading skills.
How do you make coding accessible to pre-readers?
By removing reading from the critical path. Loopz World 1 uses clear visuals, one idea at a time, and minimal on-screen clutter, so a child who can’t yet read can still understand what to do and why.
Why is the first lesson so simple?
Because the first lesson’s job is confidence, not challenge. If a four-year-old succeeds and understands why, they’ll keep going. Front-loading difficulty is how you lose a young learner before the real learning ever starts.