I’ve observed that any application architecture that is based around the GUI for dependencies of anything beyond the scope of a single screen just isn’t readily extended/modified/reused. From watching the video, I see an architecture that puts views and data in their appropriate places in relation to views: views are just a window into the soul of an application’s business logic, and data is modified according to business rules, and logically, it doesn’t matter how the views are represented: they’re merely window dressing for end users to present a user-friendly face to do the most important function of an application, which is to transform inputs into outputs for use by users. Logically, Uber’s applications when architected this way should only ever go awry if the business logic creates unrecoverable states that are undefined: the routing logic is simple, the presentation code (views) should be easy to test. Almost makes me curious enough to download the Uber app ;)
I mean from everything im hearing it sounds exactly like React. I really dont see the difference. React + dependency injection + context for sibling communication
![[Uber Mobility] RIB (Router Interactor Builder) - Yi Wang](/img/n.gif)
Nice to see the Dependancy Inversion Principle and Clean Architecture being applied again to solving the age old software problems of massive teams.
This man is a great story teller, nice presentation.
I’ve observed that any application architecture that is based around the GUI for dependencies of anything beyond the scope of a single screen just isn’t readily extended/modified/reused. From watching the video, I see an architecture that puts views and data in their appropriate places in relation to views: views are just a window into the soul of an application’s business logic, and data is modified according to business rules, and logically, it doesn’t matter how the views are represented: they’re merely window dressing for end users to present a user-friendly face to do the most important function of an application, which is to transform inputs into outputs for use by users.
Logically, Uber’s applications when architected this way should only ever go awry if the business logic creates unrecoverable states that are undefined: the routing logic is simple, the presentation code (views) should be easy to test.
Almost makes me curious enough to download the Uber app ;)
"three people... working super hard on an off-site" (1:55) something about engineers working during an off-site rubs me the wrong way a bit
It was still a startup back then, my dude.
Isn't that similar to React?
No, it is the opposite of react
I suppose it is similar to VIPER, but not view-centered, it is bussiness-logic centered.
I mean from everything im hearing it sounds exactly like React. I really dont see the difference. React + dependency injection + context for sibling communication
React is a rendering framework mostly used for building HTML and mobile UI (ReactNative). It’s not related to app architectures.
I just hate how we've come to this idea that views can't even read or write their own text fields.
Looks like react in some ways