2 ms·
I can take a mobile web site, wrap it in a browser component and publish it to the App Store. Now I will lose one of the advantages of PWA e.g. remote updates b
by threeseed 4y ago
I can take a mobile web site, wrap it in a browser component and publish it to the App Store. Now I will lose one of the advantages of PWA e.g. remote updates but everything else I can do e.g. push notifications, access device APIs.
This has been available for close to a decade.
Guess what. Users hate it. They hate mobile web apps and their slow, clunky, feature-poor, non-native interfaces and for that reason they will also hate PWAs.
- noduerme 4y agoDoes this argument matter to the question of Apple allowing Chromium?
- encryptluks2 4y agoI think you're ignoring the fact that App Store didn't allow PWAs until fairly recently, among a bunch of other things. Mobile web apps aren't slow or clunky or feature-poor and you can design your interface however you want now... except on Apple products. It sounds like your issue is the poor support from Apple, which is exactly what I was getting at. I'd encourage you to read through the blog post I linked here: https://blog.pwabuilder.com/posts/publish-your-pwa-to-the-ios-app-store/ https://blog.pwabuilder.com/posts/publish-your-pwa-to-the-io... > PWAs remain a second-class citizen on iOS > PWABuilder doesn’t guarantee that your app will be accepted into Apple’s App Store. > In 2019, Apple released new guidelines for HTML5 apps in the App Store 2019 isn't close to a decade.