Identify Android App Startup time issues
summary
Defines cold/warm/hot startups and gives concrete thresholds: Play Console: cold >5s, warm >2s, hot ~1.2–1.5s counts as slow. Recommends measuring TTID (first frame) vs TTFD (ready to interact), notes TTID shows in logcat since API 19 and reportFullyDrawn is unreliable. Uses three tools: StrictMode with penalty log/dialog/death to catch main‑thread disk/network, Jetpack Macro/Micro benchmark with traces to get min/median/max and isolate tasks, and CPU profiler flame charts focused on the main thread to find costly initializations.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 3:20Types of app startup
- 10:07Key metrics and definitions
- 14:21Common startup bottlenecks
- 17:12Using Strict Mode for detection
- 21:24Benchmark testing with Jetpack
- 30:11CPU Profiler analysis
- 39:10Q&A and resources
related talks
24mHow to Improve App Startup Time
18mHow we improved our app startup time by 50%
36mWin on startup time! Improving app launch performance
20mMajor Savings with App Startup Shaving
45mLaunch Screens: From a Tap to Your App
45mDeep dive into Modern Android Performance
41mModern App Performance
42mPerformance Paradox: Navigating the Complexities of Mobile App Optimisation