But @k00b mentioned it in my websockets draft PR which lead to me prioritize PWA:
Another use for this kind of push system is push notifications in a PWA. I think this would be a big upgrade in terms of people being willing to start and engage in conversations ... and its one of the most frequently and afaict "real" feature requests we get.
But it's of course only the first iteration on it, so things will improve over time :)
And glad that you like it! So "my intuition" (besides of @k00b explicitly mentioning it, haha) that this is one of the more requested features and thus makes sense to prioritize was right :)
I think next steps for the PWA would be to use more intelligent caching strategies (it uses the defaults from workbox which may be network only for the most part) such that the PWA indeed shows better performance (as mentioned in the ticket) and push notifications
We have so much advanced PWA logic we haven't gotten to yet ourselves. Will definitely keep an eye on those tickets and PRs to see what we can do ourselves ;)
PWAs are nice because you don't have to "install" the app. PWAs are nice because it'll work on Android and Apple devices. PWAs allow you to bypass Google and Apples app stores (although you could use something like F-Droid).
I assume it's also easier to update the web app to be progressive rather than writing an Android and/or Apple app.
workboxwhich may be network only for the most part) such that the PWA indeed shows better performance (as mentioned in the ticket) and push notifications