Architecture metamorphosis: a real case study
summary
Claims a full migration of the largest financial mobile application in Italy from MVP to MVVM, replacing EventBus with RxJava then moving to Kotlin coroutines and Android Architecture Components (ViewModel, LiveData). Describes introducing use‑cases to extract business logic, splitting app into functional modules plus core and upper modules, and removing Gradle bottlenecks. Reports concrete wins: reduced boilerplate, improved testability, and build time dropped from 20 to 3 minutes; migration succeeds but requires careful, nontrivial effort.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:22Summary
- 0:43Who are you
- 2:08Real case scenario
- 2:48Things change
- 6:48ModelView Presenter
- 7:43ModelView Communication
- 9:02Heaven Bus
- 9:29Heaven Bus example
- 10:37Heaven Bus advantages and disadvantages
- 12:03Reactive programming
- 12:35Observer and observable
- 16:40Android Architecture Summary
- 20:21What are curtains
- 20:53Using curtains
- 21:53Modularization
- 23:26Automated stays
- 24:54Cons
- 27:40Speed
- 28:19Build time
- 28:29Conclusions
- 30:31Conclusion
related talks
27mHalf Way to clean architecture
28mHands-on Android Architecture & Architecture Components
26mApp Architecture Then and Now: Lessons from the DroidKaigi Conference App History
42mArchitecture Round Table
19mJava to Kotlin Migration Mistakes
41mMaking a Kotlin, Architecture Components, Rx and Coroutines sandwich
40mI Wrote an App Using Architecture Components… And Here’s How It Turned Out
41mMVI: a Robust and Modern Architecture