Let's get this Droid on the road
summary
Explains the practical differences: Android Auto projects apps from phones and exists on 150 million Android Auto units, while Android Automotive OS runs natively and appears in roughly 10 models with Android Automotive OS today; templated apps are limited (≈35–50 live), native apps can access vehicle HAL properties, and many OEMs ship older Android versions. Notes real issues: wireless dropouts, setup friction, audio latency, Qualcomm often runs Android in a VM on QNX, and convenient options like QR-code login and tablet-in-cupholder testing work well.
AI-written summary · about
chapters (17)
- 0:00Introduction to Android in cars
- 1:11Android Auto vs Automotive OS
- 3:59Android Auto setup issues
- 6:49Android Auto market growth
- 10:01Early app opportunities
- 11:26Android Automotive OS benefits
- 13:55Android versions in cars
- 15:39Developing for Automotive OS
- 17:31Adoption by car manufacturers
- 21:07Gas vs gasless systems
- 23:58Non-Google app stores
- 26:08Templated apps for both systems
- 27:52Android Automotive OS immersive apps
- 31:01Car data and permissions
- 32:02Car vs phone UI differences
- 34:10Testing on emulators and tablets
- 35:16Wrap-up and Q&A
related talks
14mHow to Build Android Apps for Cars
37mGet in the fast lane; Android Automotive OS
18mAndroid in Automotive, the Real Fragmentation
34mBuild apps for Android Auto and Android Automotive OS
32mAndroid Auto: Rolling Droid gather no moss (en)
17mAndroid for Cars third party ecosystem
48mAn Introduction to Android Automotive OS
41mGet More Mileage From Your Adaptive App With Android for Cars