How we brought the Uber Driver App to Android Auto
summary
Ports the Uber Driver app to Android Auto by extending the existing RIBs framework into car screen RIBs, keeping the same interactors and a single data source so phone and head unit share consistent state for go-online, heat map guidance, accept/decline offers, in-app navigation, start/complete trip. Implements a conditional worker API to avoid duplicate processing, ships behind 100% feature flag, and measures 24.2% adoption among compatible users with 71% retention and largely issue-free long sessions.
AI-written summary · about
chapters (12)
- 0:00Android Auto project intro
- 1:31Why Uber Driver on Android Auto
- 2:38Architecture changes for Android Auto
- 5:27Android Auto library limits
- 7:37Design paradigms for Android Auto
- 10:07Consistent state and redundancy
- 11:54Simple and maintainable code
- 13:17Screen stack and worker optimizations
- 15:03Android Auto integration factors
- 16:48Early exploration and POC
- 17:51Results and adoption metrics
- 18:33Q&A
related talks
33mAndroid Auto app development today — a case study from building navigation apps
32mAndroid Auto: Rolling Droid gather no moss (en)
14mHow to Build Android Apps for Cars
38mDeveloping Apps for Android Auto.
41mGet More Mileage From Your Adaptive App With Android for Cars
13mAn introduction of Android Auto
27mBuild your own ridesharing app with
36mfrom regular to Android Automotive app development