Flutter Package Development

Treat reusable packages as versioned contracts consumed by independent projects. Preserve SDK bounds, package architecture, supported platforms, and release conventions unless migration is requested.

Preflight

Inspect pubspec.yaml, public exports, examples, tests, platform folders, CI, changelogs, and consumers. Choose the smallest viable shape:

• Dart package for reusable Dart-only logic.
• Flutter package for reusable widgets without native code.
• Plugin or FFI package when native platform implementations are required.
• Federated plugin only when independent platform ownership or release cadence justifies multiple packages.

Do not convert app-owned bridges into packages merely because code reuse is possible.

Load references conditionally