Robots for Education: So Many Choices!

The sheer number of educational robots available for teachers today can be overwhelming.

It’s hard to differentiate between so many products, even for someone who spends as much time with these devices as I do. I don’t consider myself an expert on all of these devices; they’re so new, no one is an expert, yet! But I’ll tell you about those I’ve seen in action, with a focus on the most popular choices.

Who this is for

This article is intended for the teacher who has decided that they would like to introduce robotics in the classroom. There is a larger argument to be had as to whether your classroom needs robots at all — but that is an argument for another blog post.

It’s also for parents who want to bring a robot into the home for learning purposes. We’ll mention which robots are balanced towards play, and which towards lesson planning.

Coding: blocks vs. text

Below, you’ll see us distinguish between “blocks based coding” (sometimes called “Scratch-style”, since the popular platform Scratch uses blocks) and “text-based coding”.

Blocks-based code

Text-based code

As you can see, blocks help get younger students into coding because they snap together and show their function visually. Text based coding is what we usually think about when we imagine programming; with text coding, however, beginners are more likely to get stuck on tricky syntax like parentheses and commas.

A word about Bluetooth

All of these robots are controlled wirelessly via Bluetooth. As you probably know from your own adventures with Bluetooth speakers and headsets, Bluetooth works perfectly… until it doesn’t. Nothing is worse than having to postpone a lesson because your tablets aren’t connecting to your robot.

Unfortunately, there’s no good answer to this problem. One idea: when things go wrong, invite students to troubleshoot it with you. Our world is full of technologies that don’t quite work right all the time, and troubleshooting is a crucial skill for students to practice.

Sphero SPRK+

Website: sphero.com/educators

Price: USD $130; classroom packs of 12 Spheros run $1200–1800, depending on model and accessories
Age, suggested by company: 8+
Age, suggested by me: 8–13 (grades 3–8)
Platforms for control and programming:

• iPhone/iPad (iOS 9+)
• Android phones/tablets (Android 4.4.2+)
• Chromebook (Chrome OS 50+)

Coding style: both blocks and text

Sphero is a cool robotic ball, about the size of a tennis ball, that can be programmed using a Scratch-like blocks language or with Javascript text coding.

There are several different types of Spheros that range in mobility and are at times marketed as educational products, and at other times as a toy. For the purposes of this post I will be speaking about the (confusingly named) Sphero SPRK+ (pronounced “spark plus”) as this is the model most commonly used in educational settings.

Pros:

• tablet app controller and programming environment are well designed
• no assembly required: can use it right away
• indestructible and waterproof. I have seen Spheros survive being thrown across a room
• great platform for sharing projects
• well-constructed in-app tutorials

Cons:

• Macs and PCs not supported
• no assembly means students know very little about its construction or workings
• text-based coding is supported on tablets, but using a tablet to type code — instead of a real laptop/desktop keyboard — can be a miserable experience.
• large space required. These little balls are fast! Students will be running around trying to catch up. You will find yourself repeatedly saying “No more than 50% speed!” to your students
• drive mode: allows the student to play with Sphero like any remote control car. This has little educational value… and, of course kids love it. That means repeatedly saying “Drive mode is not allowed during class time!”

Overall, I am a fan of the Sphero SPRK+ because the app is built so well and the hardware will last several years in any classroom because of its durability. Kids love it, but I do feel it transitions from educational tool to toy too easily.

There are also two other models of Sphero:

• Sphero Ollie (USD $100): has a hoverboard-style feel to it, and is a lot of fun to drive around. A good choice for the home, but not as good a match for educational use as the SPRK+
• Sphero Mini (USD $60): about the size of a ping-pong ball, it runs the same main education app as the SPRK+. However, the motor is weaker, the body is not as durable, and it isn’t transparent, so kids can’t see its workings as it rolls around. Consider only if the SPRK+ price is a deal-breaker.

Who it’s for (SPRK+): teachers of grades 3–8 with access to tablets or Chromebooks, looking for a quick way to add robotics to their classroom

Lego Mindstorms EV3

Website: lego.com/en-us/mindstorms/about-ev3

Price: USD $350
Age, suggested by company: 10+
Age, suggested by me: 9–15 (grades 4–10)
Platforms for control and programming:

• Mac (OS 10.6+)
• PC (Windows 7+)
• Chromebook (Chrome OS 50+)
• iPad (iOS 8+)
• Some Android tablets

Note that iPhones and Android phones can use some simple Mindstorms control apps, but not programming apps.
Coding style: blocks

Lego has been in the robotics industry for quite some time, through a partnership with the MIT Media Lab. The EV3 is their current marquee product.

Physically, robot designs are assembled from a mix of traditional Lego blocks and special Mindstorms parts like motors, servos, sensors, and a large central minicomputer block.

In terms of software, it works with either the Mindstorms iPad/Android app, or software downloaded to any Mac, PC or Chromebook computer. Both feature essentially the same blocks-based coding interface.

Pros:

