Attributed Everything: Ensuring Quality for Large Apps
summary
Snap rewrites its Android app and then builds an attribution system that maps every file and metric to a team using owners files and runtime attributed features, producing attributable exceptions via custom RX schedulers and navigation breadcrumbs. UI jank is measured by a frame monitor that flags large drops over 80 milliseconds and frozen frames over 700 ms; snapshots on navigation let the team pinpoint which page caused regressions. APKs are analyzed with modified bundletool and APK Analyzer, exported to BigQuery/Looker, and PRs that add >30KB are blocked; app size falls to its lowest level after these changes.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 3:21What is attribution and why needed
- 5:29Attributed everything framework
- 6:31Owners files and code quality
- 9:21Attributed features and runtime attribution
- 13:10Attributing jerky frames with Yaoming
- 22:02App size attribution with Ben
- 37:04Benefits and future of attribution
- 38:49Q&A and closing remarks
related talks
44mDriving App Stability & Performance Zero to Hero
33mAndroid Benchmarking and other stories
25mConsiderate App Update Delivery
30mBoosting Performance Through App Quality Improvements
41mModern App Performance
29m10 Ways To Improve Your Android App Performance
39mAndroid App Performance in a Nutshell
17mWhat I found when I look into your APK