Super apps: wanted a skateboard, built an aircraft carrier
summary
Compares small apps to “super apps” and explains when an Android project needs to shift architecture and organization as it grows. Covers technical and organizational challenges of building modular, multi-team Android super apps, common hidden mistakes that hinder evolution, and practical ways to anticipate those issues to keep the app maintainable and avoid costly rewrites.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:08Speakers and context
- 4:13Super apps definition
- 7:47Feature teams evolution
- 10:16Release train delivery
- 13:51Team sync
- 15:14Feature flipping for safe releases
- 17:384T for super apps
- 19:59Clean architecture
- 21:30Gradle modularization
- 24:17Feature breakdown responsibilities
- 26:45Slow builds solutions
- 28:09Dedicated technical platform
- 30:13Dependency management
- 33:25Shell app alternative
- 34:29Summary
- 35:33Q&A
related talks
46mBuilding a Superapp from Scratch
32mBuild a modular Android app architecture
40mModularizing Android Applications
46mBuilding a SuperApp: Lessons from merging multiple apps into one
01h 00mMobile App Architecture: How to Conquer the Giant!
39mScaling an Android App from 1 to 100 developers with modularization.
44mHow We Built the Superapp "Dealer Online" and What Came of It
01h 28mApps at Scale: An Industry Discussion