Architectural journey
summary
Badoo runs Android for many apps with over 420 million registrations and faces stateful, async bugs; the claim is that switching from MVP/Clean to an MVI style and open‑sourcing an mvi-core library (features, actors, news channel) plus a lifecycle‑aware binder and middleware/time‑travel debugger actually reduces mysterious state bugs, scales across apps, and simplifies wiring; code and libraries exist on GitHub and the approach proves practical enough to merge with a RIBs‑style node hierarchy.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:04State
- 6:48Side effects
- 10:26Events
- 13:24Dataflow
- 17:29Scoping
- 22:51Middleware
- 24:47Summary
- 25:34The bigger picture
- 26:50Problems
related talks
27mHalf Way to clean architecture
33mMobile app architecture
31mArchitecture metamorphosis: a real case study
38mHands On MvRx: Building Real Apps
36mSimple MVI Architecture for Android
17mApp architecture - singular vs plural
46mMvRx: Android Development on Autopilot
37mAdaptable architecture for agencies