Hi ,i'm new to aaos ,i've made tons of react native and flutter apps but none for aaos,i've been searching ways to get started and tutorials/documentation are scarce and to make matters worse i can't run emulators as my pc has issues with virtualization (i use my android to test ui and it's even better as i get an in depth feel of end user experience)
Built a lightweight AAOS radio app because most automotive radio apps felt bloated, outdated, or simply not designed for actual driving.
So I made bradio.app — a native Android Automotive OS radio app focused on:
Current version:
A few things I intentionally didn’t add:
The whole APK stays under 10 MB because AAOS hardware fragmentation is still very real.
Some AAOS-specific choices:
The app is currently distributed through:
Distribution itself is global, but actual availability can vary depending on OEM integrations, regional storefronts, certification status, and vehicle platform decisions.
It also recently passed Harman Ignite Automotive APK validation with zero NOK findings.
What I’ve learned building for AAOS:
I’m currently restructuring the internal architecture before eventually doing a full Media3 session migration, but trying very hard not to turn the app into another overengineered media platform.
Curious what other AAOS developers here think:
What are the biggest mistakes you see in current automotive media apps?
Also happy to answer technical questions about MediaBrowser compatibility, validator requirements, distraction optimization, OEM distribution, or AAOS UX constraints.
I’ve also been publishing some AAOS and other platform architecture notes, validator reports, and development writeups on bradio.dev for anyone interested in the engineering side of automotive Android apps.
