3 ms·

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 main

• illiarian 4y ago
  > 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