- 10 critical bugs found and fixed in our first release
- One platform across two clouds: the device fleet on Azure IoT Hub, services on Google Cloud
- Remote fleet operations: provisioning, reboots and over-the-air updates
Digital signage sounds simple until you own the fleet: Android screens in venues across several countries, playing scheduled campaigns and logging proof of every play - and nobody on site to press restart.
The network belongs to Future Shop. It came to us the hard way: the original build team moved on, and we assumed a live IoT estate: an Android app on every screen, device twins and MQTT messaging on Azure IoT Hub, services running on Google Cloud. Our first move was a systematic read of everything we had inherited; our first release fixed ten critical bugs, from battery drain and resource leaks to race conditions in the messaging layer.
Since then it has been a running discipline. Provisioning that used to be half an hour of manual work is being automated away. Reboots, health checks and over-the-air app updates are issued remotely through an operations API. Proof-of-play logs flow into a lakehouse data platform and come back out as the reporting the business reads. The fleet now supports an international rollout programme.
We didn’t build this platform. It gets run like one we did.