Live data from Hacker News

PWAs wont replace native iOS apps

app.campsite.co

11–20 of 268 posts

Re: PWAs wont replace native iOS apps

#11
post #5

Found 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. User…

That sucks. I use PWAs a lot for my own dev stuff. Let’s hope Apple roles back this change.

Re: PWAs wont replace native iOS apps

#12
I think this is more an illustration of how Apple are intentionally trying to hobble web apps so they can continue to tax all transactions on the app store, than any kind of issue with web technology itself. If Apple implemented the necessary features and fixed the bugs, it could well be a strong alternative to a native app. But they make money from preventing that and are doing everything they can to prevent other browsers from implementing quality PWA support.

Re: PWAs wont replace native iOS apps

#14

“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?

Yes. Obviously.

Re: PWAs wont replace native iOS apps

#15

Despite 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.

You can think of it like a web app that's been coded to have extra features when "added to the homescreen".

When added, the app can work offline, doesn't have an address bar/back button/etc, gets the ability to access device sensors, can send push notifications, etc. A well-made PWA usually looks and feels just like a native app.

Re: PWAs wont replace native iOS apps

#16

I 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…

Looks like Apple is going to fix dark mode in iOS 18 by dropping support for PWAs altogether in my part of the world.

https://www.macrumors.com/2024/02/08/ios-17-4-nerfs-web-apps...

Re: PWAs wont replace native iOS apps

#17

“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?

Does the Tin Man have a sheet-metal willy? Of course they are, it's typical Apple behavior to make it seem that anything non-apple is flawed in one way or another. It's to foster negative opinions towards PWAs so they can peddle iOS apps instead.

Re: PWAs wont replace native iOS apps

#18
post #10

Apple 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.

> If other browsers can add powerful PWAs then it competes with App Store.

This is exactly it. If they can't have full control over how PWAs work, they prefer to cut the feature out of iOS.

Re: PWAs wont replace native iOS apps

#19

I 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…

> 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.

This is exactly why they don't want it. Some will say it's because those are Apple's users and Apple wants to ensure a great user experience and doesn't want unapproved things running on their devices, and others will say it's because it skips Apple's 30% take and their gatekeeping process. My opinion is that both are true, and conveniently both are achieved the same way: by making PWAs enough of an annoyance to both developers and users that they will voluntarily steer away from them. Classic game theory

Re: PWAs wont replace native iOS apps

#20

And what is the state of PWAs on Android? Is it any better?

Yes.

Google Chrome has support and documentation on Android: https://support.google.com/chrome/answer/9658361?hl=en&co=GE...

Mozilla has documentation about PWAs across many platforms, including Android: https://developer.mozilla.org/en-US/docs/Web/Progressive_web...

Mozilla's docs are very clear in defining what makes a PWA special:

> One of the defining aspects of a PWA is that it can be promoted by the browser for installation on the device. Once installed, a PWA appears to users as a platform-specific app, a permanent feature of their device which they can launch directly from the operating system like any other app.

This is precisely what Apple is breaking for iPhone users in the EU.

Post reply on HN