Faurecia & TIDAL: building Apps for Android Automotive
summary
TIDAL ports its mobile player into cars by first shipping an Android Auto extension and then a standalone Android Automotive APK that adds a vehicle-optimized sign‑in activity and settings screen and uses a MediaBrowserService + MediaSession to serve content and custom playback actions (example: a track radio custom action). Templates let apps run while driving and reach both Auto and Automotive; non‑templated apps cannot. Testing relies on emulators such as the Pulsar emulator and OEM images (Volvo, Honda) plus the Media Controller Test app. Android Auto already reaches about 200 million cars and systems enforce driving restrictions from a 5 m/s threshold.
AI-written summary · about
chapters (18)
- 0:00Introduction and context
- 1:29Android Auto vs Automotive
- 2:51Google Automotive Services
- 4:15App categories for Automotive
- 6:00Templated apps and branding
- 9:15Distraction optimization
- 14:38Testing tools for Automotive
- 16:23Tidal’s journey to Automotive
- 17:05Media apps architecture
- 19:52Designing user experience
- 21:37Custom playback actions
- 23:23Standalone Automotive app
- 24:47Authentication flow
- 25:31Settings and preferences
- 25:52Emulators and testing
- 26:55Releasing to Play Store
- 27:16Distribution beyond Google
- 27:59Q&A and closing
related talks
34mBuild apps for Android Auto and Android Automotive OS
41mGet More Mileage From Your Adaptive App With Android for Cars
23mGoing on a road trip with Android Auto
14mHow to Build Android Apps for Cars
38mDeveloping Apps for Android Auto.
31mHow to build Android apps for cars
19mAndroid Auto: Your Media in the Car
13mAndroid on the Road: Playing Music with UAMP in Cars