App Architecture Then and Now: Lessons from the DroidKaigi Conference App History
summary
A year-by-year code archaeology traces the DroidKaigi conference app from a 2015 Java + RxJava1, fragment-heavy MVC implementation to a 2021 Kotlin codebase using Coroutines/Flow, multi-module structure, and Jetpack Compose for UI. The talk details concrete migrations: Rx → Flow, Dagger2 → Hilt, SQLite → DataStore, moving view state into stateful screens with MVI/MVVM hybrids, and using Kotlin Multiplatform (KMM) to share the data layer with iOS, which successfully avoids duplicate business logic while growing the repo to ~100 OSS contributors.
AI-written summary · about
chapters (8)
- 0:00DroidKaigi history
- 2:56App architecture evolution
- 6:05Year-by-year differences
- 12:562018-2019 shifts
- 16:50MVVM with coroutines
- 18:58Future-proof design
- 23:55Six years of lessons
- 25:41Q&A
related talks
31mArchitecture metamorphosis: a real case study
58mModern Android Development
01h 01mKeynote! 10 years of Android development: the retrospective
29mShaping Your App's Architecture with Kotlin and Architecture Components
35mShaping your app’s architecture with Kotlin and Architecture Components
27mHalf Way to clean architecture
18mArchitecture is vital to build an app. But what is that concretely?
41mMaking a Kotlin, Architecture Components, Rx and Coroutines sandwich