LastLast week, I wrote about Google’s somewhat confounding hardware strategy in the wake of a report about internal conflict from The Information. But I did something else right after that: I interviewed Google and Alphabet CEO Sundar Pichai on The Vergecast with Nilay Patel.
The whole interview is worth a listen, of course. Pichai is in charge of one of the most important tech companies in the world, and Big Tech has taken on such an outsized role in our lives that it’s only natural that it’s taking on an outsized role in the coronavirus response. We spoke to Pichai about that and also about the recent report about Google’s flagging diversity efforts.
And he definitely made fun of me for being obsessed with RCS Chat before getting into his thinking on Google’s communication apps. So give it a listen; it’s in our feed.
But here in this newsletter, I want to zoom in on Pichai’s responses about Google’s hardware division because I do think they’re illuminating — not in a sharp, spotlight kind of way but in a soft glow on the horizon kind of way. Not to belabor the metaphor, but when it comes to Google’s hardware efforts, there’s a bit of a “darkest before the dawn” vibe.
I asked specifically about the Pixel, but Pichai wanted to put it in a larger context. I’m quoting the beginning of his answer in full here because I think it contains the seeds of the rest of our discussion:
The last couple of years have been a major integration phase for us because we’ve combined our Google hardware efforts with Nest. We absorbed the mobile division of HTC. So it’s been a lot of stitching together. And we have a wide product portfolio, too. So it’s definitely been a building phase. We’re super committed to it for the long run. Hardware is hard. And it definitely has components, which take real time to get it right, thinking about underlying silicon or display or camera or any of those tacks. And so we are definitely investing in it, but that timeline. I think we’ve made a lot of progress.
Pichai’s not wrong that the hardware division under Rick Osterloh has had a lot of corporate distraction. The HTC mobile division was acquired in 2017. Osterloh has said the first phone to fully come out of that division was the Pixel 3A. And Google made the public announcement that it was reabsorbing Nest from Alphabet almost one year ago.
So, fair. There’s been a lot going on. But if there’s a “getting in your own way and squandering an opportunity” example worthy of a canonical Harvard Business Review case, Google’s handling of Nest is it. You would think that a company as big and multifaceted as Google (to say nothing of Alphabet) would be able to walk and chew through an internal merger at the same time.
One of the reasons that it’s been frustrating to watch the Pixel struggle to catch on is that smartphones seem like a solved problem. That’s obviously an oversimplification at best, but companies big and small crank out Android phones at a dizzying pace every year — hell, every week. You’d think Google — Google! — could figure it out.
“Hardware is hard,” Pichai says. It is. And just adding more engineers and resources doesn’t necessarily make it easier. Still, explanation isn’t absolution, and I think Google’s hardware division could have done more over these past few years.
All that history is what it is. What’s most important about the exchange is when Pichai answers the question I posed last week in this newsletter: what is Google hardware for? It turns out that, as with many things in tech, what you think is the obvious answer turns out to be the obvious answer. Or three answers, as it happens. Emphasis mine below:
So for me, three reasons. One is to drive computing forward. The second is we really guide our ecosystem. Pretty much everything we’ve done well, you can go all the way back and Android’s early days, Samsung Galaxy Nexus, which we worked together, was a pivotal phone. Nexus 7 in the tablet world. I can point to Chromebooks — all along, we did our original hardware to kind of bootstrap it. And I look at areas maybe where we haven’t done opinionated [work] — maybe [smart]watch is a good example where we haven’t. And then you can see it’s tough to guide an ecosystem to what your vision of it is, just building the underlying platform.
So I think that’s the second reason. And third is to really build a sustainable hardware business. I think all of it is important, and that’s how I think about it. And I’m excited. Rick [Osterloh] and team, working closely with Hiroshi [Lockheimer] and team, they have that long-term view. So we’re pretty committed to it.
If you’ve been watching Google’s hardware efforts over the years, there is just so much you could unpack here. The admission that Google squandered its first-mover advantage in smartwatches. The fact that the first two reasons are the exact reasons Google created the Nexus program before the hardware division existed. The idea that Google needs to do “opinionated” work (which I’d distinguish from just trying to make the flat-out best thing possible).
Finally, there’s the part of the original quote where Pichai looks ahead, talking about components “which take real time to get it right, thinking about underlying silicon or display or camera or any of those tacks.” Later, he adds: “Because some of the deeper efforts we are putting in will take three to four years to actually play out. And when they come in, I think I’m excited about how they will shape where we are going.”
When I think about investments that “will take three or four years to actually play out,” I wonder what they might be, especially in the phone space. Maybe this is just wishful thinking, but to me, there’s only one Android component that really fits the bill: the processor.