Healthy Code: A guide to Flutter App audit
summary
A practical checklist for a Flutter code audit that reports concrete findings and fixes: create a Google Sheets table of perspective / checkpoint / findings / location and prioritize by goal, then estimate and execute. Run linters and metrics — example result: 250 static analysis warnings (50 unused const, 300 trailing commas) — using Dart Code Metrics and Firebase Performance Monitoring, Flutter devtools, FlutterGen, Lcov/Codecov, Dependabot, Crashlytics/Sentry, R8/obfuscate flags and Envy. Watch for a 145 MB Android app bundle, missing model equality, broken migrations, and unreleased CI/CD workflows.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 1:27Why code audits matter
- 3:56Setting audit goals and metrics
- 5:40Developer perspective checklist
- 9:51Code patterns and architecture
- 13:03Dependencies and licensing
- 14:26Persistent storage analysis
- 15:53Design system consistency
- 16:54User experience performance
- 19:44Network and API efficiency
- 21:51Production readiness checks
- 25:01Security best practices
- 29:17Prioritizing and fixing findings
related talks
20mCode Quality Gates for Large-Scale Flutter Apps
31mExploring Static Code Analysis techniques in Flutter
40mBeyond the widgets Evaluating Flutter apps with code assessments
30mCat-like Development: Flutter for Efficiency
36mcontribute to the Flutter ecosystem.
30mAccelerating the Dev Loop with DCM Lints at Betterment
24mFearless Flutter Debugging: When All Else Fails, Hack the Tools!
18mOptimize your productivity with Flutter developer tooling