Google Needs to Force It's Own Medicine
There is a long-running argument in the tech community that the only way Google will ever truly make the Pixel beat the iPhone is by enforcing strict, company-wide dogfooding. If every single Google engineer and product manager were forced to put down their personal iPhones and carry a Pixel, the daily friction, the minor UX bugs, the random stutters, the hanging processing would get fixed overnight.
When you don't use your own product every day, you lack the empathy required to fix the papercuts.
We actually saw a perfect case study of how this forced internal exposure forces rapid improvement. Earlier this year, a Google engineer caused an uproar when they openly admitted how much better a competitor's tool solved an internal infrastructure problem.
"I'm not joking and this isn't funny. We have been trying to build distributed agent orchestrators at Google since last year. There are various options, not everyone is aligned... I gave Claude Code a description of the problem, it generated what we built last year in an hour."
That brutal realization, having to grind through internal constraints while knowing exactly how far behind Google's models were compared to Anthropic, is exactly what forces a company to wake up. That internal friction directly catalyzed the rapid, aggressive updates that made Gemini a legitimate heavyweight. I'm sure Apple does the same thing. I've heard that culturally, Apple strongly encouraged using Apple products and it makes sense. How can you be good at your job at Apple if you don't even use Apple products?
Software gets good when the people building it are forced to survive in its ecosystem. If Google wants the Pixel to truly continue making the platform the best of Google, it’s time to take the iPhones away from Mountain View, at least from every team that isn't part of the Google for iOS team. Soon I think this should even apply to Chromebooks and Googlebooks.