Engine management/lifecycle and so forth

[banjerluke]

All that annoying production-ready stuff we need to handle:

• Changes in speakers/headphones/Bluetooth connections
• Sample rate changes?
• Playing nice with other apps / being backgrounded
  • I don't play audio in the background, because currently WebViews aren't able to run in the background
• Passing errors back through Cordova to WebCode

You mentioned making certain calls in AppDelegate. Keep in mind that we don't have access to that file from our Cordova plugin. See below.

Cordova does have a few events it sends to plugins, which we might want to listen and respond to (stubs in CordovaAudioKitPlugin.swift):

• onAppTerminate
• onMemoryWarning
• onReset - called when WebView refreshes - we should reset/destroy everything here, as we don't know if it'll be wanted after refreshing

About that last point. I'm planning to expose a setting in the app to choose an audio backend: AudioKit or Web Audio API (obviously with more user-friendly names). AudioKit will be opt-in at first, until I gather enough data to support making it opt-out. When the setting is changed, the WebView will be refreshed and the web page reloaded with whatever their preference is. Therefore, we don't want to instantiate any AudioKit objects until after the plugin calls initialize, and we want to be able to shut all the AudioKit-related stuff down if they refresh the page with Web Audio selected.

[banjerluke]

Oh, hang on... looks like the AppDelegate object is exposed to the plugin (in CDVPlugin) after all. So you can access it with self.appDelegate() in CordovaAudioKitPlugin.swift.

[banjerluke]

Check out the dev/destroyable-audiomanager branch if you want, where I started down the path of making AudioManager something that can be instantiated and (eventually) destroyed on command.