Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

on the one hand, a browser engine monoculture is going to be a disaster for the standards-based internet (if it's not already a disaster).

on the other hand, apple crippling webapps with a half-assed browser so that they can sell apps and rent-seek also sucks.

i'm glad safari exists, but for the wrong reasons. it's such a tragedy that there are not more for-profit browser companies.



> apple crippling webapps

Of course apple isn't crippling them.

On top of that you have the world's most popular OS with none of the perceived crippling, and we've yet to see a single amazing web app on that OS.


Apple IS crippling webapps.

They just released new Wake Lock API, but it only works in browser Safari. It is broken in PWA...

QA cannot be that bad they do not test PWAs for new features.


> Apple IS crippling webapps.

Of course it isn't. Unless you can come up with a non-random list of things of what constitutes a PWA. Everytime someone screams about Apple not doing something in PWAs, that list is different.

Meanwhile, as I said above, there's an OS that holds about 70% of the world's marketshare that has none of this "crippling" as you put it. And yet, there are literally none of these amazing PWAs there that Apple supposedly cripples on their OS.

Something tells me, the problem doesn't lie with Apple.


Just because you do not like PWAs does not mean there are not amazing uses of PWAs.


> Just because you do not like PWAs does not mean there are not amazing uses of PWAs.

Talk is cheap. And yet in all these discussions no one ever says "ho, look, over there in this amazing OS with no restrictions that has 70% of the world's market there are these amazing PWAs, just look at them!"

It's always complaining about some absolutely random API that absolutely must be there on iOS for the PWA to finally happen (even if it exists on that other OS).


As I said, there are more people in the world than you.

There are other opinions also.

I know it is hard to accept it.


See how there's still zilch about the amazing PWAs on Android.

But sure, do tell me how it's "just my opinion".


My most useful PWAs are local websites. City transport, government websites etc.

These sites never make their own native app because they cannot afford to maintain those apps.

Websites and PWAs are great and cheap compared to apps.

But it is not hard to google?

https://www.monterail.com/blog/pwa-examples


> But it is not hard to google?

The question about hard-not-hard to google.

Always in discussions about Safari you will find someone complaining about "Apple crippling PWAs" and coming up with yet another random APIs that they absoluely need to finally make a great PWA.

Always in these discussions I hint that Android is 70% worldwide market share, and has none of the perceived restrictions on PWAs. Surely these amazing PWAs that Apple doesn't allow should exist there. Right? Right?!

And invariably there are crickets.

Even your "example" are literally "we made our site not suck and open faster, this increased conversions, yay! It's all because of PWAs".

Of course it's not. Correlation is not causation. If your page load went from 3s to 0.9s (Washington Post) or is now 4x faster (BMW), it's not really PWA who's responsible for people staying on your website. Oh, you pushed your bloated abomination of a website into offline storage on users' phones and now the site opens faster? Yay (not)!

And then there are egregiously bad takes like "Thanks to PWA Telegram's platform cna be accessed from different devices". Newsflash: Telegram's native apps are available across different platforms




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: