My ever-useful Android Auto setup never really goes beyond Maps, Spotify, and whatever text app I’m using that week, and for a long time I assumed that was all the platform was. Then my car started making a noise I didn’t like, and I wanted a torque and boost gauge on the dash to keep an eye on it. I also wanted my dashcam’s trigger button somewhere I could actually tap while driving instead of digging for it on the phone itself. Neither one showed up when I searched Android Auto’s section of the Play Store, and that’s not an oversight — Google only certifies apps in a handful of categories, mostly navigation, music, and messaging, and anything outside that gets left off the dashboard entirely.

So I looked for a workaround and found one that didn’t involve rooting my phone or tethering it to a laptop for an hour of ADB commands. It’s called AAAD, short for Android Auto Apps Downloader, and it’s been quietly doing this since 2021.

Why does Android Auto have so few third-party apps

Google’s 2018 crackdown still shapes what you can install

Google locked this down back in 2018. Before that, developers could build apps that declared themselves Android Auto-compatible, and users could sideload them freely. Google didn’t like that, mostly on safety grounds, and started requiring apps to go through a certification process before they’re allowed to register as Auto-compatible. The approved categories are narrow on purpose: navigation, media playback, messaging, and a handful of voice-first tools. A dashcam controller doesn’t fit. A performance monitor doesn’t fit. A screen-mirroring tool definitely doesn’t fit, since Google would rather you not run whatever app you want on a screen you’re supposed to glance at while driving.

The apps still get built, just outside the Play Store’s rules. Developers distribute them as standalone APKs, and normally installing one and getting it to actually show up inside Android Auto required a rooted phone and some manual patching. That’s the gap AAAD fills. It reads as an app store because that’s functionally what it is, just for a category of software Google has fenced off.

OS

Android

Developer

shmykelasa

AAAD (Android Auto Apps Downloader) is a sideloaded Android app, active since 2021, that works as a curated store for third-party Android Auto software Google’s Play Store won’t list — dashcam controllers, screen-mirroring tools, a torque/performance monitor, and similar niche apps that fall outside Google’s approved navigation, music, and messaging categories. It installs without root, a PC, or developer options: you grab the APK from its GitHub releases page (the only official source), pick an app, and install it through Android’s normal installer, after which it shows up in Android Auto directly.

How to install AAAD on your Android phone

No root, no PC, no developer options required

This is the part that surprised me most, because I went in expecting to need at least one of the usual workarounds. AAAD needs none of them.

The app itself only lives on GitHub. That matters more than it sounds like it should — search around, and you’ll find copies on aaadapk.com, Uptodown, and Softonic, none of which are affiliated with the actual developer, and I wouldn’t trust an APK for something that reaches into your car’s software from a site that isn’t the source. Grab it from the AAAD releases page instead.

From there, the setup is almost boring. You install the APK the same way you’d sideload anything else on Android, which means allowing installs from unknown sources for whatever browser or file manager you used to download it. Open AAAD, and you land on a scrollable list of apps built specifically for Android Auto — dashcam tools, mirroring apps, gauge readouts, that kind of thing. Tap one, let it download, then install it the normal way through Android’s own installer prompt. Plug into Android Auto, and the app is just there, sitting in your app grid like it was always supposed to be.

No developer options, no ADB, no computer involved at any point. The whole process happens on the phone, start to finish, and took me under 10 minutes, including the download.

One wrinkle: Google Play Protect will almost certainly flag the installer with a warning. That’s expected, and it’s the reason the install button you’d normally tap gets buried — you’ll need to dig for an “install anyway” option instead of the default blue button, which is deliberately unhelpful about walking you through it.

What apps you actually unlock with AAAD

Dashcams, gauges, and mirroring tools Google won’t approve

The free tier caps you at one download every 30 days, which is enough to test the waters but not much else. A one-time purchase — a few euros, no subscription — unlocks unlimited downloads permanently, and the license survives an uninstall of AAAD itself, so you’re not locked into keeping the app around.

The library leans heavily toward the stuff Google’s category rules exclude by design. It includes a dashcam trigger, a couple of screen-mirroring apps for running phone-side software on the car display, a performance and torque monitor for reading live engine data, a browser built for the constrained but much more useful Android Auto interface, and a contacts-navigation bridge, among others. None of it comes from the Play Store, and none of it ever will — anything already sold through Google’s storefront gets Android Auto access automatically and has no reason to show up here.

I ended up installing the performance monitor and a dashcam control app, and both showed up in my car’s Auto interface exactly like a sanctioned app would, just without the sanctioning.

What to watch out for before you install anything

None of this is officially supported, and the developer says as much — if Google tweaks how Android Auto validates apps, any of these tools can stop working with no warning and no fix timeline. A few device brands have known issues going in: Oppo, Realme, and OnePlus phones reportedly fail to show installed apps or throw a persistent “no messages during drive” error without a manual fix applied first, and Pixel owners on Android 13 hit a similar bug unless they patch it beforehand. Android 14 and later (including the current Android 17 with its many new features) support is shakier still, with older AAAD versions not working at all and newer ones only partially tested.

There’s also the license quirk that a factory reset wipes your paid unlock, recoverable only by emailing support with proof of purchase. And if you’re already on a rooted phone, AAAD isn’t even the right tool — there’s a sibling project built specifically for root users that handles things differently and adds more tweaking options on top.

None of it is deal-breaker territory for me. I’d rather deal with an occasional bug on a torque gauge than not have one at all, and the install process is low-stakes enough that testing it costs ten minutes and nothing else. If Google keeps treating “apps built for cars” as a smaller category than it actually is, tools like this will keep existing to fill the gap.