| ▲ | Telaneo a day ago | |||||||
> Was no one else using Discord as a progressive web app 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 a day ago | parent [-] | |||||||
> Having to pull along a whole browser 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. | ||||||||
| ||||||||