Scratch, Blockly and MakeCode are all block-based coding tools: your child drags puzzle-piece blocks together instead of typing lines of text. The difference is what each one was built to do. Scratch is aimed at on-screen stories and games, MakeCode is aimed at physical boards and sensors, and Blockly is the engine that many other block editors are built on top of. Once you know the target, the choice gets simple.

Scratch: built for stories, games and animation

Scratch, from MIT, is where most children start. The blocks control sprites on a stage, so a child can move a character, play a sound, or keep score. Under the surface it teaches the real ideas that every language shares: loops, events, variables and conditionals. There is nothing to buy and nothing to install, because it runs in a browser.

For a first taste of coding, roughly ages 8 to 12, Scratch is hard to beat. The trade-off is that Scratch lives on the screen. It will not drive a motor or read a temperature sensor, so it is a poor fit if the goal is robotics.

Blockly: the engine, not the app

Blockly is a Google library for building block editors. On its own it is not a product a child sits down to use. It is the toolkit developers use to make one. Many of the block interfaces you meet, including plenty of hardware and classroom tools, are Blockly underneath.

Why does this matter to a parent? Because knowing a tool "uses Blockly" tells you the look and feel (you drag blocks) but not the purpose. Two Blockly-based tools can do completely different jobs, one making animations and another controlling a robot arm. Judge the tool by what it targets, not by the engine it runs on.

MakeCode: blocks that talk to hardware

MakeCode, from Microsoft, connects blocks to physical devices: small microcontroller boards with LEDs, buttons and sensors. You build a program in blocks, then flash it onto a board that runs on its own, away from the computer. Most of the time it also lets your child flip between blocks and text, usually JavaScript or Python, which makes it a natural bridge as they grow. This is the category that matters when the goal is robotics rather than animation.

Our own sheenbot∞ board sits in this space. You can write block code for it and watch it run in a browser simulator before touching any hardware, which is handy when data or devices are tight. Try the block canvas to see how physical-computing blocks behave on a virtual board.

Choose by goal, not by brand

The brand name matters far less than the fit. All three teach the same core concepts, so a child who learns loops in Scratch already understands loops in MakeCode. Match the tool to what your child actually wants to make:

• Goal is stories, games or art: start with Scratch.
• Goal is robots, sensors or wearables: use a hardware editor like MakeCode, or the block coding for the sheenbot∞ board.
• Child is ready for text: pick a tool that shows blocks and JavaScript or Python side by side.
• Budget is tight: start on-screen, since simulators cost nothing and teach the same logic.
• Younger than 8: begin with simpler icon-based blocks before full Scratch.

The takeaway

Do not agonise over which block tool is "best". Match the tool to what your child wants to build, and let them move between tools as their goals change. The skills carry across, so nothing is wasted. If you would like a guided start, our academy runs block-coding classes in Cape Town, and you can book a free trial lesson to see which style suits your child before you commit to anything.