How to Improve App Startup Time
summary
How to improve Android app startup time by measuring on release builds and focusing first on cold start. Use Jetpack Macrobenchmark with logcat display-time and ActivityReport logs, capture CPU traces (startMethodTracing or sampling) to find costly calls (e.g., expensive Log.d), then prioritize fixes by time saved versus cost and apply caching, parallelism, or lazy initialization; verify improvements with Firebase Performance dashboards and periodic checks.
AI-written summary · about
chapters (14)
- 0:00First frame
- 0:51What happens during app startup
- 1:26Startup patterns in Android Vitals
- 3:10Why measure it?
- 3:36Why you shouldn’t rely on intuition
- 4:43How to measure it
- 9:30How to time it
- 11:55When executing from code
- 14:47Flame Chart use cases
- 16:55Patterns that don’t reproduce locally
- 19:07Why monitoring is necessary?
- 19:53Common mistakes
- 20:20How to monitor
- 21:58Case study from an app
related talks
36mWin on startup time! Improving app launch performance
18mHow we improved our app startup time by 50%
39mAndroid App Performance in a Nutshell
05mWorkshop: Inspect and improve app performance
45mDeep dive into Modern Android Performance
41mModern App Performance
42mPerformance Paradox: Navigating the Complexities of Mobile App Optimisation
20mMajor Savings with App Startup Shaving