Case Study: Delivering App, Cloud and Admin as One Loop for Three IoT Products
Table of Contents
The situation
Three hardware products from different industries were ready on the device side, but each still needed the software around it before it could reach customers: a companion app, a cloud backend and an admin console. All three had to ship together, with one team accountable for the whole software side.
What we did
- Device-side integration: BLE connection and pairing, device binding and scanning, OTA firmware update flow, and debugging on real devices.
- Companion apps built around the actual device behaviour rather than an idealised specification.
- Cloud backend and admin console for device data, users and day-to-day operations.
- Release support through app store review and launch.
We worked directly with each firmware team, so protocol questions were settled on real devices instead of in documents.
The result
All three products went from device prototype to apps published and systems online in August–September 2026. Because one team owned the app, cloud and admin together, there were no hand-offs between vendors: development cycles were significantly shorter and costs stayed low.
Lessons for hardware companies
- Treat app, cloud and admin as one product. Most “the app is broken” complaints are really integration problems between the three.
- Test on real devices early. Bluetooth and Wi-Fi behaviour varies across phone makers and OS versions.
- Keep one owner. A single accountable engineer avoids the finger-pointing that happens between an app agency, a cloud vendor and a firmware team.
Already shipped, but the reviews are bad? Read why hardware companion apps get one-star reviews, see how forward deployed engineering works, or contact us to discuss a small paid pilot.