Mobile Architecture at Scale
summary
Company rewrites core mobile stack and ships a native iOS and Android architecture called RIBs architecture designed for reliability, testability, isolation, maintainability and developer velocity. Team details: mono-repo, a mobile platform team, code generation templates, lint rules and blocking code reviews; rewrite claim: rewrote the Uber app in 3 months with 200 engineers. Results: 600+ ribs, ~200 developers using it, most classes <300 LOC, strong unit test coverage. Pain points: heavy boilerplate and dependency plumbing; next work is to make it more lightweight.
AI-written summary · about
chapters (44)
- 0:00Introduction
- 2:53Motivation
- 3:06How many engineers does it take
- 3:31Uber has grown exponentially
- 3:51Why 100 mobile engineers
- 4:16The drivers side
- 6:23The Uber app
- 7:57Lets just change everything
- 8:46Engineering Challenges
- 10:56Biggest Problems
- 12:22State
- 13:48Modifying
- 14:42Starting from scratch
- 14:56Staying native
- 16:09Independent code bases
- 17:56Rewrite goals
- 20:21How did we do this
- 22:04What did we learn
- 22:16What did we build
- 23:03Hands on
- 23:44State in State
- 24:10Tree
- 25:35UI
- 26:19Menu
- 28:57Mobile MVC
- 29:33MVP Model View Presenter
- 30:25MVP Model View Intent
- 31:09MVP View Intent
- 32:16Interactor
- 32:48Routing
- 33:25View Tree
- 34:13Viper
- 34:44Ribs
- 34:59Presenter
- 45:05Onboarding
- 46:34Open Source Architecture
- 46:51lint rules
- 49:09RFC
- 50:12Ownership
- 51:00Apps
- 51:23Reb
- 51:58Feedback
- 53:46Is it worth it
- 54:50Wrapping up
related talks
44mRIBs - Uber's new mobile architecture that scales to hundreds of engineers
36mHot Off the Open-Source Grill: RIBs, Scalable Multiplatform App Architecture
31mA platform approach to scaling mobile app development
33mMobile app architecture
45mScaling Architecture at Lyft
40mIts fairy tale time: hybrid app development
25mFrom 0 to 15 million users
34mMobile at Scale with React Native & Multi-Module Architecture