Going by me and my friends, no.
> striking the best balance between resource footprint
If this is the best balance possible, then that balance is horrible. Having to pull along a whole browser is a massive ball and chain on any program that I wish I could cut off anywhere I see it.
> no additional local apps on their device
This isn't an advantage for my use cases, nor any of my friends apparently.
> still preserving their native UI
As in preserving Discord's or your OS's UI?
I don't care about the former. I'd use DiscordMessenger[1] if it was mostly feature complete and Discord didn't ban third-party clients.
The latter isn't really preserved in any meaningful opinion by shoving it into a browser. The difference in UX post-install between a PWA and a seperate browser window (or a seperate app) is zero to me. It's still not native.
[–] bagacrap 2 days ago
[–] Telaneo 2 days ago
Sometimes, I might actually not be running the browser. And even if I am, a native app is still better.
> you don't have to run Electron next to a browser
I don't quite see the point you're making here?
> your Electron app lags behind in security fixes compared to Chrome or whatever you use to browse
Any app I download is sandboxed to the point I don't see this as a benefit of any magnitude.
Not to mention I might want the option of not updating (although I think this is an option with PWAs nowadays, although I've never actually tried).
> PWAs have a much stricter permission/capability model than native apps
Ditto.
> so you can run PWAs from publishers you don't trust that much.
I don't want to do that in the first place.
Native apps can do all those things better already. Can we please just have native apps instead?
Electron apps do this. PWAs do not because you are already running the browser.
> > no additional local apps on their device > This isn't an advantage for my use cases,
It objectively is, because (a) you don't have to run Electron next to a browser (b) your Electron app lags behind in security fixes compared to Chrome or whatever you use to browse, and (c) PWAs have a much stricter permission/capability model than native apps, so you can run PWAs from publishers you don't trust that much.