AA Browser is a WebView browser built for Android Auto head units

A browser shaped for a dashboard, not a phone

AA Browser describes itself as a WebView browser experience for Android Auto head units, aimed at turning parked time into something useful, and the feature list is built around the size and the constraints of a car screen. The interface is Material 3 Expressive, built for car screens with fluid animations, modern bottom sheets and a true black AMOLED theme. There is one touch switching between mobile and desktop mode, global UI scaling, and bookmark management designed for head units rather than for a mouse. Tab handling is described as desktop class, so you can open, switch, close and restore several browser tabs from the dashboard. The start page holds up to six quick link tiles with drag and drop reordering, cached site icons and a custom background image. The video side is aimed at parked viewing, with DRM protected Widevine L3 streaming and a one tap fullscreen toggle. None of this is generic browser functionality, and that is the point of the project.

Installing means turning on unknown sources for Android Auto

There is no special installer and no app store listing, so the setup work is on the Android Auto side, and the README is explicit that you have to turn on the hidden developer settings. The sequence is short. Open the Android Auto settings by searching for Android Auto in the phone's settings, then scroll to the bottom and tap the Version section ten times, tapping OK on the pop-up. From there, open the three-dot menu in the top-right corner, choose Developer settings, and turn on the Unknown sources checkbox.

The app itself is then a plain download and install, and the README recommends Obtainium for keeping it up to date without limitations, with a GitHub Releases APK as the alternative. The Obtainium link in the README is a configuration URL for the app, with the package id com.kododake.aabrowser and the GitHub repository as the source, and its settings include turning off prereleases, falling back to older releases, and filtering release titles and notes by regular expression. That is a more useful configuration detail than it looks, because it means the update behaviour is something the user controls rather than something the app decides.

The safety framing is unusually direct

The README opens its usage section with a developer's safety request, and it is worth quoting the spirit of it because it sets the terms of use. If you are the one steering, do not look at this app, and if you think your eyes might wander while driving, uninstall it right now. The app is for passengers or for when you are safely parked. The legal note that follows is blunt as well: the author built the code, but the GPLv3 licence means they are not responsible for your actions, and the advice is to drive smart. The current issues list repeats the same point under the heading of stationary use only, and pairs it with the other known gap, that ad filtering is not currently implemented. Those two together define the realistic use case, a browser for the parked car, and any evaluation that ignores them is evaluating the wrong thing.

Fake download sites are the operational risk

There is a caution block in the README about fake websites. Sites impersonating AA Browser have appeared, the GitHub repository is stated to be the only official source, and the advice is not to trust or download from any other website, with the stated reason being to prevent malware infections and financial damage. That is a different kind of warning from the usual documentation note, and it is a consequence of the distribution model. An app that is not in a store, is downloaded as an APK from a GitHub release, and is recommended through a third party updater such as Obtainium is easy to impersonate, and the people most likely to look for it are the people least likely to check a repository URL. The practical rule is simple and worth repeating: the release page on the project's own GitHub repository, and the Obtainium configuration that points at it, are the only two things you should be using.

The launch quirk has a documented workaround

There is one troubleshooting entry in the README, and it is specific enough to save a support round trip. If the app fails to launch, try opening a non-Google Maps navigation app such as Waze first, and then open AA Browser. That is a workaround for how Android Auto hands control to an application rather than a bug in the browser, and it is the kind of detail that the documentation exists to carry. The rest of the troubleshooting section is the usual contributor workflow: check for an existing issue and open a new one with reproduction steps if there is none, start a discussion for an idea, fork the repository and submit a pull request if you want to contribute code, and share a photo of the app on your dashboard in the discussions tab.

The alternative is a host app that launches what you already have

The author points readers to a second application of his own, AA Anything, in the same note where the missing ad blocking is mentioned, and the description tells you what the difference in approach is. AA Anything lets you use your own favourite browser with built in ad blocking, or other apps such as VLC, on Android Auto. So the two are not competing browsers. AA Browser is a self contained WebView browser with its own interface, its own start page, its own tab management and its own video handling, which is why it can be tuned for a car screen and why it lacks the ad blocking that comes from a real browser. AA Anything is a host that delegates to whatever you have installed, which is why it can offer ad blocking and third party media players, and why it gives you none of the car specific interface work. If the missing ad blocking is what stops you, or if you want VLC on the head unit, the host approach is the one to look at. If you want the dashboard experience, this is it.

A fast moving line with a recent push

The release history is short and moving. v2.2 came on 2026-06-13, v3.0 on 2026-09-24 and v3.3 on 2026-10-13, and the repository was pushed to on 2026-10-17, days before the current date, so the work is current. The version scheme jumps, with a move from 2.x to 3.0 and then to 3.3 in a matter of weeks, which is consistent with a project that is still finding its shape and is comfortable breaking the numbering. The licence is GPL-3.0, with the LICENSE file at the repository root, and the README notes that the licence is also the reason the author is not responsible for what drivers do with it. The repository layout is a conventional Gradle Android project, with app/, build.gradle.kts, settings.gradle.kts, gradle.properties, the gradlew wrapper scripts, a docs directory holding the demo images and screenshots, a scripts directory and a CHANGELOG.md.

Editorial conclusion

Adopt AA Browser if your car runs Android Auto on a head unit with a large touch screen, you want a browser that is designed for that screen rather than a phone app scaled up, and you are willing to sideload an APK and enable unknown sources for the Android Auto developer menu. Do not adopt it if you need ad blocking, which the README lists as not implemented, or if you want a general purpose browser with an extension ecosystem, since this one is a WebView shell. Before you install, read the safety section, confirm the head unit runs Android 15 or later, and download only from the repository, since the README warns that fake download sites impersonating it exist.

Frequently asked questions

Official sources

1. Issues
2. kododake/AABrowser on GitHub
3. License: GPL-3.0
4. README
5. Releases