Scaling up a Super-App
summary
Grab runs 200+ iOS engineers across four time zones, 600 targets and 2k+ master commits monthly, and faces huge build, CI flakiness, start time and binary size problems. Engineering introduces Bazel migration automation (about 80% automated) and achieves build time 30–260 min → 3 min, adds a flaky test analyzer to detect root causes, generates scoped projects, converts many dynamic modules to static linking to cut cold start under a second, and uses app‑size analysis, compiler outlining and remote assets.
AI-written summary · about
chapters (9)
- 0:00Grab’s super-app scale
- 1:45What defines a super-app
- 3:38Developer challenges at scale
- 7:16Migrating to Bazel
- 10:53Fixing flaky tests
- 12:19Reducing app start time
- 14:10Analyzing app size
- 17:26Optimizing app size
- 18:36Challenges and solutions
related talks
32mBuilding at Google: From Idea to Production
42mPorting iOS Apps to Bazel + Q&A
20mAdopting Bazel in a quickly scaling organization
28mGrowing Pains - What happens when your product gets BIG?
21mStreamlining Android app development and release processes
30mThe Bitter and the Sweet of Running a Planet-Scale Build &...
41mDude, Where's My Build? Android CI/CD at Uber
35mTaming a beast