Live data from Hacker News

PWAs wont replace native iOS apps

app.campsite.co

21–30 of 268 posts

Re: PWAs wont replace native iOS apps

#22

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

It's much better, but most of our users are on iPhones. The one (yes, one) Android PWA user is really happy.

Probably the best part about PWAs on Android is that you install it more like an actual app. iOS still makes you "Add to Home Screen" which is very unintuitive.

Re: PWAs wont replace native iOS apps

#24

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

> for the best experience, use

In this case you’d need “use ”. There’s no alternatives to Safari for PWAs on iOS.

Re: PWAs wont replace native iOS apps

#25
PWAs will never be as good as native, definitionally. There is always API drift. There is always runtime cost. Nothing inside a system can ever have parity with its parent container. If it could, it would be the system itself.

People's experience with hardware and physical objects matters. If you accept that, you should always want to be closer to the metal at the cost of convenience or portability.

Re: PWAs wont replace native iOS apps

#26

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

“Am I wrong? No, it is the users who are wrong.”

Re: PWAs wont replace native iOS apps

#28

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

> for the best experience, use In this case you’d need “use ”. There’s no alternatives to Safari for PWAs on iOS.

This is unfortunately correct. Chrome on iOS uses Safari's Webkit, which is horribly broken on things.

Re: PWAs wont replace native iOS apps

#29
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…

I expect this is because they have to provide equal standing to other browsers in both user choice and rendering engine, but they don’t have to and have not provided a way to use an alternative browser in the full-screen PWA mode.

Of course, there are numerous ways this could be addressed, such as not changing anything at all if the user chose Safari as their default browser anyway. But it seems quite clear Apple is willing to drag everyone down with them in their malicious compliance of the DMA.

Re: PWAs wont replace native iOS apps

#30

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

is Apple doing these slight annoyances on purpose to degrade the user experience?

It's to degrade the developer experience to force you to native apps and the app stores for distribution

Post reply on HN