PWAs wont replace native iOS apps
app.campsite.co
PWAs wont replace native iOS apps
1–10 of 268 posts
Re: PWAs wont replace native iOS apps
#2seems like minor annoyances rather than the deal breaker the headline insinuates
Re: PWAs wont replace native iOS apps
#3“There are no silent pushes, so we can only update the app icon badge with a displayed push. Ideally, if you clear your notifications elsewhere, we automatically remove the badge on your phone. This isn’t possible with PWAs via push.”
Damn, is Apple doing these slight annoyances on purpose to degrade the user experience?
Re: PWAs wont replace native iOS apps
#4I'm sure Apple doesn't have a vested interest in making PWAs good, I am actually surprised they added webpush.
Re: PWAs wont replace native iOS apps
#5Found the article they linked[0] much more interesting / problematic:
> Now, when a user in Europe taps a web app icon, they will see a system message asking if they wish to open it in Safari or cancel. The message adds that the web app "will open in your default browser from now on." When opened in Safari, the web app opens like a bookmark, with no dedicated windowing, notifications, or long-term local storage. Users have seen issues with existing web apps such as data loss, since the Safari version can no longer access local data, as well as broken notifications.
[0] https://www.macrumors.com/2024/02/08/ios-17-4-nerfs-web-apps...
Re: PWAs wont replace native iOS apps
#6Understandable... PWAs are ultimately an alternative path from traditional mobile apps which will take away money from apple/google.
But as a web dev community we need to stand firm and build PWAs regardless. If we treat pwas on iOS like we did Internet explorer (i.e. giving it special attention and hack solutions as opposed to just not developing for it) we will lose the fight.
I suggest you call out the issues with ios and put disclaimers on your app page saying what's not supported, or add taglines like "for the best experience, use ".
Apple can afford the dev work to update Safari or work with the standards committee, but im sure with their new vr goggles they will take the proprietary route
Re: PWAs wont replace native iOS apps
#7I love developing PWAs because I can quickly and easily make an app for myself and my family that works without having to provision their devices or pay a dev license to Apple. I also use it at work for internal apps. It’s great for all those things.
It’s very obvious to me that I’m a second priority for Apple. Dark mode breaking in iOS 17 and still broken 5 months later. Updating the app is tricky, and making users update is even trickier. Haven’t even bothered to try push notifications.
One pro though is that when my brother wanted to use a PWA I had developed it worked flawlessly on his Android phone. Cross platform support is a big pro in my opinion.
Maybe Apple will fix dark mode with iOS 18, let’s hope they also fix it when using guided access (which was buggy in iOS 16).
Re: PWAs wont replace native iOS apps
#8And what is the state of PWAs on Android? Is it any better?
Re: PWAs wont replace native iOS apps
#9Despite my best efforts and I still have no idea what a Progressive Web App is and why I need to use one. Seems like it's just a website that fits a certain accessibility criteria. It also seems like a hassle to get working correctly offline based on what I have read.
Re: PWAs wont replace native iOS apps
#10Apple has confirmed that PWAs will be just a browser bookmarks from now on.
Other browsers won't also have access to add (actual, not bookmark) PWAs. That is the main reason to not allow them.
If other browsers can add powerful PWAs then it competes with App Store.