Coding robots locked to proprietary one-company apps?
Our position, and other voices worth reading before you decide.
Our position
If the robot will not run in MakeCode, Scratch, Blockly, Swift Playgrounds, Python, or Sphero Edu - if its only coding interface is a branded app from a company you have not heard of - skip it.
The entire useful life of the robot is the life of that app. When the company stops updating, the robot stops working. For a classroom investment that has to survive five years of iOS and Android updates, that is a dealbreaker.
Other voices
Reputable sources worth reading before you decide. Labels reflect our honest read of each source's general stance, not direct quotes.
Sphero Edu (multi-robot platform)
Broadly agreesSphero builds its classroom case around a single app that programs every Sphero in the lineup for a decade. That model - one ecosystem, many robots - is what schools should look for, not a one-robot one-app silo.
Microsoft MakeCode
Broadly agreesMakeCode is a free, browser-based coding environment that supports micro:bit, LEGO Mindstorms, Minecraft, and more. A robot that works with MakeCode inherits a huge free curriculum ecosystem. A robot that does not is isolated.
Amazon coding-robot reviews (mixed quality)
Nuanced / mixedCheap robots with proprietary apps often review well on day one because the app actually works when it ships. The problem shows up at month six when iOS updates break the app and nobody at the company fixes it. Read recent reviews, not launch reviews.
Some classroom teachers (budget-first)
Pushes backThe counter-argument is that $40 a robot with a proprietary app is cheap enough to be disposable - replace the whole fleet every two years and you are still ahead. There is a version of that argument that works, but only if the school has a guaranteed replacement budget every two years. Most schools do not.