Which Flutter practices keep a codebase healthy?

Healthy Flutter code is mostly about boundaries. A widget should describe UI, not perform HTTP calls or own global state. Features should be easy to navigate, with clear folders for presentation, domain and data. Lints and formatting remove trivial review noise so reviewers can focus on behaviour.

• Enable flutter_lints and treat warnings as failures in CI
• Use const constructors and small widgets to limit rebuild scope
• Inject repositories and services instead of constructing them inside widgets
• Handle loading, empty, error and success states explicitly
• Support text scaling, screen readers, keyboard focus and sufficient contrast

class PriceTag extends StatelessWidget {
  const PriceTag({super.key, required this.cents});

  final int cents;

  @override
  Widget build(BuildContext context) {
    final formatted = (cents / 100).toStringAsFixed(2);
    return Semantics(
      label: 'Price ' + formatted + ' dollars',
      child: Text(formatted, style: Theme.of(context).textTheme.titleMedium),
    );
  }
}

Team-level practices

Agree on one state management and routing approach per app, document exceptions, and keep dependency versions reviewed. Add CI that runs formatting, analysis, tests and a release build. Review pull requests for lifecycle leaks, unbounded lists and missing error states rather than style preferences that a formatter can settle.