News for hackers. Stuff that matters.

A comment on Apple declined to implement 16 Web APIs in Safari due to privacy concerns. Parent comment

Re:Apple declined to implement 16 Web APIs in Safari due to ... by schwartzworld on Tuesday June 30, 2020 @08:01AM (#23689191)
counterpoint to that argument: if you want to create an app that runs on both Apple and Android products, and you know that Apple doesn't support the progressive web app specification, why would you waste your time? It makes more sense to use a cross-platform development tool and release on the app store when one of the two big software platforms doesn't support the spec.
[ Parent | on HN ]
Re:Apple declined to implement 16 Web APIs in Safari due to ... by scarface74 on Tuesday June 30, 2020 @09:08PM (#23696669)
Any app that you wrote would also have a web equivalent any way for non mobile environments. So why not just do an iOS app and a web app?

And still waiting for someone to give me an example of an app that makes a lot of money on the App Store through in app purchasing, that could probably make just as much money as a PWA if it weren’t for mobile Safari.

[ Parent | on HN ]
Re:Apple declined to implement 16 Web APIs in Safari due to ... by RodoBobJon on Tuesday June 30, 2020 @09:08AM (#23689596)
But the implication of this argument is that the benefit of PWAs is to the developer rather than the user, right? If PWAs actually benefited users, then creating one instead of an Android app wouldn’t be waste of time even if you had to create a separate iOS native app in either case.
[ Parent | on HN ]