Mobile architecture in a large team
summary
An Uber engineer explains challenges of mobile architecture in teams of 500+ developers, discussing plugin-based architecture and the controversial decision to rewrite a flagship app from scratch. The talk compares common mobile architectures for large teams, describes problems encountered at Uber two years earlier (hundreds of engineers in a single repository), and shows how those issues are addressed today using the RIBs architecture.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:12Large team challenges
- 2:38Uber architecture evolution
- 4:46Why not MVVM or Clean
- 5:51Navigation problems in classic architectures
- 6:53Router-based navigation solution
- 8:21Dependency and hierarchy issues
- 9:46DAG-based DI hierarchy solution
- 10:31Builder and Component roles
- 11:35Component interaction rules
- 12:18State updates via model streams
- 13:43New architecture benefits
- 16:35Glue code between features problem
- 18:45Example 1: multi-step operations
- 20:53Flow logic isolation solution
- 23:23Example 2: list plugins
- 24:24How plugins work
- 26:55Feature management via kill switch
- 27:57Core and common code separation
- 29:50Scaling and support
- 31:41New architecture adoption challenges
- 33:10Transition simplification tools
- 35:39Code quality control
- 37:01Architect team role
- 37:43RIBs adoption results
- 39:08Repository and documentation
- 40:09Q&A
