Migrating an app with millions of users progressively
summary
A practical guide to progressively migrating a large Android app used by millions without disrupting users or performance. Covers moving from Rx to Jetpack Compose with clear layer separation, switching dependency injection from Dagger to Hilt, and transitioning UI from XML to Compose while implementing a Design System. Describes tools and best practices (Konsist, feature flags/FF, etc.) and concrete experience-based steps to perform the migration safely and avoid common pitfalls.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:07Full migration necessity
- 3:15Reborn project strategy
- 5:00Dagger and Hilt cohabitation
- 6:25Rebranding with Jetpack Compose
- 9:36XML/Compose progressive migration
- 11:01Switching to Coroutines with Compose
- 12:26RX Java and Coroutines cohabitation
- 14:32Team process for long migrations
- 18:25Code review with GitHub Actions
- 20:56CI tests for migrations
- 21:59Risk management and communication
- 23:45Tips for sustainable migrations
- 25:10Thanks and conclusion
related talks
38mFrom Android View to Jetpack Compose — A Guide to Migrating to Jetpack Compose
47mUp to Date? Talking About Your App
45mMigrating a large-scale banking app to Compose
43mSwitching to Compose? Don’t Rush!
38mAchieving Maintainability: Best Practices for Keeping Your Android App Up-to-Date
37mMigrating your app to compose, step 1, live coding
27mHalf Way to clean architecture
01h 09mJetpack Compose for consistency of your apps' UI