Creating the Lyft Driver App: Reduce, Reuse, Recycle
summary
Lyft splits a single dual‑mode APK into two app modules by ripping mixed features into fine‑grained modules, moving shared logic into true core libraries, and reallocating deep links and long‑running jobs; the engineering payoff is smaller installs, faster startup, and independent ship cycles. Work uses Dagger, GitHub owners check gating reviews, and gradual rollout (duplicate app with driver mode off, test alpha/beta/prod). Outcome: over 80 modules (approaching 100), passenger‑only build ships a few weeks after the split and modularization continues.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 1:53Driver experience overview
- 5:23Why split the driver app
- 7:07Engineering motivations for split
- 10:13Modularization and ownership
- 12:22App split strategy and challenges
- 16:33Reduce, reuse, recycle approach
- 23:54Results and future work
related talks
31mCreating the Lyft Driver App: Reduce, Reuse, Recycle
45mScaling Architecture at Lyft
01h 00mAndroid builds
33mFrom Four Wheels to Two
30mFrom Four Wheels to Two
15mArchitecting Amp: Android integration with embedded systems
14mChanging Lanes with Lyft
46mBuilding a SuperApp: Lessons from merging multiple apps into one