Android in Automotive, the Real Fragmentation
summary
Claim: almost all cars run Android within five years, but OEM theming and API changes mean an app that works in one brand often fails in another. Polestar and Volvo include Google Play Services so deployment is straightforward, while many non‑GAS cars lack working emulators and templates (Snap supplies better emulators and an HDK). Two rival alternative app stores exist but attracting developers is the hard part. Google prioritizes projected Android Auto while Android Automotive OS misses roughly half expected features; COVESA initiative aims to standardize APIs.
AI-written summary · about
chapters (14)
- 0:00Android in Automotive intro
- 1:07Mobile Android fragmentation
- 2:35Shift to automotive infotainment
- 4:25Automotive fragmentation challenges
- 6:15Car app store difficulties
- 7:39Market size comparison
- 8:21Google’s role in Automotive OS
- 9:43Carmakers want app ecosystems
- 10:47COVESA standardized APIs
- 12:11Do cars need apps?
- 13:35Rules for car apps
- 15:40Automotive app risks
- 16:02Google’s automotive dominance
- 17:06Call to action
related talks
32mIt's time to develop apps for Android cars
17mAndroid for Cars third party ecosystem
31mHow to build Android apps for cars
09mWhat's new with Android for cars
13mWhat’s new with Android for Cars
48mAn Introduction to Android Automotive OS
36mLet's get this Droid on the road
16mGet more mileage out of your app with Android for Cars