Pere Villega bio photo

Pere Villega

If at first you don’t succeed; call it version 1.0





Wearables: Google vs Apple

After a weekend wasted in bed (food poisoning sucks) I’ve spent some hours catching up with tech news. And I’ve found a very interesting, if brief, comment about a new war between Apple and Google that may impact their success in wearables.

If you read this post you may notice something very relevant in the way Apple and Google are managing their ecosystem. I am talking about this fragment:

A telling difference between Google and Apple: Google Now becomes a more robust platform with 70 new partner apps. Apple takes an app-centric view of the world and Google not surprisingly takes a data centric view. With Google developers feed Google data for Google to display. With Apple developers feed Apple apps for users to consume. On Apple developers push their own brand and control functionality through bundled extensions, but Google will have the perspective to really let their deep learning prowess sing. So there’s a real choice.

I’m aware that at first glance this seems a minor difference, just the standard approach both companies have when treating their apps and their ecosystem. But this week brings some additional context: you may have noticed Twitter swamped by images of people showing off their Apple watches. And, in that context, this difference in approach becomes much more relevant.

Let’s assume that wearables are here to stay. One of their selling points is to streamline your access to app notifications, making it easier to act on them. On the other hand, you don’t want to get swamped by alerts as they become distracting and may drain the battery too fast. Thus, you expect only relevant alerts to appear in your fancy watch.

And here comes the big difference in approach: with Apple you relay on developers behaving nicely and not swamping the user with notifications. You expect them apps to be smart and show only what’s relevant. This may require each app to learn about each user’s preferences, which in the current era of machine learning is not hard, but it means each app needs to do this. And I won’t comment on expecting apps not to spam you, we all have our experiences on that.

Google’s approach (unless misunderstood) seems to be radically different: let’s remove the burden of learning about user preferences from the app, we will take care of that via Google Now. You just send us the data and we will send the relevant alerts. The impact for developers is massive: you don’t need to develop your own machine learning process, you can rely on Google’s far superior pool of data and expertise. And you don’t have to be worried about how many notifications are too many, Google will adjust that by tailoring notifications, taking decisions based on data that is not available to you but to which they have access, due to aggregation.

They say we are in the deep learning era, where personalisation is the key for success, and this includes not only your experience with an individual app but also your experience with a device in itself. I feel Google’s approach is a winner. It allows developers to stop worrying about notifications and how relevant are they, and focus on the app itself. At the same time the user will get a very streamlined experience, with relevant notifications at relevant times. I wonder if Apple needs to revisit their philosophy in this area.