zlacker

>>samwil+(OP)
,,In addition, Apple has been underfunding Safari for the past decade leading to missing critical functionality and a buggy experience for Web App developers thus ensuring that Native Apps, another Apple revenue source, are the only viable solution.''

It's not just funding. Apple changed webapps to delete indexedDB periodically even if they are inatalled on the home screen.

There's no way to have a great experience if you can't store data permanently.

>>xiphia+of
Why should a browser app be allowed to store data permanently? I think that breaks normal ideas about how browser apps work, except for cookies everything is stored server side.

>>msh+jg
We're talking about for installed Web Apps here.

Ask yourself the same question about Native Apps. Why should any Native App be allowed to store data permanently. The answer to that question is the same for Web Apps.

>>mtomwe+eh
I (and many others I suspect) like web apps exactly because they cannot do what native apps can. If a web app was allowed to do what a native app why would I use a web app? It would just bring the bad sides of native apps to web apps.

>>msh+li
1. Interoperable between all operating systems (mobile and desktop) 2. Does not lock you into proprietary ecosystems 3. Is built on free and open technology, and investing in that technology helps make it available to others 4. Is not subject to the whims, taxes and control of the gatekeepers

Web Apps can be every bit as capable as Native Apps except with security and privacy built in. For consumers, businesses and competition, Native Apps need to be relegated to to apps that require cutting edge use cases

>>mtomwe+Dk
I would say that a web app is worse than a stand alone native app from a open perspective.

Unless the app is open source why would it matter to me if it is build on free and open technology?

I would say per definition a webapp is less free than a native app as its under the control of the server operator and not running locally. I know iOS have somewhat webified apps to let them control if people can run them but the old idea of the native app would be entirely under the control of the user, even if its closed source.

I also dont think a web app can do privacy as well as a native app. A native app you can firewalled off from network access while with a web app you are at the mercy of the developer and server operator.

>>msh+7q
With a web app there is a direct relationship between the site owner (let's say HN) and me. There is no Apple middleman in between, making rules about what the service can do or can't do, taking a cut of the profits, shutting down the service at their whim, deciding which updates are good and which are not. Same for Google on Android.

>>pmontr+mB
I think it's bold of you to assume that in a world where Apple decides to have 1st class support PWA's that it won't also come with the same restrictions as native apps.

They'll make you submit your PWA for app store review, sign your asset and JS bundles so all other's won't load, make you support "Web IAP", and go through review again every time you want to update your bundle.

Hitching your "I want to be be free of Apple's platform control" to "I want PWA's" is a recipe for disappointment.