Google has begun notifying users that it will remove access to Google Assistant on Android phones and tablets starting September 4, 2026, with the rollout taking up to a few weeks to reach all affected devices (The Verge). Once access is removed, users will no longer be able to use or switch back to Google Assistant on their phone, tablet, or paired devices. The notification came via an email sent to some users.

The removal extends beyond phones and tablets. Paired Wear OS smartwatches, headphones, earbuds, and vehicles running Android Auto — the system that projects Android apps onto a car's built-in display — will also lose Google Assistant access. Cars running Google built-in, which embed Google's software directly into the vehicle's infotainment system, will retain access for now. Google Home and Google TV devices are unaffected by this announcement.

For users in regions where Gemini is available and whose devices meet minimum requirements, Gemini — Google's AI assistant built on a large language model — will be the only assistant available after the removal. Google framed the transition in its March 2025 blog post titled "The Assistant experience on mobile is upgrading to Gemini," describing the shift as offering "a new kind of help only possible with the power of AI" (blog.google).

This shutdown has been a long time coming, and it has slipped before. Google previously planned to end Google Assistant access on most mobile devices in 2025 but delayed that shutdown. A Google support document surfaced in November 2025 indicated that Google Assistant would remain available on Android Auto until March 2026 (9to5Google). The September 2026 announcement now replaces that timeline for Android Auto, bringing it into the same removal window as the broader mobile ecosystem.

The scope matters for developers and hardware partners, not just end users. Wear OS smartwatch makers, headphone and earbud manufacturers, and Android Auto integrators all built experiences on top of Google Assistant's APIs — the programming interfaces that let third-party software communicate with the assistant. The shift to Gemini on these devices means those integrations will need to migrate, and not all device categories are moving at the same pace. Google built-in vehicles retaining Assistant access while Android Auto loses it creates a split in the automotive experience: a car with embedded Google software keeps the old assistant, while a phone projecting into the same car's display via Android Auto does not.

For end users, the transition is effectively one-way. Google's email makes clear that once Assistant access is removed, switching back is not an option. Users on devices that do not meet Gemini's minimum requirements, or in regions where Gemini is not available, face an open question about what assistant capability remains. Google's announcement does not address those edge cases explicitly.

The broader context here is that Google is consolidating its consumer-facing voice assistant strategy around Gemini with a hard cutover rather than a gradual phase-out. The staggered rollout over a few weeks gives the migration some operational breathing room, but the end state is binary: Assistant goes away, Gemini is what remains where supported. For an industry that has watched Google maintain multiple overlapping assistant surfaces for years, the consolidation is notable in itself. Google Assistant launched in 2016, absorbed capabilities from the earlier Google Now, and became the default voice layer across Android, Wear OS, Android Auto, and smart home devices. A decade of iteration is being wound down in favor of a single successor built on large language models.

What remains unaddressed is the fate of Google Assistant on Google Home and Google TV, which are explicitly excluded from this shutdown. Whether those platforms eventually migrate to Gemini on a separate timeline, or whether Assistant persists as a distinct system for embedded and home contexts, is not detailed in Google's announcement. The retention of Assistant on Google built-in vehicles suggests a similar possibility for automotive platforms that do not depend on a paired phone.

For developers currently building against Google Assistant APIs on mobile and wearable platforms, the signal is clear: the migration window to Gemini is now bounded. The September 4 start date and the few-week rollout mean that by roughly October 2026, Google Assistant will be functionally absent from the Android mobile ecosystem and its paired-device periphery.

Worth noting: this is a significant moment for anyone who has relied on Google Assistant as part of their daily routine. Google is betting that Gemini can cover everything Assistant did and more. Whether that bet pays off will depend on how well Gemini handles the hands-free, eyes-up scenarios that made Assistant useful in cars, on watches, and through earbuds — contexts where a voice command needs to work reliably without a screen.