Matter 1.6’s Joint Fabric finally lets devices share one network across ecosystems

Matter 1.6 introduces Joint Fabric, a new way to share smart home devices across different ecosystems, and it’s exactly what “sharing” has always needed to mean. Instead of bouncing the same smart light through multiple separate setup flows and accounts, Joint Fabric aims to create a single shared Matter network that multiple authorized platforms can manage. The CSA, the group behind Matter, is set to announce this new feature as part of the Matter 1.6 spec at Unify this week.

The practical consequence is the one customers (and honestly, product teams) have wanted from day one: devices added to the network should become controllable by any authorized platform, including Apple Home, Google Home, Amazon Alexa, and others. With Joint Fabric, you do not “share” a smart device between apps. You set it up once. Then you control it everywhere, because the platforms that are authorized to access the network can all operate within the same shared infrastructure. The source frames it with a helpful analogy: it’s like a joint bank account where multiple platforms have signing authority. That is the promise, and Matter 1.6 is the vehicle.

To understand why this matters beyond the setup screen, it helps to remember what Matter is trying to solve in the first place. Matter is the smart home interoperability standard built to reduce the chaos of smart devices that only work inside a specific company’s ecosystem. In that context, “sharing” is not a cosmetic feature. It is the moment where interoperability usually breaks down, because it is where permissions, device identity, and control paths get messy. Joint Fabric attacks that directly by changing the underlying concept from “each ecosystem gets its own view and connection” to “there is one network fabric that multiple ecosystems can control.”

This is also where executive stakes show up fast: onboarding is a business process, not just a technical mechanism. If a customer has to repeat pairing or manage multiple accounts, friction rises. If friction rises, conversion drops. And if conversions drop, companies feel it in the metrics that executives actually care about, like activation rates for new devices and ongoing engagement with their platform. Joint Fabric’s pitch is simple: set up once, control everywhere. That reduces the number of times customers need to understand ecosystem boundaries, which can also reduce support burden and reduce the chances that a buyer gives up mid-install.

There is another second-order effect here for boards and leadership teams: integration strategy. Smart home platforms and device makers have historically been incentivized to differentiate through their own user experience, and those experiences often came with their own control paths. Joint Fabric shifts the center of gravity. If multiple platforms can control the same authorized Matter network, then device makers gain leverage, because they are not forced into one ecosystem as the primary control plane. At the same time, ecosystem operators have to compete on value above basic compatibility, since the “it works everywhere” advantage becomes less about proprietary access and more about the quality of each platform’s interface, automation, and reliability.

It is also worth noting the industry context behind standardization efforts like this. The CSA’s work on Matter is essentially an ongoing negotiation between competing platforms and device manufacturers, where compatibility has to survive real-world conditions, not just lab demos. Joint Fabric being part of the new Matter 1.6 specification signals that the standard is evolving from “devices can talk” to “ecosystems can cooperate over time.” That is a meaningful maturation step. Standards that only solve connectivity can still leave customers tangled in account management and permissions. Joint Fabric aims to untangle that by making shared network management a first-class capability.

For leaders, the strategic question becomes: what do you build when the interoperability baseline changes? If Joint Fabric enables a single shared Matter network controlled by multiple ecosystems, then product roadmaps, partnership plans, and go-to-market messaging need to reflect that reality. The winning posture may be to treat cross-ecosystem control as default behavior rather than a special partnership feature. Done right, it can improve customer outcomes and tighten your product story. Done halfway, it can leave teams stuck supporting edge cases that customers no longer think should exist, because the standard is now explicitly trying to make the “set it once, control it everywhere” experience real.