• software is supported on a wide variety of platforms
• also compatible with many 3rd-party applications. The popular Scratch kids coding website promises that a Lego EV3 feature is “coming soon”
• constructing these robots themselves helps students understand their mechanics

Cons:

• coding interface feels a bit old and clunky compared to newer apps
• lacks support for text-based coding
• high cost means fewer kits per student. Teachers may additionally feel the need to buy even more LEGOs to build with
• the large, complex LEGO builds can be a time-consuming distraction, and hard to do as a group
• LEGO blocks… everywhere! I found myself scouring the floor for blocks at the end of class so the custodian wouldn’t sweep them up
• Macs and PCs not supported

Though Mindstorms EV3 can offer a deep and rewarding robotics design experience, I am skeptical of recommending it to any teacher.

For older students, it lacks text-based coding. (There is a text-based third-party app, but it’s tricky to use and lacks quality lesson plans.) And the current software feels limited and unintuitive.

For younger students, I worry about the amount of tiny parts involved and the time-consuming complexity of the LEGO builds.

But there is something exciting in the works: the forthcoming Scratch 3.0 support. Being able to use the popular, powerful Scratch blocks-based language — and do away with the clunky Mindstorms app — could make the LEGO Mindstorms experience radically better. I’ll be keeping my eye this space when Scratch 3.0 is launched in fall 2018.

Who it’s for: teachers of grades 4–10 ready to invest significant time and money in a complicated but powerful robotics system

mBot

Website: makeblock.com/steam-kits/mbot

Price: USD $95
Age, suggested by company: 6–12
Age, suggested by me: 11–17 (grades 6–12)
Platforms for control and programming:

• Mac (OS 10.6+)
• PC (Windows 7+)
• Chromebook (Chrome OS 50+)
• iPhone/iPad devices (iOS 9+)
• Android phones/tablets (Android 4.3+)

Coding style: both blocks and text

mBot (officially the mBot v1.1) is a great little robot that can be assembled by the student using nuts, bolts and screwdrivers. It comes armed with plenty of sensors and can be assembled in just about any way you’d like, especially if you purchase add-ons.

Pros:

• compatible with just about any device
• all apps are well built; company’s Makeblock and mBlock software are used widely
• both blocks-based and text-based coding options
• hands-on experience! I love how students need to pick up a screwdriver to put this little robot together.
• comprehensive lesson plans. 24 projects in total.

Cons:

• runs on AA batteries, which can be an unexpected expense. A rechargeable battery is available, but sold separately.

Overall, mBot is an amazing product for middle school and high school students. The text-based code allows for complex programming and the blocks-based code allows for an easy introduction and very similar to Scratch.

There are two more advanced kits:

• mBot Ranger ($190)
• mBot Ultimate 2.0 ($350)

Both offer considerably more involved builds, and are only appropriate for experienced high school students.

Who it’s for: teachers of grades 6–12 ready for a hands-on experience, which comes with extensive curricular support.

How robots for younger kids are different

Parents and teachers know that younger kids require a different approach than older kids: more emphasis on play and exploration, more hands-on and tactile discovery, fewer screens and complex interfaces.

Here are the three robots we are seeing used most often in younger classrooms, and why teachers and parents might pick one over another.

Ozobot Bit

Website: ozobot.com/products

Price: USD $60
Age, suggested by company: 6–10
Age, suggested by me: 7–12 (grades 2–7)
Platforms for control and programming:

• iPad (iOS 7+; iPad Mini not recommended)
• Android tablets (Android 4.0+)

Coding style: can be screenless, or code with blocks

Here’s an official image from Ozobot for scale. These things are tiny!Ozobot is tiny: two can fit in your hand easily. You can program Ozobot using a mobile app or using the online blocks editor, but you can also program it just by drawing colorful lines on paper! The sensor on the bottom of the Ozobot allows the robot to follow lines, and interpret specific commands based on the color sequence the student draws.

Pros:

• no computers, no problem. Ozobot’s line coloring programming drives home computational thinking in a great way that works even when the laptop cart is reserved by another classroom and the WiFi is down :)
• loads of great printable games available
• Ozoblockly: a blocks-based programming language that can be used to wirelessly send code to the Ozobot
• no assembly required: can use it right away

Cons:

• tablet/phone only: Macs, PCs, Chromebooks not supported
• so tiny, a robot could go missing if not careful
• lacks text-based coding options, so usefulness is limited for older students
• sensitive to hand dexterity when drawing lines: the lines you draw must be precise, which can frustrate students
• no assembly means students know very little about its construction or workings

Ozobot stands out from the crowd with its line-drawing programming, which doesn’t need a screen. This does however mean you will need to keep a fresh batch of markers and plenty of paper nearby!

I have seen great success with students using Ozobots, including a special-ed group.

Who it’s for: teachers of grades 2–8 who want both screen and non-screen robotics experiences in the classroom.

