The parts list for a kid's first robotics build (not the Jetson)

Our Jetson Orin Nano guides cover a real on-device AI computer — the same class of hardware used in industry, and genuinely the right tool for a teenager doing edge AI work. It's also more machine, and more money, than most families need for a kid's first robotics build. If your kid is younger, newer to this, or you just want to see if the interest sticks before buying a more serious board, here's the on-ramp we point families to before the Jetson conversation.

The actual first decision: microcontroller, not computer

A Jetson is a small computer — it runs an operating system, runs AI models, does general-purpose computing. For a first build, that's overkill. What you actually want is a microcontroller board: a much simpler, much cheaper chip that's built to read sensors and drive motors, and nothing else. It won't run an AI model on its own, but it will teach the actual fundamentals — inputs, outputs, loops, debugging a circuit that doesn't work — that every later robotics project builds on.

This is the same reason we don't start eight-year-olds on the Jetson series. The Jetson is the advanced tool. The microcontroller is where the concepts live.

What to actually buy

We're deliberately not naming specific brands or giving exact prices here — hardware pricing shifts fast enough that a number in a blog post is stale within months, and we'd rather you check current listings than trust a figure we made up for this paragraph. What to look for, in order of what matters:

• A starter kit, not a bare board. Look for a kit that bundles the controller with a breadboard, jumper wires, an assortment of basic sensors (light, distance, button), and a couple of small motors. Buying the board alone and sourcing parts separately is a rabbit hole you don't need for a first project.
• Beginner-documented, not just powerful. The board with the most tutorials, forum answers, and beginner-specific guides beats the board with the best specs. When your kid gets stuck at 8pm on a Tuesday, documentation is what saves the project, not raw processing power they're not using yet.
• USB-powered, not a separate power supply. One less thing to troubleshoot, one less thing to lose.

A reasonable starter kit in this category runs in the ballpark of a few pizza deliveries, not a few hundred dollars — check current prices before buying, since this is exactly the kind of number that goes stale.

Three projects, roughly in order of difficulty

A blinking light that reacts to something. Not just "blink an LED on a timer" — wire in a button or a light sensor so the blinking responds to the world. This is the smallest possible project that still teaches input-and-output, and it's the right first project precisely because it's almost too simple. Finishing something completely, even something tiny, matters more than starting something impressive.

A thing that moves toward or away from an obstacle. Add a distance sensor and a motor or two. This is the first project that feels like "robotics" rather than "electronics," and it's where most kids' actual interest either clicks in or doesn't.

A remote-controlled version of the same thing. Once the obstacle-response project works, ripping out the automatic behavior and replacing it with manual control from a phone or a simple remote is a satisfying next step — and it sets up the eventual jump to a Jetson-class board later, where "the robot decides on its own" comes back, but now powered by an actual model instead of a single sensor threshold.

When to make the jump to the Jetson series

The honest signal isn't age, it's whether your kid has hit the ceiling of what a microcontroller can do and is asking why the robot can't "just tell the difference" between things on its own. That question — wanting the machine to make a judgment call instead of following a fixed rule — is the actual on-ramp to edge AI, and it's the point where the Jetson guides become the right next step instead of the wrong first one.