Check your app's vitals
summary
Shows concrete signals from real users via Android Vitals on the Play Console: no special instrumentation, alerts when crash rate or ANR thresholds spike, and flagged stuck wakelocks, wrong wakeup patterns, excessive network usage. Demonstrates diagnosis with StrictMode + Android Profilers (CPU / memory / network), Systrace for scheduling and thread traces, Battery Historian to inspect wakelock timelines, and Firebase Crashlytics for crash context. Explains fixes: move disk/network off main thread, replace wakeup alarms with JobScheduler or FCM, reduce APK size and background work.
AI-written summary · about
chapters (11)
- 0:00android Check your app's vitals
- 16:05ANR causes
- 19:34BroadcastReceiver
- 23:11Avoiding crashes Ready to use Architecture Components
- 29:54Crash detection
- 31:22Stuck wakelocks Prevent the device from powering down CPU
- 33:54Avoiding wake locks
- 39:29Alarm Manager
- 43:56Avoiding excessive wakeups
- 47:53Other vitals
- 50:43Remember!
related talks
24mMake the Most of Android Vitals
17mVitals: Past, present & future
44mEfficient Android app monitoring
35mIn Search of Performance: the Subtle Art of Android Profiling
32mChasing performance issues methodically
29mMeasure the Performance of your Android App with Sentry
29mHow the Android Framework Monitors, Processes, and Triggers ANRs
26mObservability of your app in production