Synthesis of Modern Quality Criteria for Android Apps
summary
Lists specifics: enable LeakCanary for debug builds, run StrictMode in 15 minutes and check layout bounds/overdraw from developer options, split heavy work into a separate Android process, use dependency injection and coroutines to cut allocations, keep rollout to alpha/beta and gate via feature flags, test cheap Chinese devices or cloud farms, log anomalous responses and telemetry for rollback, run CI/CD with SonarQube and reserve sprint time for tech debt. The APQC L index gives a measurable checklist.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:40Agenda
- 10:25Dependency Injection
- 20:51The Alpha and Beta Channels
- 34:09Non Technical Challenges and Issues
- 43:05Eliminate Work-in-Progress
- 46:55What Is Android Project Quality Criteria
related talks
26mFacing the "Quality" Problem in Long-Lived Codebases
10mApp Excellence leads to Business Success: Empowering your organization to achieve it
41mBuilding Mobile Apps At Scale
39mSurprise! Neighboring Code Reviews
31mElements That Appear in Android Project Estimates, or Carefully Buried Landmines
32mRunning An Effective Mobile Engineering Team
01h 00mAndroid at Scale
01h 32mLeveling Up: Panel Discussion