What should still work when Gemini replaces Google Assistant?
Ars Technica reports Google will begin retiring Assistant on Android on September 4, moving phones, watches, headphones, and Android Auto toward Gemini; the change may take weeks. Google framed this move as a way to bring more capable help to mobile. Fine. But “set a timer,” “call home,” and “take me there” should not become little conversations you have to supervise. I would want a blunt migration card: which ordinary commands changed, what still works offline or without a chat, and how to turn voice control off when it is slower than doing it yourself. A smarter replacement that turns a four-second chore into troubleshooting has taken something, not added it. What would you test first?
Comments
My first test would be a boring reminder: ‘tell me at 7 a.m. to bring the library books.’ Set it with the phone locked, then check that it lands where normal reminders live and can be changed without reopening a chat. If a one-sentence chore turns into ‘where did Gemini put that?’, it did not replace an assistant. It hid it.
Google’s 2025 announcement only says Gemini supports more of the most requested features, naming music, timers and lock-screen actions. It does not provide a command-by-command compatibility list across phones, watches, cars and headphones. For a migration test, capture the device, surface, account setting, network state and exact phrasing—not just “timer failed.” Otherwise rollout gaps and broken behavior become the same unfixable complaint.
The test should happen with your hands busy, not with the phone on a desk. Start a timer while draining pasta. Call home at a loud curb. Ask for the right entrance with the phone in your pocket. When Gemini hears the wrong thing, can you stop it before the call or route changes? That recovery is what makes a voice tool feel faster instead of more clever.
Google can sell Gemini as a smarter assistant, but Assistant was a reflex. People notice a reflex only when it fails in the car, with groceries in both hands, or while trying to call someone quickly. The honest migration message is not a feature parade. It is a short list of routine things that will behave differently—and a clear way to leave voice control behind if that trade is not worth it.
The fallback cannot assume a screen. For some people, voice is the usable route when their hands, attention, or vision are already occupied. If a basic command changes, ‘open Gemini and try again’ is not recovery. Put the affected hands-free tasks in plain language and let people keep or disable them before a failed call teaches them the difference.
On a company phone fleet, I would test the boring support call: someone says the timer, call, route, or hands-free control stopped working. Can the help desk tell whether it is a changed command, a setting, a device limit, or a network issue without sending them through another chat? A migration has gone badly when simple requests turn into tickets nobody can close.