Also, Ozobot Evo (USD $100) is a new offering from Ozobot aimed at slightly older students. Evo adds some bells and whistles like sensors, sounds and chat emojis. For a teacher new to Ozobot, I don’t think these justify the price, and even distract from the educational value.

Bee-bot

Website: bee-bot.us

Price: USD $80; 4- and 6-robot classroom bundles are available for $450–650

Age, suggested by company: 3+

Age, suggested by me: 3–7 (preschool to grade 2)

Coding style: Bee-bot is completely self-contained and doesn’t use a screen

Bee-bot is a cute robot designed for young students to get an early grasp on computational thinking. Bee-bot’s simplicity allows the student to program it to navigate a maze or create a story as it moves around the classroom floor or tabletop.

Pros:

• no computers, no problem. Beebot doesn’t need a screen!
• many great resources/lesson plans available, from many providers
• no assembly required: can use it right away
• free related iPhone/iPad app: doesn’t control your Bee-bot, but provides more lessons

Cons:

• runs on AA batteries; replacement battery costs can add up
• no assembly means students know very little about its construction or workings
• it doesn’t take long for students to get through all of the lessons

I recommend Bee-bots for grade 2 and lower. I think every preschool should be equipped with these things.

With simplicity come limitations. Bee-bot navigates mazes using only the 4 direction arrows on their back; it doesn’t take long for students to get through the lessons. But if a school is passing them around from classroom to classroom, they will get good use.

Note the free iPhone/iPad app (no Android, for now). The app doesn’t control your Bee-bot, but it does give you something to transition to after completing the screenless lessons.

Who it’s for: teachers of preschool to age 2 who want a simple way to introduce robotics to their young students

Also, there’s Blue-bot (USD $120), Bee-bot’s slightly older sibling, which has a transparent case, a Bluetooth connection, and a tablet-based app (for both iPhone/iPad and Android) for programming its movement. (There’s also an intriguing Blue-bot add-on called the TacTile Reader that we haven’t tried.) Our overall feeling is that Bee-bot’s strength is its simplicity; if you’re going for app-based programming, you’ll find more thoroughly developed apps with Dash (see below), Ozobot, or Sphero.

Dash

Website: makewonder.com/dash

Price: USD $150
Age, suggested by company: grade 1+
Age, suggested by me: 6–11 (grades 1–6; good for informal play as young as Pre-K)
Platforms for control and programming:

• iPhone/iPad devices (iOS 8.1+)
• Android phones/tablets (Android 4.4.2+)

Coding style: primarily blocks, but some support for text

Dash and his less expensive, immobile friend Dot are designed for younger students and are highly interactive. For the purposes of this post I will talk about the Dash robot (pictured above) and will not speak about Dot as it is not mobile and therefore limited.

Pros:

• excellent tablet apps, with sequential tutorials and a storyline
• fun, interactive and cute; when idle, Dash will talk to you
• in addition to Wonder’s blocks-based apps, can also be used with the iPad’s Swift Playgrounds app for text-based coding
• compelling accessories available, such as a xylophone, a ping pong ball catapult, and a base for attaching LEGO bricks
• no assembly required, but there is some room for creative design of attachments

Cons:

• Mac, PC, Chromebook not supported
• large; make sure you have enough storage space f you plan to get a classroom set
• more delicate than most; won’t survive being dropped
• cuteness might be a turnoff for older students
• accessories can be fiddly and flimsy
• no assembly means students know very little about its construction or workings

The Dash robot is pricey but is a great fit for students ready to move past Beebot, but not ready for mBot or LEGO Mindstorms. Sphero SPRK+ has the same level of simplicity/complexity as Dash, but Dash is more immediately appealing to younger students, and its educational apps hold the user’s hand more than Sphero’s.

That said, while I feel Dash is a great tool for home use and unstructured classroom play, I question its ability to deliver a full unit of computational learning in a classroom. The apps and the robot are incredibly attractive, but the curriculum is not as well developed.

Who it’s for: teachers of grades 1–6 looking for an attractive robotics experience that doesn’t need a lot of pedagogical depth. Also a good option for home use as early as Pre-K.

In addition, Dash has an older sibling called Cue, intended for grades 6+, which was clearly motivated by Wonder hearing that older students were turned off by Dash’s color scheme and cuteness. Cue costs $200, is gray-colored and offers additional text-based programming using JavaScript.

Choosing among many robot options

In summary, with all the robotics options out there, it can become overwhelming for any teacher to choose what is best for their students. Whatever the age of your students, and whatever you hope they learn from working with robots in your class, there is an option for you — but the world of educational robots is so new, you should expect to have to try several times before you find the right fit.

My suggestions:

1. choose a robot that you can manage in the classroom with ease, and won’t exhaust your budget
2. start with just one robot, expand to more if it’s working, and try another if it isn’t
3. try to choose one that can allow both your highest- and lowest-performing students to be challenged appropriately
4. don’t expect to move too quickly through lessons at first
5. as you try out the robot, include students on your own discovery process; troubleshooting is as important a part of the learning process as the coding!

Good luck, and please let us know how you do!