flutter-dart-code-review

Topics in the source

• Flutter/Dart Code Review Best Practices
• 1. General Project Health
• 2. Dart Language Pitfalls
• 3. Widget Best Practices
• Widget decomposition:
• Const usage:
• Key usage:
• Theming & design system:

Comprehensive, library-agnostic checklist for reviewing Flutter/Dart applications. These principles apply regardless of which state management solution, routing library, or DI framework is used. -- [ ] Project follows consistent folder structure (feature-first or layer-first) [ ] Proper separation of concerns: UI, business logic, data layers [ ] No business logic in widgets; widgets are purely presentational [ ] pubspec.yaml is clean — no unused dependencies, versions pinned appropriately [ ] analysisoptions.yaml includes a strict lint set with strict analyzer settings enabled [ ] No print() statements in production code — use dart:developer log() or a logging package [ ] Generated files (.g.dart, .freezed.dart, .gr.dart) are up-to-date or in .gitignore [ ] Platform-specific code isolated behind abstractions -- [ ] Implicit dynamic: Missing type annotations leading to dynamic — enable strict-casts, strict-inference, strict-raw-types [ ] Null safety misuse: Excessive ! (bang operator) instead of proper null checks or Dart 3 pattern matching (if (value case var v?)) [ ] Type promotion failures: Using this.field where local variable promotion would work [ ] Catching too broadly: catch

This is an excerpt. Refer to the complete source and its current requirements.