Migrate to federated plugin

[sebastianhaberey]

I was thinking it would be good to migrate the plugin to the federated plugin structure to facilitate contribution. As I understand, this would enable developers to contribute platform implementations in their own repositories, without having to go through PRs. Also, it's how the packages maintained by the Flutter team (such as url_launcher and shared_preferences) are structured now.

The necessary steps are detailed here:

1. Create platform interface package
2. Publish to pub.dev
3. Refactor base package to use platform interface package

I think I'm done with step 1, you can preview it here. I'm not sure how to proceed though, since I can't publish under your name (of course). Let me know if you're interested in doing this. If you don't have the time / resources to do it, I understand, too!

[Nimrodda]

Interesting. I need to learn a bit more about federated plugins. I thought it's just another way to organize the codebase 🤔

[sebastianhaberey]

I am also just learning about it. The concept is fairly new and the Flutter team hasn't finalized it yet, but it seems it's the way they want to go in the future.

Since federated plugins involve a lot more publishing, I think what I want to do is publish a "federated" version of the plugin using my account to save us both a lot of back and forth. Also, I have a few major changes in mind that will be easier to carry out that way.

[Nimrodda]

From what I read it doesn't sound like a lot of publishing. After the plugin is converted to a federated plugin, I need to endorse your plugin by adding it to pubspec and then publish a new version. Doesn't sound to me like a lot of a hassle. I think it would be better to have the community working on one repo together instead of splitting.