We also got further confidence by consulting sites such as where it shows the audio element as fully supported since several major versions.īig, big mistake. Java, Flash, Unity…) so we started in a quite confident mood. There is no development platform built in the last 20 years that does not support such minimal requirements for audio (and much, much more, see e.g. The background audio is not responsive with respect to game events.īeing a 3-match game, events are at a slow pace so effect sounds would be mostly played one at a time, at most two having a partial overlap. Our audio feature requests are very limited: we want a background track for the game, changing only at level change, and a few sound effects on events. This looks like a peachy start, as the browsers for which support is required are on mature platforms supporting (in theory) a wide range of HTML5 features. Hence we would want our audio solution to work also on desktops. With the well known scaling trick (CSS “transform: scale(…)”) which we built in our mobile app, we got it to run quite nicely in all resolutions, so also on desktop browsers. The game is for mobile browsers, actually a limited and updated range of mobile browsers: Safari for iOS 6+, and the stock browser (i.e. The game: Bust the Dust This story starts when we had to provide audio to an HTML5 game we were building.

Html5 audio autoplay mobile