All 7 Flutter Plugin & Package Development questions
More in Flutter Plugin & Package Development
What is the difference between a Dart package and a Flutter plugin, and when would you specifically need to build a plugin rather than simply a pure Dart package? What is the basic folder structure of a typical Flutter plugin project, and how does it separate the shared Dart interface from each individual platform's own specific native implementation? How should you properly write both unit tests and platform specific integration tests for a Flutter plugin to genuinely verify it correctly works across every single one of its supported platforms? What should a well written pubspec.yaml and a genuinely thorough README file for a Flutter plugin actually include, to help other developers properly understand how to correctly use and depend on it? How do you properly handle a breaking native API change on one specific platform, such as a new required Android permission model, while genuinely still maintaining backward compatibility for consumers of your plugin using an older version of that same platform? How can you design a plugin's own public Dart API to remain genuinely stable and backward compatible across several successive plugin versions, even as its own internal native implementation continues to meaningfully evolve and change over time?
Advertisement
Back to results for “Architecture”
Flutter › Flutter Plugin & Package Development

How does a federated plugin architecture let several genuinely separate teams or contributors independently maintain the different platform specific implementations of exactly the same overall shared plugin?

Intermediate

Answer

A federated plugin splits what would otherwise be one single combined plugin package into several genuinely separate packages, typically including one app facing package exposing the actual public Dart API, one separate platform interface package defining the shared abstract contract every platform implementation must properly follow, and then individual separate platform specific implementation packages for Android, iOS, web, and so on, and this particular architecture lets genuinely different teams or contributors independently maintain and separately release updates to just one single specific platform's own implementation without needing to coordinate a combined simultaneous release across every single supported platform together at once.
my_plugin/
my_plugin_platform_interface/
my_plugin_android/
my_plugin_ios/
my_plugin_web/
Real-world example The official url_launcher plugin uses a federated architecture, letting its own web specific implementation be updated and separately released completely independently of its Android and iOS implementations, without requiring every single platform to always be coordinated and released together simultaneously.

Common follow-ups: What is the platform interface package specifically responsible for defining within this overall federated architecture?;How does a specific consuming app actually know which particular platform implementation package it genuinely needs to depend on?

Publishing Packages on pub.dev;Platform Channels (Native Android & iOS Integration)
All 7 Flutter Plugin & Package Development questions