Add an optional iOS "Tap to Play" interstitial button to Loader to accommodate interaction requirements for playing sounds

[eonarheim]

Add an interstitial step to Loader that is optional (and extensible) to have user interact with a UI element to allow iOS to play sounds immediately after loading.

---

This is for the HTML5 Audio Fallback.

Created a test case here: http://kamranicus.com/wp81-ie11-audio-bug/

Issues:

• iOS will not play audio unless there's user interaction
• Mobile devices have a long initial load time causing a significant delay in playback

Related posts:

• http://codetheory.in/html5-audio-behaviour-and-support-in-ios-and-android/
• http://codetheory.in/fixing-html5-audio-problems-in-ios-and-android-mobile-browsers-to-overcome-the-limitations/
• http://codetheory.in/solve-your-game-audio-problems-on-ios-and-android-with-web-audio-api/
• https://developer.apple.com/library/safari/documentation/AudioVideo/Conceptual/Using_HTML5_Audio_Video/Device-SpecificConsiderations/Device-SpecificConsiderations.html

I think the plan will be to implement the app cache storage with the audio tag fallback for browers that support it. Then in WinJS environment, use Windows Runtime API for sound.

[eonarheim]

Is this fixed?

[kamranayub]

Nope. Will need to add local data/appcache enhancement to audio tag provider.

[jedeen]

@kamranayub Has any work been done to resolve this issue?

[kamranayub]

I don't remember doing anything for this, no.

On Sun, May 10, 2015, 18:13 Josh Edeen notifications@github.com wrote:

@kamranayub https://github.com/kamranayub Has any work been done to
resolve this issue?

—
Reply to this email directly or view it on GitHub
#262 (comment)
.

[eonarheim]

We should confirm this is still bug

[eonarheim]

We could use the Xamarin test cloud to help test this
https://www.xamarin.com/test-cloud

[kamranayub]

Tested with Sweepstacks:

• Galaxy S6, Chrome -- No delay, works.
• iPhone 6S - Starts audio after engaging drag

For Web Audio on iOS, you still need to trigger via user interaction:

https://developer.apple.com/library/safari/documentation/AudioVideo/Conceptual/Using_HTML5_Audio_Video/PlayingandSynthesizingSounds/PlayingandSynthesizingSounds.html#//apple_ref/doc/uid/TP40009523-CH6-SW1

I don't know if we can "fix" this--we may just need to warn people in the docs/tutorials.

One idea we had was to implement a flag on Loader where it will pause after loading all assets and say "tap to play" or something. On iOS, this would address the issue as a workaround.

[eonarheim]

@kamranayub I like the "tap to play" workaround in the Loader to get around this iOS limitation

Also this article was pretty good https://www.ibm.com/developerworks/library/wa-ioshtml5/ it suggest a similar workaround

[kamranayub]

Lets make this issue about implementing an optional loader function to do
this (with overridable draw/update). Just need to figure out how to detect
iOS... browser detection sucks, better if we can detect feature or test if
user interaction is required.

On Sat, May 14, 2016, 09:14 Erik Onarheim notifications@github.com wrote:

@kamranayub https://github.com/kamranayub I like the "tap to play"
workaround in the Loader to get around this iOS limitation

Also this article was pretty good
https://www.ibm.com/developerworks/library/wa-ioshtml5/ it suggest a
similar workaround

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#262 (comment)