Google has now confirmed what most of us already suspected. The Google Assistant is officially leaving mobile devices, with the process starting on September 4.
I received the email last week. The language was polite but firm. From September 4, Google begins removing Assistant access from Android phones and tablets. The rollout stretches over a few weeks, so do not panic if yours still answers on the fifth. The end is scheduled, though, and it is not coming back.
Here is the part that actually matters: this is less a shutdown than a swap. Assistant gets replaced by Gemini, but only if your device meets the hardware requirements and you happen to be in a supported region. That second condition is doing a lot of quiet work. Not everyone receives the upgrade.
I have used Google Assistant since the Nexus era. It was never great, exactly. Sometimes it misheard me. Sometimes it sat in silence when I asked for a timer. But it covered the basics, things like weather, hands-free texting, and turning off the lights, and that is precisely why people will miss it. A voice assistant does not need to be smart. It needs to be there when you call it.
What actually breaks on September 4
The cut is not limited to phones. Wear OS watches lose Assistant. Wireless headphones lose it. Android Auto loses it in most cars. The exceptions are Google’s own car platforms, Google Home devices, and Google TV, which keep it for now.
If you drive with Android Auto and navigate by voice, that is the piece I would plan around first. On most setups your phone’s assistant and your car’s assistant were the same service. After the swap they may no longer be, and if you are in an unsupported region they definitely will not be. The honest answer for those users is that Google has no fallback ready. You keep the old behavior until it stops, and then you go back to tapping the screen.
The rollout is also not a software update you can simply defer. It is per device, so two phones in the same home on the same account can run different assistants for a few weeks. If you are the person everyone calls when their phone acts up, expect that phone call.
There is a group I keep coming back to, and it is not the gadget enthusiasts. It is anyone who depends on voice to operate a phone at all, people with limited hand mobility, or anyone who has built an entire daily routine around spoken commands. Telling them to just use the new one quietly assumes the new one runs on their hardware. For a large number of people, it will not.
Is Gemini actually better?
I moved over a few months ago to test it, and the result is mixed. Some parts are genuinely improved. The conversational flow feels more natural, and it holds on to follow-up questions instead of resetting after every line. But it is slower on older hardware, and it produces confident wrong answers in ways Assistant never did. Assistant would simply tell you it did not understand, which was annoying, but at least it was honest about the failure.
Google first planned this shutdown back in 2025 and delayed it. Maybe Gemini was not ready. Maybe users were not. Either way, the extra time did not change the outcome. Assistant is heading to the Google Graveyard, parked next to Reader and Inbox.
What I find revealing is how Google handles these transitions in general. There is no opt-out. There is no keep the old one if you prefer it switch. They flip it and tell you to adapt. From a business standpoint I understand it, because running two AI systems costs real money. From a user’s standpoint it is simply something that happens to you.
I have written before about where Google is pushing Gemini next, and the pattern is consistent. Every surface eventually becomes a Gemini surface.
What you should do this week
If you are already using Gemini and it works for you, nothing changes. You are ahead of the curve, and the migration will feel like nothing happened.
If you are still on Assistant, you have until September 4 to decide. You can upgrade to Gemini where it is available, or you can accept that your phone’s voice assistant is going away. Before you upgrade, check two things: your Android version and your region. If either is unsupported, the upgrade will not appear, and no amount of waiting will fix it.
If you are outside Gemini’s supported regions, you are effectively out of luck for now. The practical move there is to pick a different voice tool that works in your country rather than hoping Google expands the list soon.
Before September 4, it is worth checking what you actually rely on Assistant for. Open the Google Home app and look at your routines. Anything that fires on a spoken command will need Gemini or a manual replacement. Smart-home users who built lighting or thermostat control around voice phrases are the most exposed group, because those routines rarely survive a platform swap without someone rebuilding them by hand.
The real story here is not the date. It is what the swap reveals about Google’s strategy. The company is betting everything on large language models. Assistant was not retired because it was bad at being a voice assistant. It was retired because it could not hold context, and in Google’s current view that now counts as broken.
My actual concern is cost. Gemini is expensive to run in a way Assistant never was. Google has already started charging for the advanced tiers, and I do not believe the basic tier stays free forever. The day basic voice access lands behind a paywall is the day I start looking at alternatives in earnest.
For now I am staying on Gemini. It is not perfect, but it is good enough, and on Android I do not have a clearly better option. I will keep using it and watch what happens next. If Google raises prices or lets quality slip, I will post an update here.
