Developing Android Automotive Apps for the VW Group
summary
VW Group ships a white‑label Harmon Ignite Store app marketplace integrated into car head units, with payment via Samsung Checkout and a digital wallet, plus OTA feature‑on‑demand support. Android Automotive apps use the AndroidX car templates and negotiate API level 7 with the host; the platform exposes ~240 vehicle properties (about 50 available to third parties). WebView is mandatory, media apps run via MediaBrowserService, and Ignite provides emulators and CI images for validation.
AI-written summary · about
chapters (18)
- 0:00Android Automotive intro
- 1:10Android Automotive history
- 5:25Kariad’s role in VW infotainment
- 6:29Android Automotive OS overview
- 9:37Third-party app categories
- 11:27Audio media apps dev
- 12:57Car templated apps & AndroidX
- 15:57Ignite tools & emulators
- 17:00Ignite Store features
- 18:07Publishing to VW store
- 19:33OEM vs third-party apps
- 22:02Premium partner apps
- 23:49Monetization in Ignite Store
- 24:53App store content categories
- 27:01Automotive dev challenges
- 33:08Future trends & AI
- 35:15AI in-car experience
- 38:24Closing & Q&A
related talks
23mMy car - my ecosystem? A close view on emerging automotive app stores
32mIt's time to develop apps for Android cars
12mBuilding and Shipping Android Automotive Apps
17mAndroid for Cars third party ecosystem
31mHow to build Android apps for cars
48mAn Introduction to Android Automotive OS
29mHow Android Automotive Helps Us to Design and Build In-Car User Experiences
14mHow to Build Android Apps for Cars