The Most Important Decision You Will Make—How to Build the Cloud Platform for Your Connected Home Device
It’s a common scenario. The pressure to get your connected product to market is real. The true cost of delaying your product launch is in the millions. One month of delay could give the competition the edge they need.
The product team agrees that Amazon Alexa is the biggest player out there, so integration with them is a must have and enables instant access to millions of users. It makes sense to start there. Low risk right? What could go wrong?
AWS is the answer, right? You read some blogs, checked out some templates. There seems to be a quick and dirty way to stand up the cloud service to get your device integrated with Alexa. Quick and dirty turns into a slog, consultants are brought in, weeks go by, you fire the consultant and hire another... The product receives “Works with Amazon Alexa” certification just in time!
The weeks pass, product sells, and customers start giving you feedback and product suggestions that unfortunately you can’t solve for…
"Alexa is telling me that your device is not responding..."
"I’ve got the *other* wizz bang voice assistant. It’s not finding your device? Can you help?"
Oh and by the way, the AWS bills are coming in and they are… surprisingly large and growing fast.
IoT Vendor Lock-in, It hurts
So what’s the problem? The team realizes the product is suffering from vendor lock-in. It’s a one trick pony.
Focusing on the Alexa use case for launch meant the team didn’t scope for future integration scenarios. As a result, the product team has limited its ability to adapt to current and future customer use cases. For example, the product doesn’t have the hooks in place to integrate with Google Home/Google Assistant, or that other voice assistant that everyone is talking about. And what about the next thing? And the next?
And it’s not just new voice assistants complicating the IoT ecosystem and making navigating the right choices as a product owner difficult. The IoT space is growing and changing at the speed of, well, the absolute cosmic speed limit - blazing speed.
Building on an Open IoT Platform is Critical
This is a typical scenario we hear all too often from partners who, after the fact, approach Yonomi. What they realize is that they don’t need to sacrifice speed to market for market reach, product flexibility and agility. The lesson. In the IoT market, new players and use cases are a given. Architecture matters, so you’ve got to get it right. Not just for universal compatibility but, critically importantly, for affordability!
An open IoT platform is just that, open. So you can integrate with just about any provider (software or hardware) and meet just about any use case. And Yonomi ThinCloud’s serverless architecture keeps costs to a minimum.
As a device manufacturer, the current context is Google Home, Alexa, HomePod… but what’s next? Is your system open so you can integrate with the next cool new thing that happens to have just launched, yesterday?
With Yonomi ThinCloud, it will be.
Check out our free guide to building a connected device!