Result of testing new Soundescape version on Mac Safari: Have to re-write the audio loading/playing logic so that it doesn't get blocked by the "autoplay" policy π’
Apple has some ridiculous "autoplay" policies which make it very hard to implement serious audio applications. This perfectly lines up with their yearlong strategy of preventing web apps to be able to compete with native apps, defending their app store monopoly. I have to find a way now that the audio soundescape if playing on randomized intervals don't get classified as "autoplaying" (which they obviously don't, and all the other browsers, which also have autoplay policies in place, are perfectly able to recognize that). Sorry if I sound frustrated, that's because... I am.
**Now I have to postpone the launch of the new soundescape version. Great**
**Now I have to postpone the launch of the new soundescape version. Great**