Most Android version bumps are about kernel updates, new APIs, and tightening security. Android 17 is different. It is the version where Gemini becomes a first-class system service — and that has cascading implications for every app on the platform.
Two notes upfront, because the reporting conflates them: Android 17 is the phone OS update, and Aluminium OS is a separate Google product — a desktop operating system for PCs (HP, Lenovo, Acer, ASUS confirmed) that happens to be built on top of Android 17[1][2]. They will be launched together at I/O but they are different products with different audiences. This post is about Android 17 on phones; Aluminium OS is its own thing.
Here is what I am tracking for Android 17, and what developers should be planning for.
Gemini as a system service
Android 17 introduces system-level Gemini context, surfaced through new APIs[3]. Apps will be able to:
- Request relevant context from the user's Gmail, Calendar, and Drive (with explicit permission).
- Surface AI-generated suggestions through new notification and quick-action APIs.
- Hand off complex tasks to the Gemini system service rather than calling the Gemini API directly.
The third one is the big change. Today, AI-enabled Android apps either bundle a local model (slow, bulky, behind the frontier) or call the Gemini API (fast but every call is a developer-side cost). With Android 17, apps will be able to call the system Gemini service — Google handles the billing relationship with the user (via their Gemini subscription tier), apps get high-quality AI without API costs.
The economics are very different. App developers may stop paying for AI per call. Users pay Google. (The exact billing model is still pre-I/O speculation; watch the keynote for the confirmed mechanics.)
App Actions become AI-mediated
App Actions are Android's mechanism for letting external surfaces (Assistant, Search, Now Playing) trigger actions in your app. In Android 17, App Actions are expected to become AI-mediated[3] — meaning Gemini can decide which app to invoke based on user context, not just on explicit voice commands.
Practical implication: if a user says "add this to my shopping list", Gemini chooses which app to invoke. If your app is registered with the right App Action, you get the user. If you are not registered, the user goes to Google Keep or whichever app is the system default.
This is a meaningful new acquisition surface — and a meaningful threat. Apps that win at App Actions integration will get more usage. Apps that ignore App Actions will see traffic siphon to AI-native competitors.
Proactive Assistance — system-wide notification ranking
Proactive Assistance[4] is Gemini-driven context that lives across the OS, not just in the Gemini app. Three concrete bits relevant to developers:
- Battery management. The system predicts which apps you will use next (based on calendar, time of day, location) and pre-loads them; unused apps get aggressively suspended.
- Notification ranking. Gemini ranks notifications by relevance to the user's current context. Apps that send notifications can no longer assume the user sees them.
- Home screen suggestions. The launcher surfaces apps and actions based on Gemini context, not just on usage frequency.
The shift is subtle but real. Android used to be deterministic — set X notification rule, user sees X notification. With Proactive Assistance, the system has a vote. Developers need to assume that not every notification will be seen, and that being visible on the home screen depends on Gemini's read of what the user needs right now.
What developers should ship by autumn
Five concrete actions for any Android developer:
- Register your App Actions. If you have not in 2025, do it now. Every app that touches a verb (add, schedule, find, book, send) needs to be registered as the right App Action target.
- Adopt the new context APIs (when documented). Apps that surface contextually-relevant data when the user opens them will retain attention better than apps that show the same thing every time.
- Audit your notifications. Cut anything that is not actively useful. Proactive Assistance will suppress noisy notifications harder than Android 16 did.
- Think about AI features that ship for free. If your competitor uses the system Gemini service and offers AI features that cost them nothing per user, you cannot win by bundling a paid OpenAI API call into every screen.
- Plan for the Gemini-pricing-tier-dependent user. Some users will be on AI Ultra; others on free Gemini. Your AI features need to degrade gracefully when the user has limited Gemini quota.
Aluminium OS — a separate developer opportunity
If you build Android apps that would benefit from a proper desktop form-factor — keyboard / mouse / large screen / multiple windows — Aluminium OS opens a new distribution surface. Google will be working with HP, Lenovo, Acer, and ASUS on launch hardware[1][2]. Apps that already adapt to ChromeOS / large screens will work on Aluminium OS on day one. Apps that don't will need to add proper desktop affordances to be visible there.
The honest read
Android 17 is the most consequential Android release for AI since the OS-level voice assistant work in 2017. The shift from "AI as app feature" to "AI as system service" is real, and it changes the developer-side economics in fundamental ways.
If you have an Android app, the next six months are about getting your App Actions registered, your notifications cleaned up, and your AI features rebuilt to use the system service. Apps that get this right will benefit from the Proactive Assistance surface area in ways they cannot match by API integration. Apps that do not will feel old.
The platform shift is real. Plan for it.