Using static analysis we can strip out anything that isn’t
used (“tree shaking”). If you import a huge Dart library
but only use a self-contained two-line method,
then you only pay the cost of the two-line method,
even if that Dart library itself imports dozens and
dozens of other libraries. This guarantee is only secure
if Dart can identify the code path at compile time.
To date, we’ve found other approaches for specific needs
that offer a better trade-off, such as code generation.

How do I do international­ization (i18n), localization (l10n), and accessibility (a11y) in Flutter?

Learn more about i18n and l10n in the
internationalization tutorial.

Learn more about a11y in the
accessibility documentation.

How do I write parallel and/or concurrent apps for Flutter?