3 ms·

Also, please omit webapps on iOS Safari as an alternative. Apple gives no explanations on why it cripples Safari's W3C compatibility, especially features around

Also, please omit webapps on iOS Safari as an alternative. Apple gives no explanations on why it cripples Safari's W3C compatibility, especially features around PWA, but everyone knows it's to drive developers, users and hence revenue/profits to the app store. Someone needs to sue Apple for this, and the truth will be revealed when the case enters discovery mode, when Apple internal communications on this are laid bare

anoncareer0212 7y ago
Honestly, they just don't have headcount to pull it off/the manager doesn't care. (hi maciej!) He lionizes it on Twitter as not jumping on the latest fads and gets kudos from Apple fans who conflate "new web API" with "slapdash nonsense Google is rushing to try and make the web beat apps" as if it's 2008 still.
BlueTemplar 7y ago
Remember how the first iPhone released without an app store and the plan was for developers to use web apps?
dwaite 7y ago
Progressive Web Apps aren't a standard but a Google web strategy term. Different browsers just have different priorities. For example, Apple prioritized service workers over web app manifests (which BTW are not yet a W3C recommendation). I can only assume this is partly because there have been so many failed attempts at static web app manifests in the past. Them prioritizing other features for earlier release doesn't mean that Web App Manifest support isn't in active development ( https://bugs.webkit.org/show_bug.cgi?id=158205 https://bugs.webkit.org/show_bug.cgi?id=158205 ).
- throwGuardian 7y ago
  Missing in iOS Safari: 1. Binary WebRtc data channel messages 2. Browser notifications that a PWA can use 3. Web App storage beyond 50MB, and guarantee that the OS won't whimsically delete storage, despite being below 50 MB 4. You've already cited Web App Manifest There's probably a ton of other W3C standards not in compliance, but the above list is pretty damning.

anoncareer0212 7y ago

Honestly, they just don't have headcount to pull it off/the manager doesn't care. (hi maciej!) He lionizes it on Twitter as not jumping on the latest fads and gets kudos from Apple fans who conflate "new web API" with "slapdash nonsense Google is rushing to try and make the web beat apps" as if it's 2008 still.

BlueTemplar 7y ago

Remember how the first iPhone released without an app store and the plan was for developers to use web apps?

dwaite 7y ago

Progressive Web Apps aren't a standard but a Google web strategy term. Different browsers just have different priorities. For example, Apple prioritized service workers over web app manifests (which BTW are not yet a W3C recommendation). I can only assume this is partly because there have been so many failed attempts at static web app manifests in the past. Them prioritizing other features for earlier release doesn't mean that Web App Manifest support isn't in active development ( https://bugs.webkit.org/show_bug.cgi?id=158205 https://bugs.webkit.org/show_bug.cgi?id=158205 ).

throwGuardian 7y ago
Missing in iOS Safari: 1. Binary WebRtc data channel messages 2. Browser notifications that a PWA can use 3. Web App storage beyond 50MB, and guarantee that the OS won't whimsically delete storage, despite being below 50 MB 4. You've already cited Web App Manifest There's probably a ton of other W3C standards not in compliance, but the above list is pretty damning.