Why Android Auto Only Allows Certain Apps — and What You Can Do

Plug into Android Auto and you get navigation, media players, and messaging — rendered in Google's templates, in Google's layouts. The phone in your pocket runs thousands of apps; the screen in your dash shows a couple of rows. That gap is not an accident.

The restriction is a design decision

Google gates Android Auto behind driver-distraction guidelines: approved app categories render through standardized templates with big targets, short text, and limited interaction depth. It's a defensible default for a screen the driver glances at — and it's also why video apps, browsers, and most of your daily tools simply aren't there, parked or not.

What enthusiasts actually want

• Video and reading apps for charging stops and waiting time — parked.
• Entertainment for passengers on the big screen.
• The apps they already use — not a template version, the real thing.

Two roads around the catalog

Over the years the community has taken two broad approaches. The first patches the allow-list: tricking Android Auto into listing apps it normally wouldn't. You get extra icons, but each app still runs inside Android Auto's constraints, and results vary per app.

The second — the road KoalaMirror takes — is mirroring the desktop itself. With root and a Zygisk runtime, injection-based projection treats the head unit as another screen of your phone: your launcher, your apps, your layouts. There is no per-app compatibility lottery, because the apps are running exactly where they always run — on your phone.

The honest trade-offs

• It needs root (Magisk, KernelSU, or APatch) on Android 12L+ — that's a real prerequisite, not a footnote.
• The flip side: no custom ROM, no flashing, nothing installed on the car — a regular APK and one reboot.