Model Releases
Spent Tuesday watching @Google I/O thinking about a question. If you build on @Android, what just changed for you? Short answer: your screen…
Spent Tuesday watching @Google I/O thinking about a question. If you build on @Android, what just changed for you? Short answer: your screen belongs to Gemini now. After this week, Google owns the AI,
Spent Tuesday watching @Google I/O thinking about a question. If you build on @Android, what just changed for you? Short answer: your screen belongs to Gemini now. After this week, Google owns the AI, the operating system, the browser, the app store, and a phone that competes with every device you ship. The data your users generate trains the same model. If you build hardware on that stack, your device starts to look like a user acquisition channel for Gemini. The screen you fought to win belongs to whoever Gemini decides to surface. Your users belong to whoever trains on their data. Android used to be open source. That was the antitrust defense. In practice, the GMS and Play Store is the lock-in. Ship Google's version of Android or lose the Play Store, and without it you do not have a viable phone. We have seen this play before: @Microsoft and Internet Explorer on @Windows, Google and @googlechrome on Android. Each time, the platform's interface layer became its distribution moat and the pattern repeats. The stakes are bigger now, because an assistant is a deeper relationship to the user than the browser. Every OEM and silicon partner we talk to wants the ability to choose what AI runs on their device, and the right to keep user data on the device. None of that exists by default in what shipped this week. So they will find it elsewhere. The initial point of Android was optionality for the user. That is what we are keeping alive. On-device action AI. Any screen. Any app. Any OS? More soon.
Source: Div Garg (X) | 2026-05-21