Google Assistant → Gemini
A decade-old voice retires
on September 4.
Google Assistant, which launched in 2016, has been told it's leaving Android. Its successor is Gemini — but not every device is in scope, and the line between what switches and what doesn't is sharper than it looks. Per reporting from 9to5Google and others, Google will begin a phased shutdown of Assistant on Android starting September 4, according to emails sent to users.
The Announcement
Why this became a "next month" story
Not a rumor — a dated notice landed in inboxes.
Google emailed affected users to confirm that Google Assistant is being "discontinued," and that Gemini is now "the assistant experience on Android." According to 9to5Google's report, the rollout begins September 4, 2026, spreads over several weeks, and once a device has switched to Gemini, there is no way back to Assistant.
Gemini itself isn't new — it debuted as Pixel 9's default assistant at Made by Google in August 2024 and has expanded device support since. What makes this announcement significant is that the era of "choosing" Assistant is ending; Gemini becomes the only voice interface on Android. Gemini was originally supposed to fully replace Assistant by the end of 2025, but the complete transition slipped into 2026. For a voice that had been Android's default for roughly a decade, it's a quiet exit.
| Switches to Gemini | Assistant stays (out of scope) |
|---|---|
| Phones and tablets | Smart speakers and smart displays |
| Wear OS watches | TVs (Google TV) |
| Compatible earbuds and headsets | Cars with Google built-in (Android Automotive) |
| Android Auto (projected) | — |
By The Numbers
The switchover, in numbers
A rollout spread over "several weeks" also means it won't hit everyone the same day. TechRadar's confirmation piece stresses that this has moved past rumor status into an official date — but exactly when your own device gets the notice still depends on rollout order.
Who It Hits
Who this affects, and how
Some people can just wait it out. Others should act first.
Engineers and developers
Teams that built on Assistant Actions or Conversational Actions integrations need to check migration paths now — leaving it alone means the invocation flow disappears after September.
Everyday users
There's nothing you need to do. When the rollout reaches you, the device switches to Gemini, and some previous voice tone and command phrasing may change.
Car and smart-home users
Cars with Google built-in and smart speakers are out of scope — Assistant keeps running there. Behavior can split across devices within the same household.
What's Next
What to do next, and what's still unclear
There are three near-term recommended actions. First, on any device that's already received the notice, check early whether the Assistant routines you rely on (alarms, routines, smart-home commands) behave the same way under Gemini. Second, developers with Assistant integrations should follow Google's Gemini migration guidance and line up a replacement API path. Third, teams that build voice control into their workflows should trial Gemini's responses before the switch actually lands on their devices.
There's also a counter view and risk worth naming. While Gemini is stronger at conversation, some early feedback points to the routine-task snappiness Assistant built up over the years — instant timer or smart-home responses — feeling slower in comparison. The fact that the full migration, originally targeted for late 2025, slipped into 2026 is itself a sign that the transition proved harder than Google's own estimate. And "starts September 4, rolls out over several weeks" still leaves room: no exact date has been published for when every device will have finished switching.
This isn't the first time a voice interface has consolidated into a single AI assistant, but drawing the scope this explicitly — and shipping it as a one-way, non-reversible change — is a template other platforms may study. Treat it as the moment OS-level assistant consolidation moved from experiment to default.