Rebuilding BookMyShow for Scalability & Maintenance
summary
Rebuild replaces the old app with 3 lakh lines of code written in six months by a parallel team of 8 Android developers, using an MVP-based architecture, modular feature packages, Retrofit behind a network-manager abstraction (so swapping to Volley is trivial), Realm for storage, and unit tests. Self-sufficient view components, a param-builder API, and separate repos cut duplication; multidex causes startup and device-crash issues; rollout hits 20% initially and feature delivery drops from ~7–10 days to about 2 days.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:13Ground-up Rewrite
- 2:24Should you rewrite ?
- 2:56Why Re-write ?
- 3:30Challenges
- 11:09User Experience
- 13:28What's different?
- 19:49Simple human readable API request builders
- 28:37The Future
- 29:28Automatic Code Generation
- 31:08Asynchronous Event Driven Architecture
related talks
49mBuilding for the future at Snapchat
27mHalf Way to clean architecture
39mScaling an Android App from 1 to 100 developers with modularization.
38mAchieving Maintainability: Best Practices for Keeping Your Android App Up-to-Date
18mBuilding Mobile as a Platform-First Architecture
41mWrite once, ship multiple times
40mScaling Android Apps
27mModularising the right way