Android for Cars third party ecosystem
summary
Practical rundown of publishing Android Auto vs Android Automotive apps with concrete numbers and pain points: Google Play lists 220 published apps and shows 19 supported head units with install/rating/revenue metrics, while third‑party stores (apping) force OEM review gates and opaque brand lists. Covers UI constraints from the cars app library (cal), template vs compose limits, the Karma project for video/games/browsers, API fragmentation examples (Harman extensions) and step‑by‑step consequences for packaging and review timelines.
AI-written summary · about
chapters (18)
- 0:00Android for Cars ecosystem
- 1:25Car vs mobile interactions
- 2:48Android Auto vs Automotive
- 3:09Supported car app categories
- 4:11UI choices for car apps
- 5:41Templated apps in Automotive
- 6:23App availability by mode
- 7:05Karma project for mobile
- 8:11Custom UI beyond templates
- 8:34Distributing via Google Play
- 9:56Google Play car app features
- 10:38Non-GAS app distribution
- 11:41Fragmentation in Automotive
- 13:03Template host dependency issues
- 14:30App review transparency
- 15:34Third-party store inconsistencies
- 16:17GAS vs non-GAS choice
- 17:00Q&A
related talks
23mMy car - my ecosystem? A close view on emerging automotive app stores
34mBuild apps for Android Auto and Android Automotive OS
18mAndroid in Automotive, the Real Fragmentation
41mGet More Mileage From Your Adaptive App With Android for Cars
14mHow to Build Android Apps for Cars
09mWhat's new with Android for cars
35mThe Future of 3rd Party App Ecosystems in Cars
13mWhat’s new with Android for Cars