Development Strategies for a 14-Year-Old Android App to Survive a Generational Design Shift
summary
A talk about maintaining a 14-year-old Android app (started 2012) that now contains seven generations of architectures (MVC, MVP, Flux influences, MVVM, etc.). It explains concrete practices used at Eight to keep feature development and re‑architecture running in parallel: defining layer designs, setting clear boundaries between old and new designs, establishing module dependency rules, and scoping routine refactorings so legacy code’s cognitive load and future technical debt are localized.
AI-written summary · about
chapters (7)
- 0:0014-year-old app survival
- 2:46Design patterns over time
- 9:58Legacy data layer issues
- 16:03Avoiding new pattern buildup
- 25:24Gradual legacy reduction
- 30:30Future-proof architecture
- 37:57Summary
related talks
18mArchitecture is vital to build an app. But what is that concretely?
42m10 years of Android Development: The Retrospective
28mDesign Improvements for an Existing App Based on the Guide to App Architecture
40mApp Development - Pragmatic Best Practices
26mApp Architecture Then and Now: Lessons from the DroidKaigi Conference App History
27mHalf Way to clean architecture
40mGrowing Pains: Scaling and Re-architecting Apps Under Fire
41mSuper apps: wanted a skateboard, built an aircraft carrier