Google Just Removed an Assistant Millions Used

On September 4, 2026, Google started removing Google Assistant from Android phones, tablets, Wear OS watches, headphones and Android Auto projected from a phone. Gemini takes over. The line in Google's notice that matters reads: once availability is removed, you will no longer be able to use or switch back. Users were emailed on August 4, giving about a month.

What is actually changing

Google described Assistant as being discontinued and Gemini as now the assistant experience on Android. Removal began September 4 and Google says the process may take a few weeks to reach everyone, which is why some devices still have it and others do not.

The scope covers Android phones and tablets, Wear OS smartwatches, headphones, and vehicles running Android Auto projected from a phone. Cars with Google built-in are exempt and keep Assistant working past September 4. Google says the change does not yet apply to other form factors, and that Gemini is coming to Google TV devices and to Google Home speakers and smart displays.

Reporting at the start of September noted that a "Switch to Google Assistant" option was still appearing in the Gemini app for some users. That reflects a gradual rollout rather than a supported way to stay, and Google's own wording says the switch back goes away with availability. The deprecation was also originally planned for the end of 2025 and pushed to 2026, so anyone who read the first announcement and concluded it would slip again was wrong twice over.

Three places it might actually bite

Most offices will not notice. Three situations are worth checking before someone discovers them in a van.

Drivers using Android Auto projected from a phone. This is the group most likely to have built genuine habits: hands-free calls to the next customer, navigation to the next job, a message sent without touching the screen. The interaction model changes, the phrasing that used to work may not, and this is happening while somebody is driving. Tell the affected staff before it reaches their handset.

Wear OS watches in warehouses, kitchens and job sites. Anywhere hands are full or dirty, a wrist assistant is doing real work. Worth ten minutes of testing on one device to see what still responds.

Routines wired into something operational. A voice command that turns on shop lights, sets an alarm, or triggers a smart plug. Automations built on top of a free consumer product are exactly the kind of quiet dependency nobody documents, because the person who set it up did it in five minutes and never mentioned it.

The general version of this problem

Google Assistant shipped in 2016 and was installed on a very large number of devices. Scale, incumbency and a trillion-dollar parent did not keep it alive. Whatever you are building on now has less of all three.

We have written about the same shape twice this year, when OpenAI shut down Sora six months after launch, in what the Sora shutdown teaches, and when an acquisition changes who owns the tool you depend on, in the consolidation wave. The pattern repeats often enough now that treating it as a surprise each time is a choice.

The honest caveat: a paid contract is not immunity. Paid products get retired too, and the difference is procedural rather than absolute. What a contract usually buys is a notice period, an export path, and someone obliged to answer the phone. A free account buys an email a month before, which is what Assistant users got.

Build a deprecation register

One page, five columns, updated twice a year. It takes an hour the first time and about fifteen minutes after that.

The fourth column catches more problems than the rest combined. Plenty of tools advertise an export that turns out to produce a format nothing else reads, and you find that out at the worst possible moment. Test it once while nothing is wrong.

For the AI layer specifically, keeping switching costs low is its own control, which we set out in hedging against model lock-in. The related question of which tools are free and what that costs you is in free AI tools and what they cost your business.

What to do this week

Ask your drivers and your field staff whether they used voice on Android, and warn them it is changing. Test one Wear OS device if you issue them. Then spend the remaining forty minutes on the register, because the assistant was never the expensive dependency and the exercise is worth more than the incident.

Frequently Asked Questions