Improve your app and game quality with Android vitals
summary
Play Console now surfaces concrete, actionable checks: the pre-launch report crawls real devices (including Android Q soon) and flags non-SDK compatibility with counts of errors and warnings; Android vitals adds app size as a vital and lets you define 8–12 peer benchmarks. Metrics reveal surprises: ~30% of install attempts fail, three in ten devices have <1 GB free, and every 3 MB => 1% installs improvement. Automated PLR–Vitals linking connects production crashes to Test Lab runs, but requires test credentials and uploaded mapping files to be maximally useful.
AI-written summary · about
chapters (14)
- 0:00Start
- 7:58Android developers blog: Non-SDK interfaces restrictions
- 8:19New restrictions in Android Q
- 9:58Android compatibility in the pre-launch report
- 16:19Existing benchmarks
- 17:21New: Peer benchmarks
- 18:39Peer benchmarks integrated into Vitals reporting
- 18:53Peer benchmarks integrated into Ratings
- 26:06App size in the Play Console
- 27:26App size breakdown
- 30:04Crash stack trace in Android vitals
- 30:48Crash stack trace in PLR
- 31:20Screenshots and videos in PLR
- 31:56Vitals-PLR linking
related talks
17mVitals: Past, present & future
40mAndroid vitals: Debug app performance and reap rewards
30mBoosting Performance Through App Quality Improvements
24mMake the Most of Android Vitals
36mApp quality on Google Play
17mPlan and optimize your game for success on
37mNew and advanced Google Play tools for game developers
32mAutonomous and customized pre-launch testing in the Google Play Console