Your browser is out-of-date!

Update your browser to view this website correctly. Update my browser now


The Impact Of APIs From Smart-Home Platform Providers

Any device maker and app developer can offer an API to their partners; however, smart-home platform providers play a unique role in the ecosystem by aggregating and integrating third-party devices and apps. A platform providers’ API strategy usually reflects its business strategy to augment their market position, set development priorities and establish partnership preferences.

Parks Associates has identified more than 15 smart-home platform players in this growing, yet competitive, market. These platforms can be segmented based on the extent of their openness through APIs and their support of either custom or DIY installation. The majority provide platform solutions and professional services to business customers who, in turn, package different smart-home services for end users (B-to-B-to-C). However, a few platforms also offer smart-home services directly to end users (B-to-C).

Parks Associates segment a platform’s openness based on the following factors:

Closed system, proprietary API: A platform provider uses proprietary technologies to build the platform’s architecture, and its APIs only support its own branded devices. Third-party devices and applications cannot be added to the platform. Few companies still pursuing this approach because the smart-home market has changed so fast and consumer choices of smart-home products have exploded. Limiting consumer’s choices is no longer viewed as a sound business strategy any more.  

Closed system, private API: A platform provider chooses to work only with partners that it trusts and with technologies that are compatible with its architecture. It has APIs but is usually reluctant to share them with its partners openly and prefers integrating partners’ solutions based on its own business needs. Control4 is a good example of this approach. AT&T’s Digital Life also takes this approach.

Platform providers that follow these two closed-system approaches usually believe that they have the assets that appeal to developers and have a clear vision of their roadmap for developing a complete smart-home experience for consumers. They are concerned that an open-system approach may lead to compromising consumer experience and security holes exposed by third-party partners. Deep down, they fear that third-party partners may have a hidden agenda, including becoming their competitors in the future.

Open platforms follow these general guidelines:

Open system, managed-open API: A platform provider is open to integration with third-party apps and devices, but only on a curated basis. Companies taking this approach usually offer a developer program with a certification process to ensure that third-party apps and devices are consumer experience-optimized in addition to being technologically compatible. Their APIs are open to use by these certified partners only. Examples of smart-home platforms that take this approach include Icontrol, Nest,, Qivicon and Arrayent.

Open system, open API: A platform provider has an open invitation to third-party developers and usually offers its APIs in the public domain with few restrictions on usage. This approach can usually attract a large number of app developers and device makers, as they can experiment with the platform’s APIs and create mash-up experiences for new use cases or differentiated apps. Wink and Samsung’s SmartThings are the best examples of platforms taking this approach.

Platform providers following an open-system approach usually believe that innovation needs trump concerns about security, compromised experience, or potential business conflicts of interest. Companies taking this approach also tend to be startups that lack brand recognition and distribution channels. By following an open API strategy, companies can build an ecosystem of partners rapidly and make a platform’s ability to innovate and disrupt a main selling point to business customers.

As is the case in many other industries, a platform that adopts an open API strategy at the beginning may choose to tighten up API usage rules after it reaches sufficient scale. Therefore, it is not surprising that in the smart-home industry, the most popular platform-building approach is the one for Open System, Managed-Open API.

APIs are not only essential to consumer smart-home experience but also strategically important in smart-home platform players’ game plan. As the smart-home market is increasingly moving towards a battle among multiple ecosystems led by influential companies from the technology sector and the service provider industry, choice of API strategy can influence the size and growth of ecosystem and become a differentiator in competition.

[Update: An earlier version of this blog referenced Vivint and Honeywell as examples of closed system, and proprietary API. Both companies reached out to us to clarify their technical and business strategies related to API. We thank their contribution to our post.

Vivint explained that the company has changed directions since May 2015 to allow some third-party developers and device makers to use Vivint’s API for integration with its Sky smart home platform. Vivint API use, however, is not open and public. Vivint executive describes its approach as a curated process: they will screen developers and developers based on technical compatibility and user experience before giving them access to its API.

Honeywell executive Scott Harkins provided more insights into Honeywell’s API strategy. Honeywell runs its Lyric and the Total Connect Comfort (TCC) platform with an open and public API strategy, whereas its security system business—which runs on the Total Connect platform—takes a more conservative API approach with a highly curated process. He explained that the Lyric and TCC platform is much more open to developers and third-party device makers because it is a consumer-centric business. Apigee helps Honeywell host a developer portal for TCC APIs and Honeywell normally does not charge developers that build applications using this API. The security system side is distributed through the security dealer channel, and Honeywell is much more cautious about opening up the platform for public use for now, but works with selected partners for integration.]