> A quick search show plenty of articles talking about the limitations of webapps on iOS. Again: "PWAs" are a dozen different standards (or perhaps more). And

> A quick search show plenty of articles talking about the limitations of webapps on iOS. Again: "PWAs" are a dozen different standards (or perhaps more). And everyone selects a different subset of them to call "the one true PWA". For example, some may say that "omg I need direct access to Bluetooth or other hardware APIs". Well, those are Chrome-only non-standards that neither Firefox nor Safari will implement. There are some like push notifications which are debatable (but arriving in Safari this year). And then there's background sync that Chrome enabled by default in 2016, and which still had issues in 2019 that both Firefox and Safari objected to: https://github.com/mozilla/standards-positions/issues/214 https://github.com/mozilla/standards-positions/issues/214 No idea what their position on it is now. And so on and so forth. But these articles and half of HN will scream until they are blue in the face claiming that "it's Safari that's holding the PWAs back". Where reality is more complex and the narrative is mostly driven by Chrome, unfortunately.