[MaxBarraclough]

You sound like the right sort of person to ask: what do you make of PWAs as an alternative to proper apps on the AppStore?

I've seen various demos and showcases, some of them with pretty impressive UIs, but I've never encountered PWAs outside of exploring them as a novelty.

[DaiPlusPlus]

We're switching our app from Xamarin to be a PWA (by slowly making our web-app's HTML+JS work as a PWA) - primarily so we don't need to deal with disparate codebases - but avoiding Apple's App Store police is part of the benefit. We were never at risk of breaking Apple's policies because we're B2B, but being to publish updates immediately without having to wait 24-48+ hours for App Store review (and having to explain our app to the reviewer and create a test account for them) is a huge benefit.

We made the change after reassessing the PWA landscape and seeing that iOS 13 and Android's level of support for PWA features makes it worthwhile. Apple is dragging its feet with PWAs - but the way our app works means we don't need any of the missing functionality (like Web Push) and iOS's weird PWA app lifecycle suits our application fine as it isn't intended to be used offline for more than a few hours anyway.

[ShamelessC]

Not the person you're asking, but I've seen it suggested that Apple is slow to implement PWA features into Safari, perhaps precisely for this reason.

Would love to be corrected on this btw.

[JamesSwift]

The current deal breakers on iOS are missing push messaging and background operation. So in almost every use case, the user will have to be actively using your PWA for it to provide value. Those two missing features just cripple the experience and apple knows that.