The Impact of App Platform Teams
summary
A mobile platform team for a 30‑engineer org with four platform engineers standardizes builds with convention plugins, runs a remote Gradle cache and slim CI Docker images to cut cold CI startup ~50s and local incremental builds to ~90s, switches to JDK21+G1 for a 12% build time drop and 40% less GC, achieves 92% CI success rate, automates releases with a Kotlin release CLI, uses Paparazzi+Showcase for screenshots, contract tests for integration, and sees ~30% app startup improvement via baseline profiles and CMP features with Compose Multiplatform.
AI-written summary · about
chapters (8)
- 0:00Mobile platform teams intro
- 1:08What platform teams do
- 5:20Slow builds with plugins
- 10:18CI reliability and speed
- 17:12Automate release end-to-end
- 25:28Testing infrastructure
- 34:10App health and performance
- 36:16Q&A
related talks
46mWhen Software Becomes Everyone's Job
39mMoving fast and staying aligned how automation powers progress
01h 00mAndroid at Scale
33mMeasuring the Impact of Platform Engineering
35mPanel: Navigating the Path to Platform Engineering...
11mStarting Small to Growing Big
26mEfficient Android Builds at Scale: Lessons from Pinterest
22mThe challenges of Platform teams