Where the money goes
Hardware revisions, RF/certification, firmware, cloud ingestion, dashboards, provisioning, and support dwarfs the first PCB. Fleet-hardened signed OTA is often the line between a pilot and a product you can sleep on.
Tell engineering partners your target unit cost, fleet size in year one, and update cadence — those numbers shape architecture more than buzzwords.
Security is a product feature
Unmanaged devices become network footholds. Design device identity, secure provisioning, encrypted transport, and least-privilege cloud credentials from revision A. Retrofitting crypto onto a million units is how vendors write breach postmortems.
How devices talk: MQTT, HTTP, and edge
MQTT suits telemetry and command with intermittent links. HTTP works for simpler pulls. Edge computing keeps decisions near the machine when round-trips are too slow or connectivity is poor — common in industrial IoT (IIoT).
Consumer IoT optimizes for experience and cost; IIoT optimizes for uptime and safety. Be explicit which you are building.
Signed OTA and fleet visibility
If you cannot update firmware safely, every bug is a truck roll. Signed images, staged rollouts, health checks, and rollback beat “flash everything Friday.” Pair OTA with a console operators actually open — online count, version skew, failed updates.
- Unique device identity from first boot
- Signed artifacts and verified boot where hardware allows
- Canary cohorts before full fleet
- Companion apps only after the device story is solid