ryanheise

Great! Maybe the first step is to try out #568 since once that's merged any new work should be based on that.

This feature would go in just_audio_background, although at the same time there's a whole range of features we could consider adding and philosophically this package is intended to be simple....

Since I personally use Linux, I may personally give this a try (no ETA, though, since I'm also working on several other issues - if someone wants to jump in...

Options options options! There is no problem having multiple implementations in a federated plugin framework. In #103 we had come up with a naming convention like this: ``` just_audio_library_platform ```...

Hmm, I thought I had already implemented audio_session as a noop on other platforms. That is something I should fix: https://github.com/ryanheise/audio_session/issues/34

OK, this is now implemented in the git version of audio_session but I'll hold off doing a release until we can test whether this solves the issue.

Hi @megamegax I was just taking a look at your code and it looks like quite a clever approach! Basically, to start with the existing web implementation as a base,...

@GZGavinZhao Yes, I was coincidentally looking at path_provider last night for the same reason. So in the VLC case, something like this is now possible: ```yaml flutter: plugin: implements: just_audio...

Just a quick comment, on the plugin name, but if the plugin is written entirely in Dart and you move all of the native code into a separate dependency, and...

> @ryanheise I tried to use this approach with the pubspec file but it didn't work. :( I just tried the path_provider example on linux and it works. I then...