Scratch vs MakeCode vs P-Blocks: which block-coding platform should you choose?

Block-based programming stopped being an educational experiment years ago. Today it's the standard entry point into code for almost anyone from age 7, with no syntax errors to get frustrated over before reaching your first idea. The question isn't whether to use it anymore — it's which of the many options to pick.

We compare the three that show up most in schools and at home: Scratch (the pioneer), Microsoft MakeCode (the bridge to hardware) and P-Blocks (the option built around environmental data).

1. Scratch: the king of animation

Created by the MIT Media Lab, Scratch has the largest community in the world and an interface any 8-year-old masters in half an hour.

Where it wins: animations, 2D games, interactive stories. Nothing else competes with it on this ground.
Where it falls short: connecting external hardware requires Scratch Link, a bridge program that tends to cause problems on centrally managed school networks. It's not its natural territory.

2. Microsoft MakeCode: the industrial workhorse

MakeCode became popular alongside the micro:bit board. It has a solid built-in simulator and lets you move from blocks to Python or JavaScript, seeing the actual code instantly.

Where it wins: hardware integration and the visual transition from blocks to text-based code, very useful for anyone ready to make the jump to "real" programming.
Where it falls short: the interface is more technical than creative. In primary school, especially in the first sessions, it's harder to keep students hooked than with Scratch.

3. P-Blocks: the data-focused option

Built by POWAR STEAM, P-Blocks takes Scratch's visual simplicity and adds native Bluetooth connectivity with sensors, straight from the browser, with no bridge software to install. A typical block reads like this: "read humidity sensor" connected to "if less than 30, turn on red LED" — the same conditional logic as MakeCode, but designed from the first block to work with real-world data, not just on-screen movement.

Where it wins: data science and environmental projects. Reading a real sensor and plotting it in seconds, with nothing to configure.
Where it falls short: its community is much smaller than Scratch's, and it's not designed for video games or animation — if that's what you're after, it's not the right tool.

If you're choosing as a family, not as a school

If your child wants to create stories and games, start with Scratch: it's free, needs no hardware, and the community has thousands of projects to draw inspiration from. If you already have a micro:bit at home, MakeCode makes use of what you've got. If what hooks them is measuring things in the real world — the plant, the balcony, the fish tank — P-Blocks is the most direct option.

Honest conclusion

There's no single answer. For video game design and digital art, Scratch. For electronic robotics with motors and servos, MakeCode. For combining programming with environmental data science and sustainability, P-Blocks puts the least friction between the sensor and the chart.

To see P-Blocks applied to a real project from start to finish, the article on the classroom acoustic traffic light programs the conditional logic step by step.

Found this useful? Share it:

← Back to Blog

We wrote this article with AI assistance to move faster, and reviewed it by hand before publishing: technical data and links are verified by our team. We're sharing this because it feels like the honest way to do it, not because a law requires it.