Achieving Maintainability: Best Practices for Keeping Your Android App Up-to-Date
summary
GetYourGuide’s Android app serves ~75k experiences and just raised about $200M; codebase is mostly Kotlin with about 2% Java, lingering Rx and heavy data binding while Jetpack Compose replaces XML gradually. Migration uses Koin, coroutines, Room, MVI, and a staged integration plan with quarterly roadmaps, hack/focus days, tests (unit + screenshot tests via Paparazzi, UI tests with UiTest Lace), Detect linting, Dependabot, CI that runs only affected-module tests in parallel, and end-to-end checkout checks to cut release pain and lower bus‑factor risk.
AI-written summary · about
chapters (11)
- 0:00Introduction and team background
- 2:19Legacy code challenges and team decisions
- 8:02Building team vision and roadmap
- 13:48Convincing managers with metrics
- 20:32Implementing change with team alignment
- 24:27Testing strategies for refactoring
- 27:35Sneaking refactoring into features
- 31:04Automating maintainability checks
- 33:50Monitoring impact and metrics
- 35:13Cultivating continuous improvement
- 37:19Celebrating success and sharing achievements
related talks
47mUp to Date? Talking About Your App
27mHalf Way to clean architecture
26mMigrating an app with millions of users progressively
58mModern Android Development
51mModern Android Development
26mApp Architecture Then and Now: Lessons from the DroidKaigi Conference App History
44mAn iOS Developer's Guide to Building Android Apps
01h 13mModern Android development