> Of course there aren’t. Indeed > we would have to build it as a PWA for Android and native for iOS. We’ve consistently chosen not to do that. Translation:

> Of course there aren’t. Indeed > we would have to build it as a PWA for Android and native for iOS. We’ve consistently chosen not to do that. Translation: PWAs and their purported advantages are a myth > But, with these recent Safari changes, it might be enough for us to finally consider building PWAs. And they will invariably suck. Edit: It looks like the only "argument" for PWAs is "but on iOS the people have more money". (They also use much more powerful devices than most Androids out there). So the "argument" for PWAs is "we can't even pretend to care about 70% of the addressable market, and even with the purported advantages we can't even begin to think of building these amazing PWAs that would open the doors to people on non-expensive devices etc. because those people have no money and those people dont have powerful phones"