SwitchAI: a selector for Android's digital assistant role

What SwitchAI actually solves on Android

Android lets one app hold the digital assistant role. Whichever app claims that role answers the long-press of the home button or the swipe from a bottom corner, and changing it means a trip through system settings. SwitchAI sits on top of that role and turns it into a menu. The README describes it as an app that lets you "easily select, start, and manage your preferred AI digital assistants," either by choosing one on the fly with a single tap or by setting a default for the system assistant feature. The audience is narrow but real: people who keep ChatGPT, Gemini, Claude or a regional assistant installed side by side and want the trigger to reach a different one depending on what they are doing. It is not an assistant. It does not answer questions, hold a conversation, or ship a model. Everything it launches is another app already on the device.

How the selector and the assistant role fit together

The mechanism is package and class launching rather than any kind of API integration. The README states plainly that "SwitchAI launches these apps using package and class names," which explains both the breadth of the support list and its fragility. The app holds a catalogue of roughly 40 assistants with their package identifiers, from com.openai.chatgpt to ai.perplexity.app.android, and starts the matching activity when you pick an entry. Two modes sit on top of that catalogue. In one, you set a default and the system assistant trigger goes straight there. In the other, the assistant selector intercepts the trigger and asks which assistant to use that time, which the README frames as useful for optimizing different workflows. Voice input is passed through to assistants that support it. Shortcuts, home screen widgets and Quick Settings tiles are entry points into either the chosen assistant or the selector itself. Because the whole thing depends on package names, an app that renames its package or changes its launch activity can drop out of the catalogue, and the README warns that if an app is not installed you may see an error and be prompted to install it.

Installing SwitchAI and setting a default assistant

SwitchAI is distributed through GitHub releases, not the Play Store. The README's Download section points at the releases page and a Telegram channel, and the repository carries the usual Gradle wrapper and build files (build.gradle.kts, settings.gradle.kts, gradlew) for anyone building the APK from source with Android Studio. There is no published package name for a store listing in the README, so the release APK is the path most users will take. After installing, open the app and pick your assistant from the list. Then hand it the system role. The exact settings path differs by OEM, but the flow is the standard Android one: open Settings, search for the digital assistant entry, and choose SwitchAI as the assistant app. Once SwitchAI holds the role, the selector prompt appears when you trigger the assistant. The README's feature list is the reference for what you should see: a Material 3 Expressive selector, home screen widgets, and Quick Settings tiles for the chosen assistant or the selector. If nothing appears on trigger, the first thing to check is whether the assistant you want is actually installed, since SwitchAI matches on package name and cannot launch an app that is not there.

Where SwitchAI breaks or is the wrong choice

The package-name approach is the main limitation, and the README is honest about it. App availability varies by region and device, so a user in one market may find that a listed assistant is simply not installable, and the entry becomes a dead link that produces an error and an install prompt. The catalogue is also a snapshot: assistants ship new package names, and a list maintained by hand will lag behind them. There is a second, quieter issue. SwitchAI depends on Android's digital assistant role being assignable to a third-party app. Some manufacturer builds restrict or repurpose that role, which is outside SwitchAI's control. If you want an assistant that works without any other app installed, or if you expect the selector to unify the assistants' own interfaces, SwitchAI is the wrong tool. It is a router. Every conversation still happens inside the app it launched, with that app's account, history and limits.

SwitchAI compared with setting a default in system settings

The obvious alternative is doing nothing: pick one assistant in Android's own settings and live with it. The difference is in what happens at the trigger. The system setting is a single fixed choice, changed by going back into settings each time. SwitchAI keeps the same role but adds a decision point at the moment of use, plus widgets and tiles that skip the system gesture entirely. That is a genuine difference in approach rather than a cosmetic one, because it moves the choice from configuration time to use time. The cost is an extra tap and an extra app in the chain. If you only ever use one assistant, the system setting is simpler and has one less component that can fail. The other alternative is the project's own ancestor: the README describes SwitchAI as a continuation of Plugin-VoiceGPT with "extensive support for assistants apps and much more features," and that branch still exists in the repository for anyone who wants the older, narrower behaviour.

Licence, maintenance and upgrade cost

SwitchAI is licensed under GPL-3.0, which matters if you plan to redistribute a modified build: derivative works you distribute have to carry the same licence and source. Using the app as-is on your own phone carries no such obligation. On maintenance, the repository is not archived and the last push was on 2026-07-11, which is when release 4.1 landed; before that, 4.0 shipped on 2026-03-30 and 3.4.1 on 2025-11-17. That is roughly a release every few months, so treat the supported-assistant list as something that gets refreshed on that cadence rather than continuously. Upgrading is a matter of installing the newer APK over the old one, since there is no store channel described in the README that would handle it automatically. The practical upgrade cost is rechecking the assistant list after each release, because that list is the part most likely to change and the part your daily use depends on.

Editorial conclusion

SwitchAI suits Android users who already have several assistant apps installed and want the long-press or swipe-up assistant gesture to reach the one they actually use, plus anyone who prefers a selector prompt over a fixed default. It is the wrong tool if you expect it to provide an assistant, run without the target apps installed, or work identically on every OEM build, since the README notes availability varies by region and device. Before adopting it, confirm that your device exposes a changeable digital assistant role, that your preferred assistant appears in the supported list, and that the package names match what is actually installed on your phone.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes