{"docs":[{"id":179,"title":"Anatomy of a Connected Product: Device, Gateway, Cloud and App","heading":"Anatomy of a Connected Product: Device, Gateway, Cloud and App","subheading":null,"category":"IoT","body":{"root":{"type":"root","children":[{"type":"heading","tag":"h3","version":1,"children":[{"type":"text","text":"Desired and reported state","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"A pattern that works on most platforms is to keep two copies of device state in the cloud: the state the user or system wants, and the state the device last reported. The device reconciles the two whenever it connects. Platforms call this a device shadow or device twin; the idea is the same whatever the name.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"This keeps the app simple, because it writes intent rather than commands, and it copes with devices that are asleep or offline. It also shows support staff what each device believes.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"tags":"IoT, Architecture, Connected Products","cardCta":{"label":null,"link":null},"pageCta":{"label":"Talk to AAVICO engineering","link":"/contact"},"excerpt":"A connected product is four systems that have to agree with each other. Deciding early what each part owns prevents most integration surprises.","featuredImage":null,"type":"Blog","readTime":"3 min read","publishedAt":"2026-11-15T16:14:00.000Z","heroImage":null,"introText":"A connected product is rarely one piece of engineering. There is the device itself, often a gateway or hub, a cloud service that stores data and manages the fleet, and an app that people actually touch. Each is built with different tools, often by different teams, and each fails in its own way. This article sets out what each tier is responsible for and the interfaces that hold them together.","metrics":[{"id":"anatomy-of-a-connected-product-device-gateway-cl-metric-1","value":"Device","label":"Senses or actuates, and must keep doing its core job when the network is gone.","icon":null},{"id":"anatomy-of-a-connected-product-device-gateway-cl-metric-2","value":"Gateway","label":"Bridges radios such as BLE, Zigbee or LoRaWAN to an IP network, and can buffer data.","icon":null},{"id":"anatomy-of-a-connected-product-device-gateway-cl-metric-3","value":"Cloud","label":"Holds device identity, state and history, and is the authority for fleet management.","icon":null},{"id":"anatomy-of-a-connected-product-device-gateway-cl-metric-4","value":"App","label":"Onboards, controls and reports, but should not be the only place business logic lives.","icon":null}],"gallery":[],"challenge":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Most integration trouble comes from responsibilities nobody wrote down. The device team assumes the cloud validates a setting, the cloud team assumes the app already did, and an out-of-range value reaches hardware that trusted it.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"The tiers also change at different speeds. An app may be updated weekly, a cloud service daily, and device firmware a few times a year, with old versions in the field for a decade. Interfaces have to survive that mismatch.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"blockquote":{"quote":"Decide which tier owns each piece of state before writing code. Most connected-product bugs live on the boundaries.","author":"","role":"AAVICO Engineering"},"supportImage1":null,"deliverables":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Draw the four tiers and list every piece of data and every decision. Give each one an owner and a single source of truth.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Define the interfaces between tiers as versioned contracts: message formats, error responses and what happens when a peer is missing.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Decide how each tier is updated and how long old versions must be supported, then test the oldest supported combination, not just the newest.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"results":[{"id":"anatomy-of-a-connected-product-device-gateway-cl-result-1","title":"Clear Ownership","description":"Every setting and decision has one owner, so there is one place to fix it."},{"id":"anatomy-of-a-connected-product-device-gateway-cl-result-2","title":"Resilience","description":"Devices behave sensibly when the gateway, cloud or app is unavailable."},{"id":"anatomy-of-a-connected-product-device-gateway-cl-result-3","title":"Maintainability","description":"Versioned interfaces let each tier change without breaking the others."},{"id":"anatomy-of-a-connected-product-device-gateway-cl-result-4","title":"Supportability","description":"Reported state gives support teams evidence instead of guesswork."}],"lookingAhead":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Choose the messaging protocol between device and cloud once responsibilities are clear. The traffic pattern, not familiarity, should drive that choice.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Plan device identity and provisioning alongside the architecture. Every later security decision depends on how a device proves who it is.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"supportImage2":null,"testimonial":{"quote":null,"author":null,"role":null,"photo":null},"challengesSolved":[{"id":"anatomy-of-a-connected-product-device-gateway-cl-challenge-1","title":"Validation each tier assumes another performs","description":null,"icon":null},{"id":"anatomy-of-a-connected-product-device-gateway-cl-challenge-2","title":"Devices that stop working when the cloud is down","description":null,"icon":null},{"id":"anatomy-of-a-connected-product-device-gateway-cl-challenge-3","title":"App updates that break older firmware","description":null,"icon":null},{"id":"anatomy-of-a-connected-product-device-gateway-cl-challenge-4","title":"No record of what state a device believes","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}