How We Build Spotify for Android Automotive
summary
Build process focuses on concrete constraints and integrations: Spotify supplies mostly data to Android Automotive media templates, owning only login and settings screens, while playback uses the shared Spotify Library and custom session commands. Two platform paths exist: Android Automotive with Google built-in (GAS) and non-GAS headless APK/SDK shipped to manufacturers with a certification loop. AI DJ ships to 50 markets in two languages; emulators and staggered Play Store canary releases (bi‑monthly main, weekly canary) struggle against long car lifecycles and old OS versions.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:10Android Automotive
- 5:01Car app challenges
- 6:47Building Spotify app
- 13:28Adding AI DJ
- 15:54Testing on emulators and cars
- 16:15Google and manufacturer testing
- 24:41Releasing to users
- 28:52Android Automotive future
related talks
34mBuild apps for Android Auto and Android Automotive OS
31mHow to build Android apps for cars
28mFaurecia & TIDAL: building Apps for Android Automotive
14mHow to Build Android Apps for Cars
18mAndroid in Automotive, the Real Fragmentation
44mBuilding and Launching Android Automotive Apps to the App Store
17mAndroid for Cars third party ecosystem
23mMy car - my ecosystem? A close view on emerging automotive app stores