Connected-device mobile product
2
App stores the product shipped to
BLE
The state machine senior engineers own outright
Live
Telemetry from the device into the app
A connected device is judged in its first thirty seconds, and then every time the signal wobbles.
Hardware is unforgiving: the app is the only face the device has, and the moments that break trust — pairing, dropouts, a reading that looks wrong — are the ones generic app work tends to skip. We built the companion product around exactly those moments.
The problem
A connected device is judged in its first thirty seconds — the pairing flow — and then every time the signal wobbles afterward. Bluetooth Low Energy is where consumer hardware products most often feel broken: a pairing that fails silently, telemetry that stalls without saying why, a companion app that assumes the happy path and has nothing to show when the device drops. The engineering that matters is in the unhappy paths.
The difficulty is structural rather than incidental. A phone and a device disagree about the world constantly: the radio link drops without either side being told, the operating system suspends the app in the background and stops delivering events, permissions get revoked between sessions, and readings arrive out of order or late enough to be misleading. None of this is exceptional — over months of ownership, every one of these happens to every user.
What we built
A companion mobile product across iOS and Android, built around the failure modes rather than in spite of them:
- BLE hardware pairing designed to be legible when it works and honest when it doesn't.
- Live telemetry from the device into the app.
- A companion app whose hard cases — disconnects, retries, stale readings — were treated as the product, not an afterthought.
How it was built
The volume of a native app across two platforms — screens, state, store scaffolding — is the generated part. The BLE state machine, where the edge cases live, is the part senior engineers own, because that is where a device product actually succeeds or fails.
Outcome
The product shipped to both the App Store and Google Play.
Most of what we build is under NDA — yours would be too, unless you told us otherwise. Send the requirement and you get back a functional specification, at no charge.
Student transport · United States
Student transport development: two apps, two portals and an automated trip builder
Parent and driver apps, school-district and franchise portals, and an automated trip builder that routes and prices shared trips across several school districts — apportioned to the cent.
Read
Language services · Canada
Language access development: an interpreter on demand, in 230+ languages
The application suite and client portals behind an on-demand phone and video interpretation network — 230+ languages, 24/7, run by the non-profit sector.
Read