I built a progressive web app and published it in three app stores
&gt; From minor things like “iOS Safari won’t let you play audio without first interacting with the page” to major, show-stopping things like, “iOS Safari won’t let you play the next song if your app is in the background or if your screen is off.”<p>I disagree that these things are purely because Apple wants your $99&#x2F;year. Maybe that&#x27;s part of the story, but not all.<p>I am glad that websites cannot play audio without the user first interacting with the page. I am also glad that websites can&#x27;t play audio in the background — as a user, I would find it too &quot;buried&quot; behind Safari and I wouldn&#x27;t appreciate the feeling that a website was running in the background. (Yes I know you can control audio via the Notifications Center and Control Center.)<p>I appreciate that these permissions are reserved for apps that Apple has vetted, even if this is a pain for developers and they are not a perfect institution, as a user I appreciate that they are trying to maintain quality and encourage good app behavior.<p>I&#x27;m glad your app had to jump through these hurdles to gain the functionality your users wanted. Like you said, it&#x27;s where the users are they were asking you directly for it. These are higher-level permissions and should not be free for the taking.