Android's AI Era: Hype vs. Architecture

I have spent the last year and a half building against Android's agentic APIs, not reading about them from a keynote seat. Be nice got an AppFunction so Gemini could invoke createAppPair directly; a few months later, bumping a single alpha broke it, because alpha10 quietly stopped shipping the service component alpha08 depended on . That scar tissue is a decent filter for keynote language. So when Android's president, Sameer Samat, describes the platform moving from an operating system to an intelligent system, I try not to start with whether that's true. I start with which layer of the stack that sentence is describing, because "Intelligence System" covers at least three very different things at once, and only one of them is finished enough to build on. Three Claims Wearing One Name Layer one is the model runtime: what executes on the device, which APIs call it, how stable those APIs are. Layer two is app integration: how an app exposes itself to an agent, and how much of that exposure the app developer controls versus how much Android does for them without asking. Layer three is distribution: who gets to be the agent standing in front of the user, and whether that's a genuinely open contest or a foregone one. Google's own framing blurs all three into a single narrative arc. The February 2026 "Intelligent OS" post redefined what success means for an app: not opens, but completed tasks, with or without a human touching the UI. Android's May I/O recap made the platform claim explicit: agents like Gemini can already "complete task automation" on Android, navigating an app on the user's behalf without anyone tapping through it themselves. One sentence, three separate engineering claims bundled together. I want to pull them apart in the order I trust them least to most, which also happens to be the order in which the marketing runs furthest ahead of the shipping code. Layer Three First, Because It's the Weakest: Who Gets to Be the Agent Start with distribution, since th