Google Assistant Will Go Dark on Android Starting September 2026

Google has told users by email that Google Assistant will begin shutting down on Android phones and tablets on September 4, 2026. Gemini takes its place as the default voice assistant across the Android ecosystem.

The rollback isn't instant. Google says the removal will roll out gradually over several weeks before every affected device loses access to Assistant entirely.

Once a device makes the switch, there's no going back. Google has confirmed that users won't be able to revert to the old assistant after Gemini takes over, making this a one-way migration rather than an optional upgrade.

The scope goes beyond phones. Gemini is also replacing Assistant on Wear OS smartwatches, headphones, and Android Auto in vehicles. Google TV, Home speakers, and smart displays are getting Gemini too, extending the transition into the living room and beyond mobile devices.

One notable holdout: Google Assistant will keep working in cars equipped with "Google built-in" software, at least for now. Google hasn't specified when or whether that carve-out will end.

A Delayed Deadline

This shutdown isn't happening on the original schedule. Google had initially targeted 2025 for retiring Assistant, but pushed the timeline back to September 2026, giving developers and users an extra year to adjust.

That delay suggests the transition carries more complexity than a simple feature swap. Voice assistants sit deep in a phone's default behaviors, third-party integrations, and smart home routines, and replacing one system-wide without breaking existing user habits is a nontrivial engineering lift.

Why It Matters

Assistant has been a fixture of Android since 2016, handling everything from setting timers to controlling connected devices. Its retirement marks one of the clearest signals yet that Google is fully committing to generative AI as the interface layer for its hardware and software stack.

For users, the practical impact is mostly about muscle memory and habits built around Assistant's command structure. Gemini's conversational style differs meaningfully from Assistant's more rigid, command-based interactions, so some workflows built around specific phrasing may need to be relearned.

Developers who built Assistant Actions or integrations will also need to track how Gemini's extension and app-connection model differs, since Google hasn't detailed a like-for-like migration path for third-party skills built on the old platform.