My car - my ecosystem? A close view on emerging automotive app stores
summary
Explains concrete differences: Android Auto: 200 million vehicles mirrors a phone, while Android Automotive: fully embedded head‑unit apps installs apps directly on the car; use Google’s car app library for driver‑safe templates and the VHAL exposes vehicle sensors and battery state for features like parking, charging, navigation and ambient orchestration. Cariad builds an app store with Harman, lists ARD Mediathek, Webex and Spotify as examples, and accepts submissions via Harman Ignite (upload process like Play Store, contact ignitepartnerships@harman.com).
AI-written summary · about
chapters (11)
- 0:00Introduction to automotive digital revolution
- 2:35Android for cars overview
- 3:59Android Auto vs Android Automotive
- 7:11Cariad and VW Group role
- 8:14VW Group app store introduction
- 10:21Why develop for Android Automotive?
- 12:08Ecosystem analogy with Borneo
- 15:58Opportunities for app developers
- 20:58Vehicle data and technical resources
- 22:06App submission process
- 23:07Q&A and closing
related talks
17mAndroid for Cars third party ecosystem
32mIt's time to develop apps for Android cars
35mThe Future of 3rd Party App Ecosystems in Cars
39mDeveloping Android Automotive Apps for the VW Group
34mBuild apps for Android Auto and Android Automotive OS
16mGet more mileage out of your app with Android for Cars
14mHow to Build Android Apps for Cars
09mWhat's new with Android for cars