The Future of 3rd Party App Ecosystems in Cars
summary
OEMs are rolling out Android Automotive stores (BMW already ships a store client) while vendors offer white‑label stores and QA bridges; current tooling is primitive, emulators miss hardware, and manual OEM validation blocks scale — hundreds of apps are manageable, thousands are not. Covesa publishes an SDK and a push‑notifications spec (Zoom is committed) as the first standardized APIs. Expect vehicle properties, camera and cabin sensors, in‑car payments and charging APIs, plus conversational assistants; templated UIs limit design but enable safer driving UX and build once deploy everywhere.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:18Why third-party apps essential
- 7:36Developer challenges
- 12:31OEMs versus app developers
- 16:23Brand versus ecosystem
- 23:25Release cycles versus innovation
- 25:56Future APIs opportunities
- 31:19Covesa standardization role
- 33:47Q&A
related talks
32mIt's time to develop apps for Android cars
23mMy car - my ecosystem? A close view on emerging automotive app stores
17mAndroid for Cars third party ecosystem
14mHow to Build Android Apps for Cars
31mHow to build Android apps for cars
12mBuilding and Shipping Android Automotive Apps
48mAn Introduction to Android Automotive OS
09mWhat's new with Android for cars