The Search for Yodlee, Yummly, and Geek Squad in Consumer IoT
I was in a meeting this week where I was asked my view on the state of the Internet of Things (IoT) in the consumer market. It was an interesting question given that professionally I have been focused on enterprise and yet personally I am a consumer of IoT technology in my home. I have a Ring doorbell and an August lock installed in my house. Both have their challenges that only the tech-savvy individual can tolerate - it is these challenges that will delay mainstream adoption another 3-5 years.
There is a gap in the experience I have now versus the experience I expect. To close the gap requires a shift in how consumer IoT companies approach service integration and customer care. I will explain the shift I believe is necessary while illustrating the current gap with a few examples from my personal experience.
We are in the era of Web 1.0 when it comes to consumer IoT; the services and applications are standalone. Service Integration is a big technical challenge. Consumer IoT needs its own version of Yodlee. Yodlee is an aggregation service that allows users to see all their credit card, banking, investment, and other accounts in one place. The service is most widely known for its role in Mint’s success; enter your account logins from your portfolio of bills and banks to get a single view of your financial life. How does this apply to my connected home? Lets look at the Ring doorbell and August lock. My Ring doorbell is pressed while I am at work. I open the Ring app to discover that it is the delivery person with my new electric bike! I can see the delivery person via video and talk to them through the doorbell, asking them to put the package on the front entry to my house between the gate and the door. Next, I need to open my August lock app to unlock the gate to let the delivery person in. Two devices, two apps. Not integrated. This is why there is a need for a Yodlee-type service integration layer that manages my logins across my devices and brands that I use for my connected home. This means the firmware and applications need to have APIs and a cloud-based service to remove the hassle of handling various connectivity protocols.
Yummly is a recipe application to find recipes from across the web and save your favorites in a single repository. The app integrates nutrition data based on the recipe ingredients and then allows you to register your Jawbone device to track the calories you will need to burn during your workout. The app also integrates with Instacart to order the shopping list for the recipes and have it delivered later that day! Access to many services in a single place. Imagine this same type of simplification of the products and services across a connected home. Consumers could use industry leading products by category, and yet manage and optimize them all via a single connected-home app. The app could make recommendations to help you optimize your electric bill by analyzing your automated blinds, furnace and AC unit. It could reduce your water bill by coordinating the use of your washer, dishwasher and sprinklers. The connected home app would also facilitate the management of your home safety (locks, cameras, etc). There are a few attempts in this area that exist today. Octoblu has an interesting model for drag and drop automation of workflows and Smarthings which standardizes integration via a hub - I am sure there are more, but none of them are where the industry and the consumer needs them to be to drive mainstream adoption.
The Target Open House in Yerba Buena Gardens in San Francisco has created a view of this future state. If you haven’t been there - you should go. There is a model home that you walk through and experience the automation we would all hope for - things just work - we don't see the integration, we don’t see the multiple apps - we get one experience.
The next big challenge is handling when things don’t work as expected -- customer care. The customer care required is a combination of Geek Squad, Genius Bar, and Zendesk. You need someone who can come to your home when things don’t connect to each other; you will need someone who you can take individual products to for repair, and lastly, you will need someone to call when you get locked out of your house because the firmware upgrade on your lock caused you to lose access! I love my August lock, but this did happen. Thankfully I had a key with me as a backup. Continuing on the August lock theme - it has a great feature that automatically unlocks your door based on proximity allowing for quick access on a rainy day or if you have your hands full and can’t get to your phone. One evening I set the phone on a table near the door. Throughout the evening I heard the door lock and unlock repeatedly about every 30 minutes. Thinking there was someone trying to break into my home I reviewed the log file on the application to see who was trying to enter our house. To my surprise, I was unlocking and locking the door. It took me a few minutes before I realized my phone’s proximity to the door was causing the lock to be activated. We submitted a bug to tech support and a few days later the problem was solved. There are usability challenges and technology kinks that will get worked out over time but the customer support offered will be critical to driving adoption.
None of the challenges in consumer IoT are insurmountable. They require some understanding of technology and a bit of patience right now. More importantly to drive mainstream adoption they will require someone providing the abstraction layer, someone creating the integrated application, and someone providing these three tiers of customer service.