Don't Buy a Kit First When Starting Robotics: 8 Development Boards Can Already Be Taken Apart and Reassembled in the Browser

When learning robotics, should your first money go to a kit? Movez's approach is direct: don't buy one yet. He put 8 common development boards into the browser, where they can be rotated, have parts removed, be connected with jumper wires, and even have chips and pin headers placed back onto the pads to simulate assembly. The original tweet puts it plainly: you don't need to spend over $500 on a starter kit just to learn what GPIO pins are.

The site is called Robotics Lab, at http://robotics-lab-app.vercel.app. It is free and requires no sign-up. The 8 boards include Arduino Uno R3, Nano, Mega 2560 R3, ESP32 DevKit V1, NodeMCU, Raspberry Pi Pico, STM32 Blue Pill, and Raspberry Pi 4 Model B. The workbench has guided missions, such as blink an LED, read a sensor, and drive a motor, as well as free build so you can wire from pin to pin yourself.

The Uno page breaks the board into 15 numbered parts. Click a part, and the camera flies to it. Quizzes have you find parts by name, and assembly mode has you put the chip, connectors, and pin headers back onto the bare board and then solder them on one by one. The page also gives pin descriptions, the first blink code, and a comparison table of the 8 boards. For people without a hardware background, this is more intuitive than looking at a pinout diagram.

Movez says Fable 5.2 generated each 3D model entirely in code, with no ready-made 3D files or photos. The bottom of the page also notes three.js and WebGL. For people who write code, the procedurally generated geometry, traces, silkscreen, and markings are worth a look. For ordinary users, start by using it as a tool for learning to recognize boards.

The real value is that the cost of mistakes is front-loaded. On a real board, wiring VCC and GND incorrectly can cause smoke. In the browser, a wrong connection means at most starting over. A $500 kit is not necessarily expensive because of the parts. Many people's first board ends up gathering dust for a simpler reason: they wire something wrong once, or the motor spins and the board resets, and then they stop.

Someone in the replies asks a very apt question: does it simulate pin states and current limits, or is it just a 3D reference? That question is worth keeping. Solder joints, current limiting, power distribution, sensor timing, and unshared grounds still have to be gone through on a real board. Others in the replies also mention that similar tools have existed before, but this one is more detailed.

If you want robotics as a career, just looking at 3D boards is not enough. Ronin's article How to become a Robotics Engineer in 6 months is heavier: nearly 12,000 words, more than 100 links, 27 hands-on projects, split across 6 months into electronics fundamentals and soldering, Arduino and ESP32, motor drivers and sensors, CAD and 3D printing, ROS 2 and Gazebo/Nav2, control and kinematics vision, LeRobot and VLA, and portfolio and interviews. The article repeatedly emphasizes one thing: every stage should leave behind a project that moves, and the README should clearly state what broke and how it was fixed. The original is at https://x.com/i/article/2095038636362248196.

Open the model and go through the boards first, then decide what goes in the shopping cart.