
Arduino Uno
Best for direct control logic, relays, simple automation, and easy explanation in class.
Use the smallest board that solves the control problem cleanly, then step up to Raspberry Pi only when the project also needs storage, networking, or a software layer running on-device.
Board choice affects cost, wiring, software complexity, and how professional the final prototype feels during the presentation.

Best for direct control logic, relays, simple automation, and easy explanation in class.

Best for compact enclosures, breadboard builds, and projects where space matters.

Best for dashboards, logs, camera work, and richer local processing.
The board choice should match the technical role instead of being selected only because it is popular.

A strong default for learning and prototyping. It is easy to wire, easy to explain, and sufficient for many sensor-and-output systems.
Official Arduino Uno image

Use Nano when the project needs to look cleaner or fit into a smaller case. It carries the same general idea as Uno in a tighter footprint.
Official Arduino Nano image

Use Raspberry Pi when the project crosses from simple control into software hosting. It can store data, run a dashboard, and connect the prototype to a network.
Official Raspberry Pi 5 image
The board should match the role, not the hype.
Picking the right platform makes the project easier to build, easier to explain, and more believable as a complete system.