Every Flutter project starts clean, then the dependencies pile up. A package for tuples, a union-type library, a state-management package wired in for a single toggle. Take freezed, which most Flutter developers know and love. A few years ago, reaching for it was obvious. Today the language has caught up. Dart 3 ships sealed classes, exhaustive switches, pattern matching, and value equality for records, which cover the union and matching features most teams actually used freezed for. freezed still earns its place when you need copyWith on complex models or JSON serialization, and that is exactly the point. The bar for adding a dependency rises every time the SDK absorbs what it used to do, so the package has to justify itself.

This talk names that reflex, then tours the features hiding in plain sight. Records and pattern
matching for returning and destructuring data, and for equality without equatable. Sealed classes and exhaustive switches for modeling loading, success, and error so the compiler flags the case you forgot. ThemeExtension for keeping design tokens in the theme instead of a scattered constants file. ValueListenableBuilder for rebuilding only the widget that changed instead of pulling in a state package. Each comes with a before and after: the package or boilerplate you ship today, and the few lines of built-in Dart or Flutter that replace it. You will leave able to open your own pubspec, find a dependency that no longer earns its place, and delete it tonight.

The bar for adding a Flutter dependency rises every time the SDK absorbs what it used to do. A
fast, example-driven tour of the Dart and Flutter features now built in, and how to tell which
packages in your pubspec still earn their place.

Key takeaways

• How to tell when a beloved package like freezed is doing work the language now does for
free, and when it still earns its keep.
• The built-in Dart and Flutter features that replace union types, tuples, scattered theme
constants, and single-toggle state.
• A concrete habit for auditing your pubspec and deciding which dependencies still justify
themselves.