Android Auto: Rolling Droid gather no moss (en)
summary
Android Auto uses the phone as the app host so the phone renders the UI over USB while car head units run a thin client. Media playback uses the same media service as Android Wear, messaging is done via a ConversationBuilder extension API, and demos ran on Pioneer units and hacked Nexus 7s; prototype works but custom UIs are blocked by certification, OBD access isn’t exposed yet, and Android Lollipop is required for the video pipeline.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:07Early experiments
- 5:51Hardware and OAA
- 8:42UX benefits
- 12:13Technical architecture
- 15:28Developer APIs & certification
- 16:54Live demo
- 20:36Conclusion & future
- 23:08Q&A
related talks
38mDeveloping Apps for Android Auto.
36mLet's get this Droid on the road
14mHow to Build Android Apps for Cars
34mBuild apps for Android Auto and Android Automotive OS
51mDeep Dive into Android Auto — From How to Use It to the Technologies Behind It
13mAn introduction of Android Auto
19mAndroid Auto: Your Media in the Car
19mAndroid Auto - live coding