Showduino grew from the practical problem of making physical effects, lighting, sound and interactive scenery behave like one production instead of a pile of unrelated controllers.
Showduino is not a browser application waiting for somebody to invent a controller later. The touchscreen, enclosure, P4 runtime, communications bridge, specialist nodes, wiring, diagnostics and authoring workflow are being built as one system.
That means the unglamorous parts matter: service access, labels, status lights, emergency behaviour, local storage, failure modes and what happens when an operator interface disappears mid-show.
A browser is brilliant for designing a timeline. A touchscreen is brilliant for an operator. Neither should be the only thing standing between a running attraction and a dead show.
That principle is why the current Showduino architecture gives the ESP32-P4 Show Engine the authoritative runtime and keeps Studio, the Director and communications layers in clearly separated roles.
The enclosure is printed and revised around the electronics rather than treated as an afterthought. Connections, cooling, controls and mounting are allowed to influence the software architecture too.
The goal is not the smallest possible pile of boards. It is a system that can be installed, understood and repaired.
The live show should keep running without cloud services, internet access or a browser session.
The P4 owns show state so multiple interfaces do not become competing sources of truth.
Dedicated nodes make physical roles easier to test, replace and diagnose.
Emergency behaviour interrupts normal effects and requires deliberate recovery rather than auto-resume.
Showduino is aimed at immersive attractions, scare events, escape rooms, practical-effects builds, interactive installations and small-scale theatre where physical outputs and repeatable timing matter.
Coordinate environmental effects, triggered scenes, signage, audio and operator control across physical spaces.
Treat relays, MOSFET loads, pixels and sound as parts of a timed production rather than independent gadgets.
Keep the flexibility of ESP32 hardware while adding clearer roles, project files, timelines and diagnostics.
The architecture guide documents the Director → Comms → P4 → Nodes model now used by Showduino.