For all those who responded positively on using PWAs in the wild, can you explain why you prefer the PWA over the native app (if available)? I am curious why someone would choose it.
My favorite aspects: more restrictive hardware access (e.g. no tracking through Bluetooth or running in the background), having access via platforms that typically don't have apps (e.g. desktops), ability to modify behavior through extensions, caching can clear asset data if I don't use the app frequently (e.g. ridesharing)
The main thing isn't really about it being preferable, feature-wise - it's that it's the future of cross platform apps. If I could have apps like Photoshop or Ableton on Windows, Linux, Mac, ChromeOS, Android, etc - and they all work the same, that's a huge win all around.
I wouldn't count on any other browser to be anywhere onboard with that. Chrome is known for implementing things in a quick and dirty way with complete disregard for input.
Also, Fugu will definitely no bring a signinficant amount of native APIs to the web. Here's the full list [1]
For example, the post I'm replying to mentioned Ableton. Well "I don’t know who the Web Audio API is designed for" [2] Oh, and then there's no guarantee Chrome will not break it the way it broke automatic audio previously [3]
The web is not the long-term future for any foreseeable future
The vast majority of native apps need next-to-no extra features on top of what the web provides. Facebook, Uber, Seamless, etc. etc... all they really need is an internet connection and location. And the web provides that.
One thing I like is that I can use them in my browser with tracking protection. Also nice to know it only has access to browser API's I give it access to - I'm always somewhat weary of what native apps do in the background.
And of course, there's the first-use hurdle. I probably wouldn't even have tried Pinafore if it hadn't been a PWA (in fact, I haven't tried any Mastodon apps). I could just go to the website, sign in, and I'm off.
