It's time to develop apps for Android cars
summary
Android Automotive is rolling into Volvo, Ford, GM, BMW, Honda and more and the claim is 70% by 2028; app stores (Appling by Forvia and others) already host roughly 400 apps so distribution is shifting from OEM-by-OEM to centralized stores. Fragmentation comes from AOSP vs GAS branches, differing app host implementations and car‑specific API levels; COVESA pushes an updated AOSP app host and a dynamic vehicle property access module. A working demo shows push notifications using Unified Push v3 with the Sunup distributor app and auto‑push‑rs server running in the emulator.
AI-written summary · about
chapters (18)
- 0:00Android Automotive development
- 1:25Android Automotive overview
- 3:54AOSP vs Google Automotive Services
- 5:20Why now for car apps
- 6:05Key concepts for car apps
- 9:24Car app vehicle integration
- 11:56Car app API levels and templates
- 13:41Car app host role in OEMs
- 15:49Hands-on development workshop
- 16:11Automotive app fragmentation
- 17:32Kavisa’s fragmentation solutions
- 18:36Updating AOSP app host
- 19:19Vehicle property access issues
- 20:44Kavisa expert group
- 21:09Push notifications demo
- 23:22Unified push in automotive
- 26:40Push notification setup
- 31:27Summary and getting involved
related talks
18mAndroid in Automotive, the Real Fragmentation
35mThe Future of 3rd Party App Ecosystems in Cars
23mMy car - my ecosystem? A close view on emerging automotive app stores
09mWhat's new with Android for cars
31mHow to build Android apps for cars
14mHow to Build Android Apps for Cars
13mWhat’s new with Android for Cars
34mBuild apps for Android Auto and Android Automotive OS