The problem is that those approaches require the developers to actually care about what browser the user has installed instead of pushing Chrome everywhere.
The problem is that those approaches require the developers to actually care about what browser the user has installed instead of pushing Chrome everywhere.
Yes, each Electron app ships a copy of node and Chromium engine, but user gets icon on a desktop, ability to manage windows with whatever window manager and utilities, hotkeys, tray icons, dedicated menu etc.
A few years ago I wrote a framework for daemon-based native/browser apps: https://github.com/jdarpinian/web-ui-skeleton. I used it for a benchmark that I wrote: https://google.github.io/latency-benchmark/ This approach is underused for sure.
Same can be done with web widgets, or a couple of utility daemons.
Well, at the end of the day don't complain about Google owning the Web.
And whatever its problems are, not being an Electron app is not one of them.
Jupyter Notebooks.
You do have to be careful to avoid security issues. XSRF could be a problem if your server exposes sensitive APIs. But XSRF is not unique to this approach, and the techniques for defending against it are well known. And Electron has security issues of its own which are probably more serious.
Overall I recommend the daemon + browser approach. The "benefit" to Electron of only having to support one browser is rarely realized in practice because you almost always want a hosted version of your app as well, and that needs to support all browsers anyway. For example Slack and VSCode both have web versions.
As I keep saying don't complain about Web == ChromeOS, when you push Electron everywhere.