ryanheise

That sounds fine. Although if it were me, I wouldn't see the benefit in creating a platform interface. It would only create more maintenance work until the Flutter tooling improves.

Congratulations on completing the package! Where can I find it? I'm not sure if I follow your thinking completely, but the point of a URI is to be a uniform...

OK, I'm not quite willing to work with background channels until that feature makes it to stable. I presume it will still be possible for you to write an app...

FYI, I just saw this mentioned on StackOverflow as yet another plugin: https://pub.dev/packages/uri_to_file

> it currently you need a master channel of Flutter, because the plugin uses background channels, which haven't landed to other branches yet. Do you know if it was included...

Hi @ddfreiling , thanks for the PR. This has been on the table for a while but I hadn't done it yet because I wanted to carefully go through each...

This behaviour does warrant better documentation, but a `main` method needs to be written in a way that can delay any unwanted initialisation until the app actually enters the foreground...

It may help to first get an example that reproduces the issue. I would suggest using a widget that wraps around your app that handles the lazy initialisation of resources....

> I'm doing quite a bit a of setup in the main method Incidentally, in all of that does `AudioService.init` get called first? If you do other setup before calling...

I don't understand the feature request. Your issue title looks more like a bug report. Can you clarify which it is? Feature request or bug?