Building a SuperApp: Lessons from merging multiple apps into one
summary
Careem merges separate ride, food and groceries apps into one SuperApp by converting apps to AAR libraries and adding a thin container repo that keeps standalone builds working. The team builds a mini‑app interface and initializer pattern so mini apps load on demand, uses a build‑order/constraints platform to lock dependency versions, solves manifest and resource name collisions, and ships a working SuperApp while keeping independent releases for each mini app.
AI-written summary · about
chapters (26)
- 0:00Intro
- 2:02Why talk about this?
- 2:43The World Before
- 4:14Two Options
- 6:24Librarisizing the App
- 9:45A two-MiniApp SuperApp
- 10:02Initial Complications
- 11:51Unwinding the Knots
- 13:38Application Subclasses
- 15:10Application Singletons
- 17:14Food Splash Screen
- 17:49Resource naming
- 18:00Resource Name spacing
- 19:10Library Versioning
- 22:22Questions
- 23:13Application Initialization
- 23:26MiniApp Library
- 26:10Solving More Problems
- 27:05Analytics
- 27:25MiniAppFactory
- 28:22Container Library
- 29:23Initializers
- 30:49Implications
- 35:35Backward Compatibility
- 37:03Things that would have saved us time
- 39:19Moving Forward
related talks
46mBuilding a Superapp from Scratch
41mSuper apps: wanted a skateboard, built an aircraft carrier
32mScaling Android Development without a Monorepo
44mHow We Built the Superapp "Dealer Online" and What Came of It
01h 10mHow Yandex Built a Superapp
24mCreating the Lyft Driver App: Reduce, Reuse, Recycle
24mScaling teams with Federated Super Apps
35mArchitecture for App Bundles