Downloaded 15 times
![â—Ź Long dependency injection chains
â—Ź Too much (boilerplate) code
â—Ź [iOS] RIBs incompatible with plain Views
Feedback from engineers after a year’s usage](https://image.slidesharecdn.com/scaleablemobilearchitectureribsmobileapproved1-181102114956/75/Mobile-Architecture-at-Scale-73-2048.jpg)
![â—Ź Long dependency injection chains
â—Ź Too much (boilerplate) code
â—Ź [iOS] RIBs incompatible with plain Views
Feedback from engineers after a year’s usage](https://crownmelresort.com/image.slidesharecdn.com/scaleablemobilearchitectureribsmobileapproved1-181102114956/75/Mobile-Architecture-at-Scale-73-2048.jpg)
Uploaded byGergely Orosz
Mobile Architecture at Scale
The document outlines a comprehensive rewrite of Uber's mobile architecture, which was driven by the need for scalability and efficiency among a growing team of over 100 mobile engineers. It presents the implementation of the RIBs architecture, emphasizing improvements in developer productivity, performance reliability, and ease of experimentation. The goals include creating a unified codebase for both iOS and Android, ensuring high reliability, and facilitating onboarding and adherence to architectural patterns across the engineering team.
Technologyâ—¦
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
Mobile Architecture at Scale
- 1. Mobile Architecture at Scale Whyand how we built a new architecture used by hundreds of engineers, all in one codebase 18 Jan 2018 Gergely Orosz, Engineering Manager, Payments, Uber
- 2.
- 3. Payments Experience • Rider •Driver • Cash • Platforms Developer Experience • Mobile • Backend Amsterdam HQ • ~100 tech (dev, design, DS, PM, UX) • ~700 total Engineering @ Uber Amsterdam
- 4. Payments Experience • Rider •Driver • Cash • Platforms Developer Experience • Mobile • Backend Engineering @ Uber Amsterdam
- 5. Motivation Architecture Scalingan architecture in practice
- 6. Motivation Architecture Scalingan architecture in practice
- 7. â—Ź History â—Ź Architecturegrowth â—Ź Goals of the rewrite Motivation
- 8.
- 9.
- 10. Over 100 mobileengineers? Request a ride Fare split Cash Uber for Business Credit card rewards points Promotions Promotions Safety Over 10 ways to pay Scheduled rides Drive for Uber Uber Eats, Freight, Self-driving vehicles... Experimentation 80 countries, 600 cities Performance Cash Instant payments Maps & navigation uberPOOL Driver incentives App health Developer tools Networking Feed cards Driver experience Driver recognition Airport pickup Uber Family Beacon Campaigns Fraud EATS app Courier experience Shipper experience Restaurant experience
- 11.
- 12.
- 13.
- 14. Let’s just changeeverything
- 15. 1. History 2. Architecturegrowth 3. Goals of the rewrite Motivation
- 16.
- 17.
- 18.
- 19. Architecture Growth: State ...... LoggedInState LoggedIn Activity ProductSelection Controller Menu Controller Location Controller Custom View Custom View Sub Controller LoggedIn Activity
- 20. Architecture Growth: State ...... LoggedInState LoggedIn Activity ProductSelection Controller Menu Controller Location Controller Custom View Custom View Sub Controller LoggedIn Activity LoggedIn Activity
- 21. â—Ź Number ofengineers â—Ź Understanding how the app works â—Ź Shared state â—Ź Modifying the app Our Biggest Problems
- 22. Shared State class DriverIsOnTheirWayToaster{ var isOnTripAndHasNotBeenNotified:Boolean = false fun onCreate(stateStream: TripStateStream) { stateStream .state() .subscribe({ (trip, driver) -> if (trip == TripState.ON_THEIR_WAY) { isOnTripAndHasNotBeenNotified = true showToast(driver!!.name) } else if (trip == TripState.ON_TRIP) { isOnTripAndHasNotBeenNotified = false } }) } }
- 23. class DriverIsOnTheirWayToaster { varisOnTripAndHasNotBeenNotified:Boolean = false fun onCreate(stateStream: TripStateStream) { stateStream .state() .subscribe({ (trip, driver) -> if (trip == TripState.ON_THEIR_WAY) { isOnTripAndHasNotBeenNotified = true showToast(driver!!.name) } else if (trip == TripState.ON_TRIP) { isOnTripAndHasNotBeenNotified = false } }) } }
- 24. class DriverIsOnTheirWayToaster { funonCreate(driver: Driver) { showToast(driver.name) } }
- 25. Modifying the App ...... LoggedInState LoggedIn Activity ProductSelection Controller Menu Controller Location Controller Custom View Custom View Sub Controller LoggedIn Activity ... LoggedIn Activity ...... ProductSelection Controller Location Controller Menu Controller
- 26. 1. History 2. Architecturegrowth 3. Goals of the rewrite Motivation
- 27. ● Constraints ○ Nativedevelopment ○ Independent iOS & Android™ codebases ● Opportunities ○ Mobile Platform team ○ iOS & Android monorepos Constraints & Opportunities
- 28. â—Ź Isolation &testability â—Ź Developer productivity â—Ź Support continued growth for years â—Ź 99.99% reliability of core flows â—Ź Monitoring as a first class citizen â—Ź De-risk experimentation Rewrite Goals
- 29. Rewrite Goals Image byTsahi Levent-Levi Android is a trademark of Google LLC.
- 30. Rewriting the UberApp January June August November Core architecture, framework & tooling Core flow Everything else
- 31. RIBs Architecture What WeBuilt Application Framework Scoping Routing Business-logic driven Dependency management Open source Monitoring Components Code generation Reactive data flows Testability Experimentation Plugins Networking Storage Location services Analytics Logging UI components
- 32. Motivation Architecture Scalingan architecture in practice
- 33. â—Ź Application state â—ŹDependency scopes â—Ź Designing of RIBs Architecture
- 34. The state managementproblem
- 35. State Tree Root LoggedInLoggedOut Onboarding MenuRequest Home ShortcutsFeedCard Location Editor OnTrip ...
- 36.
- 37. State Tree State treedrives the views Root LoggedInLoggedOut Onboarding Menu Request Home ShortcutsFeedCard Location Editor OnTrip ...
- 38. Request Home LoggedOut State Tree State treedrives the views Root LoggedInLoggedOut Onboarding Menu Request Home ShortcutsFeedCard Location Editor OnTrip ...
- 39. â—Ź Application state â—ŹDependency scopes â—Ź Designing of RIBs Architecture
- 40. Dependency Scopes Application drivenby business logic Root LoggedInLoggedOut Onboarding Menu Request Home ShortcutsFeedCard Location Editor OnTrip ... LoggedOut
- 41. Dependency Scopes Application drivenby business logic Root LoggedInLoggedOut Onboarding Menu Request Home ShortcutsFeedCard Location Editor OnTrip ...
- 42. Dependency Scopes Application drivenby business logic Root LoggedInLoggedOut Onboarding Menu Request Home ShortcutsFeedCard Location Editor OnTrip ...
- 43. â—Ź Application state â—ŹDependency scopes â—Ź Designing RIBs Architecture
- 44. â—Ź MVC, MVP,MVI, MVVM â—Ź VIPER, (B)VIPER Popular Mobile Architectures
- 45.
- 46. VIPER Interactor Business logic Router Route betweenscreens View(Controller) Layout & animation Presenter UI logic & respond to user inputs Entity
- 47. â—Ź View treedrives the app hierarchy â—Ź Business logic & view trees are tightly coupled â—Ź Deep scope hierarchies supported only based on view nesting MVC, MVP, MVVM, MVI & VIPER
- 48. (B)VIPER Making VIPER componentsreusable Interactor Business logic Router Route between screens View(Controller) Layout & animation Presenter UI logic & respond to user inputs EntityModule Builder Creates VIPER classes
- 49. RIBs Interactor Business logic ofthe app (aka “the brain”) Router Routes between RIBs View(Controller) Layout & Animation Presenter (Optional) Translation Logic View model UI event Data model Business logic calls Routing calls Builder Creates RIB units
- 50.
- 51. Request Home LoggedOut State Tree State treedrives the views Root LoggedInLoggedOut Onboarding Menu Request Home ShortcutsFeedCard Location Editor OnTrip ...
- 52.
- 54. Data flow withRIBs
- 55.
- 56. Data flow withRIBs ServiceModel Stream Pushes state onto Service callsData model Non-state modifying responses Logic calls The Internets Interactor Router View(Controller)Presenter UI event View model Push/pull Data model Routing calls
- 57.
- 58. Viewless RIBs ServiceModel StreamPushes state onto Service callsData model Non-state modifying responses Logic calls The Internets Interactor Router View(Controller)Presenter UI event View model Push/pull Data model Routing calls Attach / detach child RIBs
- 59.
- 60. Viewless RIBs -demo
- 61. Motivation Architecture Scalingan architecture in practice
- 62. â—Ź Adopting aframework with a large team â—Ź Why RIBs worked â—Ź Summary Scaling an architecture in practice
- 63. Adopting a frameworkwith a large team
- 64. â—Ź Code generation â—ŹOnboarding â—Ź Enforcing (architecture) patterns Adopting a framework with a large team
- 65. Rails for architecture& code Code Generation Android (IntelliJ, Android Studio) iOS (XCode) Open sourced
- 66. Onboarding â—Ź How longdoes it really take to learn? â—Ź Documentation â—Ź Tutorials â—Ź Encourage contribution Open sourced
- 67. â—Ź Lint rules Enforcing(architecture) patterns â—Ź (Blocking) code reviews
- 69. Enforcing (architecture) patterns â—ŹProcess for change suggestions (RFC) â—Ź Lint rules â—Ź (Blocking) code reviews
- 70. â—Ź Code generation â—ŹOnboarding â—Ź Enforcing (architecture) patterns Adopting a framework with a large team â—Ź Have a clear owner
- 71. â—Ź Adopting aframework at scale â—Ź Why RIBs worked â—Ź Summary Scaling an architecture in practice
- 72. â—Ź 3 apps,more than 200 developers â—Ź More than 600 RIBs, reused within & across apps â—Ź Less than 300 lines of code / class for most RIBs â—Ź All business logic well unit tested â—Ź Open sourced How RIBs worked out
- 73. ● Long dependencyinjection chains ● Too much (boilerplate) code ● [iOS] RIBs incompatible with plain Views Feedback from engineers after a year’s usage
- 74. â—Ź Does yourapp have lots of non-visual state? â—Ź Do you have a (fast) growing iOS & Android app/team? â—Ź Do you have the bandwidth to invest in a new architecture? Is RIBs for you?
- 75. â—Ź Adopting aframework at scale â—Ź Why RIBs worked â—Ź Summary RIBs in practice
- 76. Motivation Architecture Scalingan architecture in practice
- 77. Gergely Orosz Engineering Manager,Uber Amsterdam @GergelyOrosz eng.uber.com Thank you uber.github.io
- 78. Proprietary and confidential© 2017 Uber Technologies, Inc. All rights reserved. No part of this document may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval systems, without permission in writing from Uber. This document is intended only for the use of the individual or entity to whom it is addressed and contains information that is privileged, confidential or otherwise exempt from disclosure under applicable law. All recipients of this document are notified that the information contained herein includes proprietary and confidential information of Uber, and recipient may not make use of, disseminate, or in any way disclose this document or any of the enclosed information to any person other than employees of addressee to the extent necessary for consultations with authorized personnel of Uber.