A Developer's Guide for Connecting to Google Assistant and Amazon Alexa
If you’re building a new Thing, you already know you’ll need to support Amazon Alexa and Google Assistant. The connected home ecosystem in which your device will live will almost certainly have one or the other (or both) and your device will be expected to support Google Assistant or Alexa voice commands.
A Faster Way to Integrate with Google Assistant and Amazon Alexa
Your developers have already confirmed they can get the job done. Both Google and Amazon make integration a bit easier by publishing open interfaces and even define ‘Home Control’ standards that allow you to expose your device capabilities based on expected behaviors for the type of device you are building (i.e. All bulbs support On/Off control, all thermostats support setpoint and temperature control). Great - so the first step is to go to Google and Amazon and get started…
You could start there, and spend the time building integration to both services to support the capabilities expected of your device. But is there a faster/more efficient way to support Amazon and Google voice assistants?
Are burning integration hours to support these services the most valuable way to spend my development time? What else will come out that we’ll need to start supporting? And what might I be giving up in terms of visibility and relationship to my customers by building directly to these partners?
An IoT Platform Can Dramatically Reduce the Effort and Cost of Google and Amazon Integrations
An IoT Platform gives you a launching pad not just for rapidly deploying your connected device and experience, but also for rapidly supporting the third party services your users will use to interact with your device, including the major voice assistants, connected device automation apps like the free Yonomi app or third party aggregation hubs from partners like Wink, Vera or SmartThings.
IoT Platforms like Yonomi ThinCloud provide a simplified specification model for building your device representation and then automatically translate that spec into representative data and interaction models for all the services you’ll need to support, including Google and Alexa - as well as your own mobile experience.
The model abstracts your device definition from 3rd party services, is dynamic and mutable and readily conforms to existing IoT device type rationalization standards like dotdot or OCF. You also gain the advantage of seamless support for new ecosystem partners as they enter the market and gain traction - so you’re never left out of a new trending experience - and without touching your device code or existing mobile and voice experiences.
This means your developers spend no time building the integration to these services, and instead focus on building great device experiences for your customers.
Just as important, by taking control of and standardizing the interaction model with third party services, you’re never left out of the loop on the relationship with your customer or the ability to improve their device experience.
For more information on how an IoT Platform can help jumpstart your Google Assistant, Amazon Alexa or other 3rd party connected home solution strategy, check out Yonomi ThinCloud.