What the list reveals
A list of applications potentially compatible with Gemini's task automation feature has been disclosed by Android Authority, as reported by IT之家. The total count given is 134 apps, split between the stable version of Android 17 QPR2, which lists 114 applications, and the Android Canary version, which adds another 20 to those same 114. The areas covered range from food delivery to transport, from shopping to travel, and to work tools. The most important caveat is that being included in the list does not amount to automation actually being enabled for each individual app.
How it works and where it stops
The new development concerns how Gemini operates: it does not merely return answers or links, but opens the application in a virtual screen and performs actions on the user's behalf, such as searching, selecting products, and filling the cart. The final step—payment—remains in the user's hands, and the user must confirm it. The tests cited by the source show that the system can choose dishes on the Indian delivery platform Zomato and buy milk through Blinkit. The apps Swiggy and Zepto, which are not included in the list, are instead rejected.
Limits and outstanding checks
The first filter is access to a whitelist defined by Google, plus a match on the application signature. Passing this filter, however, does not guarantee that it will work: according to the test cited, productivity applications such as Word, Excel, Outlook, and Slack are on the list, but Gemini did not appear able to directly edit a document in Word or to perform automatic operations in Outlook. The test-version list also includes Reddit, X, LINE, and Shopee. At the time of publication, Google had not made the full list public or responded to the reports. It therefore remains unclear which apps are actually operational, at what pace, and according to what criteria Google updates the whitelist.
The distinction between listed apps and apps that can actually be automated is the central point: the list indicates a potential scope, not a service that is already available. Without official confirmation, the data should be read as an indication of the development path for mobile automation, not as an announcement of general availability.
Why it matters
Moving an assistant from textual response to action inside third-party applications changes the relationship between the user, software, and digital services: control shifts from manual selection to supervision of an operation performed by an agent, with payment confirmation as the final safeguard. The case also shows that the spread of this capability depends on technical agreements and on lists managed by the operating system provider, not only on the model's features. The source does not provide details on release timelines, countries affected, or selection criteria, all of which remain to be verified.
