Addressing package ecosystem fragmentation
summary
Discussion claims many duplicate packages (example: geoloccator vs geolocation), urges maintainers to coordinate instead of forking, and shows the federated plugin pattern with platform_interface as a practical way to let alternative implementations coexist. It highlights supply‑chain tooling already in play — scorecard, salsa and SBOMs via sift — and describes the Flutter Favorites process plus plans to automate checks and publish clearer recommendations so maintainers and users can pick high‑quality packages reliably.
AI-written summary · about
chapters (14)
- 0:00Ecosystem fragmentation intro
- 1:23Unnecessary package duplication
- 5:02Package fragmentation philosophy
- 8:13Aligning interests to reduce fragmentation
- 11:49Supply chain security
- 13:57Library design for flexibility
- 15:22Evaluating package quality
- 18:50Flutter favorites criteria
- 23:14Improving package discoverability
- 28:48Streamlining Flutter favorites
- 31:15Dart ecosystem communication
- 35:34Package choice challenges
- 37:03Opinionated Flutter docs
- 40:14Google's opinionated shift
related talks
26mPower of federated plugins in Flutter's ecosystem
55mOne Plugin, Six Platforms!
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
15mFlutter lessons for federated plugin development
35mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
40mKeynote - Flutter Is Everywhere
09mFlutter for Enterprise: How your company should be building with Flutter at scale
42mKeynote - Let's go far with Flutter