from regular to Android Automotive app development
summary
Built an experimental arrow parking feature for the Stanara One that needed camera and sensor access and per-vehicle shared settings, and ends up using a headless user0 service with singleUser=true to coordinate state across multiple Android users. Finds Android Automotive delivers UX restrictions but leaves multi-user lifecycle gaps (broadcasts can arrive during user transition) and requires vendor patches such as FLAG_RECEIVER_INCLUDE_BACKGROUND and receiver foreground handling to wake apps. Uses the driving state manager and garage mode but reports fragmentation and brittle, partly-working workarounds.
AI-written summary · about
chapters (8)
- 0:00Android Automotive intro
- 2:13Stanara One sports car
- 3:38App design challenges
- 9:37Mobile the other way
- 12:06Multi-user support
- 21:59Lifecycle and power states
- 29:04Conflicts with mobile optimizations
- 33:15Key takeaways
related talks
38mDeveloping Apps for Android Auto.
48mAn Introduction to Android Automotive OS
32mAndroid Auto: Rolling Droid gather no moss (en)
37mGet in the fast lane; Android Automotive OS
29mHow Android Automotive Helps Us to Design and Build In-Car User Experiences
41mGet More Mileage From Your Adaptive App With Android for Cars
36mLet's get this Droid on the road
13mAndroid on the Road: Playing Music with UAMP in Cars