Google Assistant shutdown on Android: Gemini takes over September 4

Google Assistant shutdown on Android begins September 4, and the practical result is simple: eligible Android phones and tablets will move to Gemini, while some connected devices will lose Assistant access. The rollout may take several weeks, and Google has not fully documented how existing integrations and automations will behave.

Gemini becomes the default mobile assistant

Google says it will remove access to Assistant from Android phones and tablets, with the change reaching users gradually. In regions where Gemini is available, devices that meet Google’s minimum requirements will receive the AI-enabled Gemini assistant instead. Once the transition happens, users will no longer be able to switch back to Google Assistant on those devices. The reported announcement describes the September 4 start date and the no-return transition.

For AI builders, this is more than a branding change. It moves the default voice entry point on Android from a relatively predictable command assistant to a generative AI layer. Teams that depend on voice-triggered actions, mobile handoffs, or Assistant-based discovery should treat the migration as a platform dependency change and test their workflows against Gemini rather than assuming behavioral parity.

The shutdown reaches paired devices too

The Google Assistant shutdown also affects devices that use an Android phone as part of the experience. Wear OS watches, headphones, earbuds, and cars running Android Auto will lose Assistant access, according to the announcement. Cars with Google built-in will retain Assistant for now, which makes the underlying car integration important when planning support.

Google Home and Google TV are described as unaffected. That leaves a split ecosystem: mobile and several mobile-linked endpoints move away from traditional Assistant, while some home and television products continue using it.

What builders should check now

Developers maintaining Android automation or voice-enabled features should inventory where Assistant is part of the user journey. Pay particular attention to wake-word flows, intents, device controls, onboarding instructions, and support documentation that tell users to invoke Assistant.

The immediate decision is not necessarily to rebuild everything around Gemini. It is to isolate the assistant layer from core application logic and provide a fallback where voice behavior, device availability, or regional access is uncertain. If a workflow is business-critical, a direct in-app action or an independent automation endpoint may be safer than relying on an undocumented transition path.

Important gaps in the rollout

The available announcement does not specify how third-party integrations, existing automations, or every Assistant-dependent feature will migrate. It also does not establish broader changes to devices outside the stated Android ecosystem. The September 4 date is a rollout start, not a promise that every user will change on the same day.

The useful takeaway for product teams is therefore narrow but actionable: audit mobile Assistant dependencies before the rollout, test Gemini where it is available, and avoid treating Gemini as a guaranteed drop-in replacement until Google publishes fuller compatibility details.