A Blog by Jonathan Low


Oct 30, 2019

Why A Google Acquistion of Fitbit Wont Challenge Apple's Smartwatch

The issue is that Fitbit doesnt solve Google's strategic problem, which is not marketing, it's the inadequacy of its watch chips. JL

Dieter Bohn reports in The Verge:

Google is looking to buy Fitbit to bolster its wearables strategy. This acquisition portends a wearables reboot instead of shoring up Google’s smartwatch strategy. In terms of basic usability and features, Wear OS is a solid platform on which to rebuild if there were hardware to go with it.Google bet it could replicate the Android model with watches: distribute free software to companies that use readily-available components to create their own devices.That didn’t pan out. There’s only way to fix Google’s current smartwatch woes: it’s the silicon. I doubt Fitbit is sitting on a  processor that can save Google’s smartwatch.
Google is reportedly looking to buy Fitbit as a way to bolster its wearables strategy. Trying to suss out what this could mean for Google, its Wear OS platform, and Fitbit’s customers is (pardon the fitness pun) exhausting.
Here’s where I landed: Assuming it bears out, I think that this acquisition portends a wearables reboot instead of shoring up Google’s current smartwatch strategy. I think that mainly because Google’s current smartwatch strategy isn’t helped by Fitbit — at all. Unless Google has completely lost the thread, this acquisition only makes sense if the company is ready to try something completely different.
It certainly should be.
Let’s just recap how poorly things are going for Wear OS. Google’s most prolific partner in making Wear OS watches, Fossil, had a sub-five-percent marketshare in North America in Q2. Even if you give Google credit for some piece of the “Others” in Canalys’ estimates, that leaves Wear OS’ marketshare hovering somewhere between wince and woof.By subscribing, you are agreeing to receive a daily newsletter from The Verge that highlights top stories of the day, as well as occasional messages from sponsors and / or partners of The Verge.
Taken simply as a piece of software, Wear OS itself is actually better than many (including me!) have given it credit for, but it’s languished for so long that its software ecosystem bears all the hallmarks of a platform in decline. Even so, in terms of basic usability and features, Wear OS is a fairly solid platform on which to rebuild — if only there were hardware to go with it.
That hardware is not imminent. The best Wear OS watch hardware currently available is Fossil’s latest generation. Reviewing one of those watches, I discovered that many of Wear OS’ performance problems are solved simply by adding more RAM, though that doesn’t necessarily make it very fast.
But even with enough RAM to run (which few Wear OS watches have), the convolutions the new Fossil watches go through to get through a full day of use are amongst the silliest I’ve seen on any device. There are settings on settings, none of which should ever be visible on a smartwatch, much less necessary.
Those convolutions are necessary because Qualcomm has yet to provide a processor for smartwatches that is worth a damn. We spent years waiting for the Snapdragon 3100 that powers the Fossil I cite above, but it is still outdated at its core in terms of both speed and battery management.
A more recent rumor from XDA suggests that Qualcomm is developing a new chip that would represent a significant step forward — but that just puts us back to where we started. Do we — and does Google — really want to wait (again) for Qualcomm to come through?
Back when it first launched Android Wear, Google made a bet that it could replicate the Android model with watches: distribute free software to companies that could use readily-available components to create their own devices. LG, Motorola, and even Samsung all took a chance on that vision and it didn’t go well for any of them.
That model just didn’t pan out. I could be convinced that’s because the only way to make a great smartwatch is to be vertically integrated from silicon to software. You don’t need to just cite the Apple Watch to make that case, either. Samsung’s Galaxy Watch Active line is successful not because the Tizen OS is great (though it’s not bad), but because Samsung is nearly Apple-esque in its vertical integration on the smartwatch.
I could just as easily be convinced that Google’s original bet could have led to good smartwatches in the same way that it led to good Android phones. The problem in that scenario is that since the ecosystem didn’t develop, there was no incentive for component makers to support smartwatches. You could call it it a chicken and egg problem, but it’s actually simpler than that. There’s no reason for Qualcomm to raise chickens if nobody’s buying the eggs.
There’s only one way to fix Google’s current smartwatch woes: it’s the silicon, stupid. And while Google’s lack of control over processors didn’t hurt Android phones, it sure does seem to be holding back Android smartwatches.
I don’t blame Qualcomm entirely — from where I’m sitting, the company has acted rationally. It surely makes much more money focusing on smartphone chips, high-end chips that could lead to Windows on ARM, and tiny chips that are about to power an entire generation of noise-cancelling earbuds to compete with the just-announced AirPods Pro.
All of this history leads us to 2019 and the Fitbit rumor. I sincerely doubt that Fitbit is sitting on a revolutionary processor that can save Google’s smartwatch efforts. Google’s current smartwatch problems can’t be solved with Fitbit.
I think it’s much more likely that Google intents to just pivot to where Fitbit already is: selling cheaper, lower-end fitness trackers and basic smartwatches.
It’s a much better strategy than trying to take on the Apple Watch — or heck, even the Galaxy Watch — head on. Maybe Qualcomm will come through with that new chip, but Google would be silly to bet its entire wearables future on it. (If you’re wondering where that mysterious $40 million Fossil smartwatch technology acquisition fits into all this, join the club. We have hats!)
There’s another reason Google might want Fitbit: its dedicated user base. Hopefully Google sees them as a core group of customers to serve well with expanded, improved fitness offerings, so that they might evangelize Fitbit again. Hopefully it’s not to take whatever fitness data Fitbit has collected and collated and use it to troubling ends. Even with the rumors of a buyout still very fresh, that’s something that Fitbit users are already worried about.
I can’t entirely blame them. Since it’s so hard to know what exactly Google would do with Fitbit, it’s easy to assume the worst. If the acquisition turns out to be real, I hope Google will do a better job communicating its intentions than it did with Nest.
And I hope Google knows its intentions better than it did with Nest, too.


Post a Comment