{"docs":[{"id":184,"title":"Designing Companion Apps for IoT Devices: Onboarding to Updates","heading":"Designing Companion Apps for IoT Devices: Onboarding to Updates","subheading":null,"category":"IoT","body":{"root":{"type":"root","children":[{"type":"heading","tag":"h3","version":1,"children":[{"type":"text","text":"Capabilities, not version numbers","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Have the device report what it supports, as a list of capabilities or a feature schema, and let the app show only what that device can do. This is more robust than hard-coded firmware version checks, and it lets one app release serve old and new hardware revisions.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"For updates relayed through the phone, design for interruption: the user leaves the app, the phone locks or Bluetooth drops. The transfer should resume or restart cleanly, and the device, not the app, should decide when an image is complete and valid.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"tags":"IoT, Mobile Apps, User Experience","cardCta":{"label":null,"link":null},"pageCta":{"label":"Talk to AAVICO engineering","link":"/contact"},"excerpt":"For many connected products the app is the product as far as the customer is concerned. It has to handle setup, daily use, updates and eventual handover.","featuredImage":null,"type":"Blog","readTime":"3 min read","publishedAt":"2026-11-15T15:39:00.000Z","heroImage":null,"introText":"A companion app has a longer and more varied job than most mobile apps. It adds a device the user has just unboxed, controls it day to day, shows its history, delivers firmware updates and eventually removes or transfers it. It does all of this while talking to hardware with its own release cycle. This article walks through the device lifecycle as the app sees it, and the design decisions each stage needs.","metrics":[{"id":"designing-companion-apps-for-iot-devices-onboard-metric-1","value":"5 stages","label":"Onboard, control, monitor, update and remove: the lifecycle every companion app must cover.","icon":null},{"id":"designing-companion-apps-for-iot-devices-onboard-metric-2","value":"Versions","label":"The app must cope with every firmware version still in the field, not just the newest.","icon":null},{"id":"designing-companion-apps-for-iot-devices-onboard-metric-3","value":"Relay","label":"Many apps carry firmware to the device over Bluetooth, making the phone part of the update path.","icon":null},{"id":"designing-companion-apps-for-iot-devices-onboard-metric-4","value":"Offline","label":"Local control over Bluetooth or the home network keeps basic functions usable without internet.","icon":null}],"gallery":[],"challenge":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Companion apps are often built against the latest prototype firmware and tested only with it. After launch the app updates through the stores while devices in the field run a spread of firmware versions, and features break on hardware the team no longer has on its desks.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Onboarding is the other common weakness. It is the first thing every customer does and a frequent source of support calls, yet it is often designed last.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"blockquote":{"quote":"Build the app around the device lifecycle, not around screens. Every stage needs a designed path, including the failure paths.","author":"","role":"AAVICO Engineering"},"supportImage1":null,"deliverables":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Map the lifecycle stages and write the success and failure path for each, including what the user sees when something does not respond.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Define a capability report in firmware and drive the interface from it, so app features follow what each device actually supports.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Keep a test rack of devices on every supported firmware version and test every release against all of them.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"results":[{"id":"designing-companion-apps-for-iot-devices-onboard-result-1","title":"Fewer Returns","description":"A designed onboarding path resolves common setup failures in the app."},{"id":"designing-companion-apps-for-iot-devices-onboard-result-2","title":"Compatibility","description":"One app release works across the hardware and firmware in the field."},{"id":"designing-companion-apps-for-iot-devices-onboard-result-3","title":"Safe Updates","description":"Interrupted transfers recover without user intervention or support calls."},{"id":"designing-companion-apps-for-iot-devices-onboard-result-4","title":"Clean Handover","description":"Devices can be removed or transferred without leaving data or access behind."}],"lookingAhead":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Plan how the app collects diagnostics, with the user's consent, so support staff can see device and connection state when a customer calls.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Agree a minimum supported app version and a way to prompt users to upgrade when an old app can no longer work safely with new firmware.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"supportImage2":null,"testimonial":{"quote":null,"author":null,"role":null,"photo":null},"challengesSolved":[{"id":"designing-companion-apps-for-iot-devices-onboard-challenge-1","title":"Features that break on older firmware","description":null,"icon":null},{"id":"designing-companion-apps-for-iot-devices-onboard-challenge-2","title":"Updates that fail when the phone locks","description":null,"icon":null},{"id":"designing-companion-apps-for-iot-devices-onboard-challenge-3","title":"Setup errors with no recovery path","description":null,"icon":null},{"id":"designing-companion-apps-for-iot-devices-onboard-challenge-4","title":"Devices that keep old accounts after transfer","description":null,"icon":null}],"relatedPosts":[],"contactUs":{"show":true},"updatedAt":"2026-11-15T17:32:32.682Z","createdAt":"2026-11-15T17:32:32.682Z"}],"hasNextPage":false,"hasPrevPage":false,"limit":10,"nextPage":null,"page":1,"pagingCounter":1,"prevPage":null,"totalDocs":1,"totalPages":1}