A device that works on your desk is not yet a product. Once it ships, it has to resist attackers, run for months on a small battery, and be fixable without anyone touching it. This final module covers the three concerns that separate a prototype from something people can rely on.
You'll start with security, learning how secure boot and code signing make sure a device only runs trusted firmware, and how over-the-air updates let you ship fixes safely. Then you'll look at power, using the sleep modes on the ESP32 to stretch battery life. Finally you'll see what it takes to move from a working prototype to production, including manufacturing, certification, and testing.
Once you've finished, put everything together in Projects, where you can apply each module to a complete build.
What secure boot is and why it matters: how attackers target embedded devices, and how a root of trust, code signing, and code validation keep a device running only unmodified code from its maker.
Why over-the-air updates are essential for keeping deployed embedded systems secure and up to date, and how to implement them in practice with the Mongoose library.
The power-saving options available on the ESP32, with real-world measurements of how much each one reduces current draw, so you can choose the right mode for a battery-powered design.
What it takes to go from breadboard to market: working with vendors, manufacturing, certification, and building testing rigs for a connected product.