From Arduino Prototype to Production Firmware: What Has to Change Before You Ship
An Arduino prototype proves the idea. Shipping thousands of units needs different firmware. How I take products from prototype to production.
The problem clients bring: "We have a working prototype on Arduino. Investors loved it. Now we need to manufacture 1,000 units and we are not sure the code is ready." Usually it is not, and that is normal.
What is really going wrong
- Blocking delays and busy loops that work in a demo but miss events in real use.
- No error handling, watchdog or recovery when a sensor or connection fails.
- Library code nobody has reviewed, with unclear licences.
- No way to update firmware in the field, and no version tracking.
How I solve it
- Review the prototype and keep what works, so the product's behaviour does not change.
- Move to an event-driven or RTOS structure on the vendor SDK, so timing is predictable.
- Add error handling, watchdogs, safe defaults and persistent settings.
- Add firmware versioning and a safe update path.
- Set up a reproducible build so anyone on the team can build the exact shipped image.
What the client gets
Production firmware that behaves like the prototype users loved, but survives real-world conditions, plus a codebase their own team can maintain.