Google Shortcuts Launcher: one app drawer entry for the Google apps on your phone

It is a launcher shortcut, not a launcher replacement

Google Shortcuts Launcher is described as providing a quick way to integrate powerful Google services into your daily workflow, with just a tap you can quickly access a variety of shortcuts designed to enhance usability and simplify your interaction with core Google features.

The project description is more specific: it gives you easy access to essential Google app features directly from your launcher app drawer. So the shape of it is a single icon that opens a folder of shortcuts, and the shortcuts are entry points into things your phone can already do but which live one level too deep: the assistant, a barcode scan, an incognito Chrome tab, the file manager, a game folder, Lens, a password checkup, a shopping search.

The technology is Android, with Kotlin as the primary language, and the topic tags name the design system it follows, with material-design, material-you, material3 and material3-expressive all listed, along with launcher, assistant, gemini, google-lens, password-manager, search, weather and music.

The build is a standard Gradle Kotlin DSL project. The top level has build.gradle.kts and settings.gradle.kts, an app/ module, a gradle/ directory with the wrapper, gradlew and gradlew.bat, gradle.properties, an .idea/ directory and an images/ folder for the README assets. The GitHub Actions badge points at a workflow named android.yml, so the continuous integration story is an Android build rather than a JVM library build.

The audience is an Android user who has the Google application suite on the device and wants those services reachable without opening each app first. The licence is GPL-3.0, and the last push was on 2026-10-01 with a 6.0 release on the same day.

The shortcut list is really a list of what each feature needs underneath

The most useful thing in the README is that every shortcut declares the app it relies on, quoted underneath the description. That single convention turns the feature list into a dependency map, and it is the fastest way to understand which entries are cheap and which are not.

The entries that need only Google Play Services are the plain deep links. Barcode Scanner uses the camera to look up product details, compare prices or reach a relevant site. Google Quick Share sends and receives photos and files between nearby Android devices and compatible Windows PCs, wirelessly. Google Password Manager needs Shizuku as well as Google Play Services, because it reaches saved credentials, the Password Checkup feature and passkeys.

The entries that go through the Google App itself are Google Lens, which searches for objects, translates text and scans QR codes from the camera, Google Music Search for identifying music playing nearby, and Google Search for quick searches by keyboard or voice.

The web entries are the ones that open a browser rather than an app. Google Finances for stocks and portfolios, Google Shopping for products, price comparison and shopping lists, and Google Travels for flights, hotels and trips. Google Chrome or Brave Browser backs the Incognito Tab shortcut, and the file manager shortcut points at the AOSP file manager for organising, copying, moving and deleting files.

Then there are the Play Store entries. Google Play Collections organises your apps by theme with recommendations, and Google Play Mini Games gives instant access games built into the Google Play Games ecosystem, listing Cricked, Minesweeper, PAC-MAN, Snake and Solitaire.

The voice assistant shortcut is the most device-dependent of the set, since it invokes your device voice assistant such as Gemini or Bixby through the Android Digital Assistant Service, and the Games Launcher displays your installed games alongside Google Play Games recommendations.

The Google app suite is a hard requirement, and Shizuku is the uncomfortable one

There is a note in the README that decides whether this app is useful to you, and it is worth reading before the feature list rather than after.

The required apps are the Google app, Google Chrome, Google Play Services, Google Play and Google Play Games, and the documentation says they must be installed on your device for most shortcuts to function properly. That is a real constraint rather than a formality, because the shortcuts are entry points into those services, and an intent aimed at a package that is not installed either fails silently or drops you somewhere unhelpful.

The second requirement is Shizuku. Some shortcuts use Shizuku to open non-exported activities. That phrasing is the technical heart of the whole project and it is where the trade-off sits.

An activity is exported when other applications are allowed to start it. A shortcut that just fires an intent at an exported activity is harmless: any app on your device could do the same. A shortcut that reaches a non-exported activity cannot be started with an ordinary intent, so the app needs a privileged path, and Shizuku provides one by running commands with elevated permissions through the wireless debugging interface. In exchange, the shortcut works on features the developer was not meant to expose to third party apps.

