My Android home screen had a problem that no launcher could solve. I could rearrange icons into folders, swap gestures, add widgets, and theme the whole grid, but the moment I tapped any app icon, the launcher was done. What waited inside the app was its own design decision, and the only way through it was a chain of taps. For most apps the chain is short. For a handful I open every day, the chain had grown long enough to annoy me. AsWidget turned the deepest three of those chains into a single tap on the home screen, and it does it without rooting the phone (rooting is the Android equivalent of jailbreaking, gaining full system access at the cost of your warranty and most app compatibility).
What AsWidget is and why it exists
AsWidget is a Play Store app, free, with no in-app purchases and no ads in the version I installed. Its job is narrow: build a home screen widget or shortcut that opens another app at a specific screen. Not the home screen of that app. A specific inner screen. Think of it as the difference between “open Maps” and “open Maps, drop a pin, switch to satellite view.” One is a launch, the other is a state.
The reason this tool exists at all is that Android apps can publish deep links. A deep link is a URL or intent (an intent is a message Android uses to ask an app to do something, like “open this specific screen”) that says “I handle requests for this destination.” Apps like Instagram, YouTube, Gmail, banking apps, payment apps, and many smaller utilities publish their own deep link surface. The published list is what AsWidget reads.
When you open AsWidget, you see every installed app that has published deep links. You pick one. You pick a destination inside it. AsWidget generates a shortcut or widget that, when tapped, fires the right intent. You drop the widget on your home screen, and one tap later you are at the screen you wanted. The whole process from install to first widget on the screen takes less than a minute.
- Free on the Play Store, no sideloading required
- Reads each app’s published deep link surface
- Generates shortcuts, home screen widgets, and quick settings tiles
- Works on Android 8 and newer without root
Why launchers hit a wall
A launcher controls the home screen and the app drawer. It can arrange icons, add widgets, set wallpapers, change gestures, and manage folders. It cannot reach inside an installed app. The launcher is the front door, but once you cross the threshold, you are inside the app’s own logic, and the launcher has no vote.
For most apps, this is fine. A tap on Gmail takes you to the inbox. A tap on the phone app opens the dialer. The chain is one tap and you are where you want to be. But a handful of apps bury their most useful screens. The destination that takes four or five taps to reach is exactly the destination you open often enough to feel the cost. AsWidget’s value is collapsing that chain.
The honest framing is this: AsWidget is not a launcher replacement. It is a complement. It does not draw the home screen, does not theme icons, and does not manage your app list. It does one thing: shortens the chain to specific screens in apps that already expose deep links.
Three shortcuts I built in week one
Week one I built widgets for the three screens I open most. The first one is for a regional payment app I use at the grocery store. Before AsWidget, the chain was launch the app, dismiss the welcome screen, switch to the wallet tab, tap the QR code button, and wait for it to render. That is five taps and a few seconds of waiting. With the widget, it is one tap and the QR appears in under a second. The saving on this one is time, not just clicks, because the QR generation happens server-side and the wait is real.
The second widget is for Instagram DMs. The default path from the home screen is open Instagram, dismiss the home tab, tap the messages icon, find the conversation. Four taps and a couple of seconds. With the widget, one tap and I am in the conversation list. The savings are smaller here, but I open this widget more times per day than any other, so the total adds up.
The third is for a YouTube destination I use to check new uploads from channels I subscribe to. The default chain is open YouTube, ignore the home and explore tabs, navigate to library, tap subscriptions, find the right shelf. With the widget, one tap and the subscriptions feed loads. The widget does not save me a lot of taps. It saves me the daily small annoyance of seeing the algorithm’s shelves on the way to what I actually wanted.
- One widget for payment QR codes
- One widget for direct message inbox
- One widget for a specific feed inside YouTube
- All three are full home screen widgets, not just icon shortcuts
How the setup actually works
Setup is short. Install from the Play Store. Open the app. Grant the accessibility permission it asks for. Accessibility is how AsWidget reliably reads what deep links each app publishes. There is a privacy cost here, and it is worth flagging: an accessibility service can see what is on your screen, in principle. AsWidget does not advertise that it uses the permission for anything beyond reading intent filters, but the permission is the same permission a screen reader would use, and you should know that you granted it.
After granting accessibility, AsWidget scans your installed app list and surfaces every app that publishes at least one deep link. You pick the app, pick the destination, and AsWidget shows you a preview of the widget with the label and icon it will use. You confirm, and the widget is ready. You drop it on your home screen like any other widget.
If you want a quick settings tile instead of a full home screen widget, AsWidget supports that too. The same flow: pick app, pick destination, choose tile instead of widget. The tile lives in the notification shade’s quick settings, where the Wi-Fi toggle and the flashlight button live. Quick settings tiles are good for things you open from anywhere, like the smart home app.
Trade-offs
The honest list of things AsWidget does not solve:
- Not every app publishes deep links. If the developer never declared a destination, AsWidget cannot reach it. Most big apps do, but smaller apps vary, and you will discover this as you try to build widgets.
- Widgets do not update their labels. If the destination app changes how it names a screen, the widget still uses the label you set when you built it. This is rare in practice but it does happen, and the widget does not warn you.
- Accessibility permission cost. AsWidget uses accessibility to read intent filters reliably. If you are privacy sensitive about the accessibility service running, that is a real cost. The alternative is the older
pm dumpAPI, which is slower and returns less. - Dead widgets after uninstall. If you uninstall an app that AsWidget built a widget for, the widget stays on your home screen as a dead icon. You have to remove it manually. AsWidget does not auto-clean.
What I would tell past me
If I were talking to the version of me that spent twenty minutes a day tapping through deep menus, I would say: install AsWidget, build widgets for the three screens you open most, and give it a week. The first week will feel like a small novelty. By week two, the muscle memory will be in place, and by week three you will not remember how you lived without the shortcuts. The launcher customization rabbit hole is fun, but the daily win is in collapsing the tap chains to the screens you actually use.