3 ms·
Pros: - Low friction install process. Prompt user and you're done. - No extra distribution channel (same build as web, auto updates baked in) - Permissions s
by chromakode 4y ago
Pros:
- Low friction install process. Prompt user and you're done.
- No extra distribution channel (same build as web, auto updates baked in)
- Permissions sandboxed by browser.
Cons:
- Compat (though for some simple apps using mature APIs this is not a big issue)
- Limited to browser features and performance. Can't integrate deeply with OS.
- BackBlast 4y agoAdditional Pros: - PWAs have much lower download requirements, whatever your SPA page weight is pretty much the download size. 1-3MB is pretty common. - PWAs will use lower memory overhead as you don't need a new copy of the browser - it shares with the likely default system browser. - Launch time can be very snappy even on lower end systems if the base browser is already loaded and you manage offline assets well. - Don't need to build for Windows, Linux, MacOS. One build serves Web, Windows, MacOs, and Linux users. Additional cons: - No guarantee of local storage remaining unmolested by the browser. In practice, it's fine unless a user's disk is filling up then you can get purged. - Most obvious OS integration limitation is the inability to control the menus on MacOS. You get a generic set that comes with the PWA.
- depressedpanda 4y ago> - Don't need to build for Windows, Linux, MacOS. One build serves Web, Windows, MacOs, and Linux users. Don't forget that they also get Android and iOS, unlike an Electron app.