Re:Apple's intentional crippling of Mobile Safari continues
by xd1936 on Sunday March 22, 2026 @08:27PM
(#47483942)
People like you could turn off these features and continue installing and updating native binaries for the Starbucks app or random hardware companion apps all you want. I'd like first-class PWAs please.
Re:Apple's intentional crippling of Mobile Safari continues
by raw_anon_1111 on Sunday March 22, 2026 @08:33PM
(#47483982)
Funny enough, I just replied to someone who posted a link to the great lengths Slack is going through to make it use less memory on the desktop.
https://slack.engineering/reducing-slacks-memory-footprint/
When the obvious answer I gave about how to reduce the memory footprint and make it more performant was “to stop using fucking [web technologies]” and create a native app
But the question I always ask people who say that it’s mean old Apple keeping PWAs back, why is it that all of these same companies see a need to create an app for Android?
Re:Apple's intentional crippling of Mobile Safari continues
by fennecfoxy on Monday March 23, 2026 @06:55AM
(#47487682)
To your last point surely it makes sense that they'd probably be rolling something like RN or similar where at that point they may as well build for Android app as well right?
Versus with proper PWA support across the board, a single button on the company's site that installs a PWA no matter which platform your customers are on.
Re:Apple's intentional crippling of Mobile Safari continues
by raw_anon_1111 on Monday March 23, 2026 @10:27AM
(#47490038)
Papa John’s doesn’t need a website seemingly and everything you can do on the app you can do on the website. Why is the app so much faster? I can say the same for banking apps, Airbnb, hotel apps, etc
There must be some reason that every major company decided to have an app even though today all of the same functionality is available on the web.
I have no desire for random websites to have that much access to my phone.