Blog

All articles

An Ecosystem of Connected Devices

Updated:

A connected device ecosystem is a product that runs on several devices and treats them as parts of one service: the account, the data, and the task in progress follow the user from a phone to a laptop, a TV, a car, or a smart speaker. According to IoT Analytics, the number of connected IoT devices reached 21.1 billion at the end of 2025, 14% more than a year earlier, with about 39 billion projected for 2030.

Connected devices in one product ecosystem | New Line Technologies

Key Takeaways

  • Users judge a multi-device product at the moment of switching, for example from a phone to a TV or from a laptop to a car.
  • Michal Levin’s 3Cs framework, consistent, continuous, and complementary design, is still a practical way to plan these moments.
  • LLM assistants such as Gemini for Home and Alexa+ are becoming a shared layer across devices: the same assistant answers on speakers, displays, cameras, and phone apps.
  • Since 11 September 2026, the EU Cyber Resilience Act requires manufacturers of connected products to report actively exploited vulnerabilities within 24 hours.

When Devices Become an Ecosystem

The test is simple: pause a series on your phone and open the TV app. If the episode continues at the same minute, the devices work as one product. If the TV starts from the beginning and asks you to sign in again, you have two separate apps that happen to share a brand.

For a product team, this means the backend, the account system, and the data model are designed once for all devices, and each client app is built around its own role. The phone app, the TV app, and the web app become views of one service.

The 3Cs Framework

Michal Levin described three approaches to multi-device design in her book Designing Multi-Device Experiences (O’Reilly, 2014). Teams combine them depending on the product:

ApproachHow it worksExample
ConsistentThe same core experience, content, and features on every device, adapted to the screen and input methodA banking app with the same accounts, payments, and history on iOS, Android, and web
ContinuousA task moves with the user from one device to the next and continues where it stoppedApple Handoff: an email started on iPhone opens on a Mac with the same draft
ComplementaryDevices take different roles and work at the same timeGoogle Cast or AirPlay: the phone picks and controls a video while the TV plays it

Google stopped selling Chromecast in 2024 and replaced it with Google TV Streamer, but the Google Cast protocol remains built into TVs and streaming apps, so the pattern is more common than ever. Consistent design is the baseline, because users expect to reach their data from any device. Continuous and complementary design are where products differ: they decide which device leads in a given moment and how the others support it.

Building a product for several devices?

What Changed in 2024–2026

One assistant, many devices. In late October 2025, Google started replacing Google Assistant with Gemini for Home on its speakers and smart displays in early access, starting in the US and English, and has since added more countries and languages. The same Gemini assistant also works on Google cameras and doorbells and in the Google Home app, and it keeps track of earlier turns of a conversation, so a follow-up question works without repeating the topic. Amazon announced Alexa+, a generative AI version of Alexa, in February 2025, and Apple Intelligence runs across iPhone, iPad, and Mac. For a product team, this means a voice or chat request can now reach your service from any of these devices, so actions and data need to be exposed through an API that the assistant can call, with the same result whichever device the user speaks to.

New devices joined the ecosystem. Apple Vision Pro brought spatial computing to the Apple ecosystem in 2024, and in September 2025 Meta released Ray-Ban Display glasses with a small built-in screen and a Neural Band wristband for gesture control. These devices depend on a phone or a computer for setup, content, and notifications, so they extend existing ecosystems instead of creating new ones. A glasses or headset app can reuse the backend of your phone app and focus on what these devices do well: short notifications, hands-free capture, or a second screen.

The smart home is converging on Matter. Matter, the standard from the Connectivity Standards Alliance, runs over Wi-Fi, Ethernet, and Thread, a low-power mesh network for battery devices such as sensors and locks. After two quality-focused releases in 2025, Matter 1.5 arrived on 20 November 2025 with support for cameras, which stream live video and audio over WebRTC, soil sensors, new closures such as garage doors and gates, and expanded energy management. One Matter integration now reaches Apple Home, Google Home, Amazon Alexa, and other platforms, for the device types each platform supports, so device makers no longer need a separate integration for each. Platforms adopt new versions with a delay, so check camera support on each one before you plan a release.

Privacy and Security Across Devices

Every new device in an ecosystem is another place where data is stored and another session that can be stolen. A product that syncs messages, recordings, or payment data across five devices needs per-device sessions that can be revoked when a device is lost, encryption in transit and at rest, and a clear rule about which data is cached locally.

Under the EU Cyber Resilience Act, manufacturers of products with digital elements, such as IoT devices and connected software, must report actively exploited vulnerabilities and severe incidents from 11 September 2026: an early warning within 24 hours and a follow-up within 72 hours. All main requirements of the act, including CE marking, apply from 11 December 2027. Cloud services fall under the CRA only as a remote data processing solution: a service the product needs for its core functions, developed by the same manufacturer. Standalone SaaS is out of scope. The European Commission published final guidance with 67 practical examples on 27 July 2026, which helps check whether a specific product is covered. Cross-device analytics also falls under data protection rules, so tracking a journey from phone to laptop requires user consent and a documented purpose.

Case: A Recording Platform for Four Operating Systems

Our real-time multimedia team built the Remote HD Recorder for Zoom for Cinamaker, a company that makes multi-camera video production tools. The product records each participant of a Zoom call separately in 1080p, then uses AI to detect the active speaker and assemble the final video. It consists of native apps for macOS, Windows, iOS, and Android, plus a web and cloud service, all working with one set of recordings.

A team of 14 people delivered the product in 18 months. The main multi-device challenges were recording consistently on four platforms with different media APIs and protecting the stored video with encryption. The product is live and has a hybrid monetization model with subscriptions and pay-as-you-go. Learn more about our custom software development services or how a dedicated development team can build apps for every platform you need.

Where Multi-Device Projects Go Wrong

A typical failure looks like this: a company builds an iOS app, then hires a separate team for Android, then another for the web. Each app has its own backend logic, sync was added later as a patch, and a user who switches devices loses their place. Every new feature has to be built three times.

Before planning the apps, write down two or three real scenarios where a user switches devices, for example starting a recording on a laptop and reviewing it on a phone. The scenarios show which data must travel, which device leads, and what the shared backend has to provide.

FAQs

Apple devices that pass tasks to each other through Handoff, the Google Home ecosystem with Gemini on speakers, displays, and cameras, and Amazon’s Echo devices with Alexa+. In business software, a video platform with apps for desktop, mobile, and web that share one cloud backend is also an ecosystem.

The 3Cs come from Michal Levin’s book Designing Multi-Device Experiences. Consistent design repeats the core experience on every device, continuous design lets a task move from one device to another, and complementary design gives devices different roles that work together.

IoT refers to physical objects connected to the internet, such as sensors, meters, or smart locks. A device ecosystem describes how one person uses several connected devices as one product, and it can include IoT devices along with phones and computers.

A cloud backend holds the master copy of the data. Each device syncs changes through an API, keeps a local copy for offline work, and follows conflict rules when the same record changes on two devices.

Planning a product for phones, web, TVs, or wearables? Talk to our team, and through our software development services we will help you design the ecosystem and build the apps.