Over-the-air (OTA) update
also: OTA · FOTA · firmware update
Delivering new firmware to devices in the field over their network connection, so bugs and security issues can be fixed without a recall.
OTA updates turn a shipped product into one you can still improve. A well-designed system downloads a signed image, verifies it, installs it into a separate memory area while the current firmware keeps running (the A/B or dual-bank approach), switches over, and rolls back automatically if the new version fails to start or check in.
For connected products this is close to a baseline expectation. A device without a secure update path is a security liability, and the EU Cyber Resilience Act requires manufacturers to be able to address vulnerabilities through security updates during a defined support period.
Where it bites: dual-bank storage roughly doubles the flash reserved for firmware; updates drain batteries and can fail midway on weak connections; and staged rollouts, version tracking and a fleet back end are needed so one bad release doesn't reach every unit at once.
Founder takeaway
Design OTA in from the first board revision: size memory for two images, sign every release, and roll out in stages with automatic rollback.
sources
engineer review pending