The password manager entry is the clearest example, since it is the one that needs Shizuku as well as Play Services. Accessing your saved credentials, their security status through Password Checkup, and your passkeys is a privileged operation, and the price of that convenience is granting a component of the system elevated access over a set of actions that other applications are deliberately locked out of.

So there is a dividing line in the list, and it is worth knowing where it falls before you install anything. Most entries are deep links and cost you nothing beyond having the Google apps present. A few, and the password manager is the one to think hardest about, need Shizuku.

Distribution is GitHub releases and Telegram, with no store listing

The download section is short and worth reading in full, because it tells you what kind of project this is.

There is a link to the latest release on GitHub, labelled Get it on GitHub, and a link to a Telegram channel. There is no link to the Google Play Store, and no F-Droid or other repository listing. The project also offers a donation page through PayPal and a Buy Me a Coffee link.

That distribution choice has consequences. Installing means pulling an APK from a GitHub release and sideloading it, which means enabling installation from unknown sources, which means the update path is whatever the release page contains rather than the Play Store's staged rollout. It also means the app is not discoverable in a store search and not subject to store review.

The release history shows a steady cadence with a jump. Version 6.0 landed on 2026-10-01, 5.9 on 2026-05-01, and 5.8 on 2026-04-30, so the 5.8 and 5.9 pair came a day apart and the 6.0 release followed about five months later. The last push to the repository was on 2026-10-01 as well, so the 6.0 work is the current state of the tree.

The Android platform requirements are in a badge rather than in prose. The API level badge reads 26+, so the app targets Android 8.0 Oreo and above, and the platform badge simply says android. There is a separate build workflow for Android in the GitHub Actions configuration.

So the adoption story is: sideload a signed release from GitHub, install the Google app suite if it is not already there, grant the Shizuku permission if you want the privileged shortcuts, and use the icon from your app drawer. It is a personal utility rather than something you would standardise across a fleet.

Where Google Shortcuts Launcher is the wrong tool

The first wrong-tool case is a device without Google Play Services. That includes most non-Google Android hardware and every device in an enterprise environment that has moved away from the Google distribution stack for licensing or privacy reasons. The documentation's own required apps list settles it: most shortcuts will not work.

The second case is a user who wants to reduce their dependency on Google rather than increase it. This app is a convenience wrapper that makes Google services easier to reach, and adding it to a device that is trying to move away from those services is a step in the wrong direction. The fact that some shortcuts open a web browser rather than the Google app does not change the direction of travel.

The third case is a threat model that does not accept Shizuku. If your organisation's policy is that no component on a device should hold elevated execution rights outside the system partition, then the password manager and any other shortcut that relies on opening non-exported activities is out. The alternative is to use the Google apps directly, which is slower and clumsier but does not require the permission.

There is also a scope limitation to be honest about. This is a shortcut launcher. It does not change what any of those services can do, it does not add features, and it does not surface anything the platform does not already allow. If the problem you have is that a Google feature is hard to find, this helps. If the problem is that a Google feature does not do what you want, this does not help at all, and the answer is a different application.

One more practical constraint follows from the app being a launcher icon rather than a widget or a service. Its usefulness depends on your launcher showing app drawer folders, which is true of the stock Android launcher and of most third party launchers, but the documentation does not say how it behaves on a launcher that does not support folders or how it appears on a device using a search only home screen.

On licensing, the project is GPL-3.0, which matters for a sideloaded binary because the corresponding source has to be available to the people you give the APK to, and the repository is where you would find it. The last push was on 2026-10-01 and the current release is 6.0, so the tree and the published binary are in step.

Editorial conclusion

Google Shortcuts Launcher suits an Android user on a device with the Google app suite installed who wants the Google entry points gathered in one place instead of hunting for them, and who is comfortable granting a Shizuku permission for the handful of shortcuts that need it. It does not suit a device without Google Play Services, since the documentation says the required apps must be installed for most shortcuts to function, and it does not suit a user who treats the launcher as a privacy-sensitive surface. Before installing, check that Google Play Services, Google Play and Google Play Games are present on your device, decide whether you want to grant the Shizuku permission at all, and read the download section for the release channels, since the project distributes through GitHub releases and a Telegram channel rather than a store listing.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. README
4. Releases
5. WSTxda/Google-Shortcuts-Launcher on GitHub