The Three Boards Every Designer Should Know

Most industrial design programs will teach you how to model a part, how to render it, and how to present it. Very few will teach you how to make it do something. That gap between an object that looks like a product and one that actually behaves like one is where electronics come in. And the good news is that the barrier to entry has never been lower.

There are three boards worth knowing. They're not interchangeable. Each one represents a different level of capability, and choosing the wrong one for a project wastes time. Understanding the difference is one of those things that separates designers who can prototype real interactions from designers who can only simulate them in software.

The Arduino is a microcontroller. Not a computer, a microcontroller. That distinction matters. It doesn't run an operating system or multitask. It executes a single set of instructions repeatedly and reliably. That simplicity is the whole point.

What it can do is wild for how cheap and accessible it is. Read inputs from buttons, knobs, distance sensors, pressure sensors, light sensors, and temperature sensors. Control outputs like LEDs, servo motors, DC motors, vibration motors, and speakers. It's the right tool when you're testing a single physical interaction like a button that triggers haptic feedback, a dial that controls brightness, or a sensor that detects when someone sits down.

The language is C++, but the Arduino IDE strips away most of the complexity. If you've never written code before, the learning curve is real but short. Most designers get a working prototype within a weekend.

Where to start: The official Arduino starter kit at Arduino.cc/en/education includes a breadboard, components, and 15 guided projects, ranging from blinking an LED to building a basic synthesizer. If you'd rather learn by watching, Paul McWhorter's Arduino tutorial series on YouTube is the most thorough free resource out there. He teaches it the way an engineer would explain it to a curious non-engineer, which is exactly what you need.

A practical first project: Wire up a proximity sensor (HC-SR04, about $3) to a servo motor. When something gets close, the servo moves. It sounds trivial, but it's not. You'll learn how sensors output data, how to map that data to a physical response, and how unreliable physical inputs actually are. That last lesson is more valuable than it sounds.

The ESP32 is where things get really interesting for product designers. It does everything the Arduino does, the same kinds of inputs and outputs, and a similar programming environment, but it has built-in WiFi and Bluetooth. That one addition completely changes what you can prototype.

Connected products are now the default expectation in consumer electronics: smart speakers, health monitors, connected appliances, and wearables. The interesting design problems in these categories aren't visual; they're behavioral. How does the device communicate with a phone? What does it feel like to receive information through an object rather than a screen? You cannot answer those questions with a screen mockup. You need something that actually connects.

The ESP32 enables you to build prototypes that send and receive data over Wi-Fi, communicate with a phone via Bluetooth, or trigger actions through simple web interfaces. The Adafruit Feather ESP32 at adafruit.com is a well-documented version that's much friendlier to beginners than the raw ESP32 development boards.

A practical first project: Random Nerd Tutorials at randomnerdtutorials.com offers a project titled "ESP32 Web Server" that guides you in hosting a simple control panel on your local network, with buttons on a phone that control LEDs on the board. It's a simplified version of how almost every connected product works, and doing it once demystifies much of what feels like magic in finished consumer products.

The Raspberry Pi is a full computer. It runs Linux, handles multiple processes simultaneously, connects to cameras and microphones, drives touchscreens and displays, and runs Python at a level of complexity the other two boards cannot match. People ship finished consumer products built on Raspberry Pi hardware. It is not a learning tool; it's a platform.

For designers, the Pi becomes relevant when the concept involves computer vision (e.g., object detection, face recognition, or motion tracking), audio processing, edge machine learning, or a display interface more complex than a few LEDs. These aren't niche use cases anymore. They show up constantly in medical devices, retail environments, automotive interiors, and smart home products.

The Raspberry Pi 5 at raspberrypi.com is the current generation. It's significantly faster than its predecessors and handles camera-based projects without the lag that used to make them frustrating to prototype.

A practical first project: The official Raspberry Pi camera module, paired with the getting-started guide, will enable you to capture and process video within an afternoon. From there, OpenCV, an open-source computer vision library, enables projects such as object detection and motion tracking. It's a rabbit hole, but a genuinely productive one.

These three boards correspond to a progression that mirrors how connected physical products function: isolated interactions, networked behaviors, and computation-heavy experiences. You don't need to master all three. But knowing what each one is capable of makes you a better collaborator with engineers, a more credible voice in early development discussions, and, most importantly, someone who can test their own ideas rather than waiting for someone else to build them.

Subscribe for more

— Alden