I haven't seen many examples of people using Electron to make applications that really should be web apps instead, but more for packaging web apps with native enhancements. Often I'd prefer a "proper" native app, pushing even more features in the browser IHMO is not the answer.
Ctrl+S -> Save whole webpage
alternatively get the Webpages source code.
There is. The major OSs provide APIs to access the platform browser. The downside is you need a platform specific shim to set this up using native code. So, developers need to step outside of their JS worldview for a few days to avoid that 200mb app size penalty.
If you are building a platform agnostic app then I understand the value of Electron to avoid that work across each platform. But, it seems several of those Electron apps aren't even platform agnostic, so why not build the platform specific shim and be a better citizen on my hardware.
edit: I'm daft
Now that internet is everywhere, couldn't Electron:
1) Setup a common bootstrap mechanism so it's version agnostic 2) Check for the declared version of the app 3) If online (and allowed by system policy) check if there are security issues, or updates for the needed version 4) Advise user where to download the update, or (again, if allowed by policy) allow the user the proceed with the installation?
With some magic to allow a 'side-by-side' distribution of the Electron runtime, on good-ol' durable media, wouldn't this go far to minimize the size of the distributions of these Electron apps? You could have a system with one (or more if nessecary) versions of the runtime, and multiple apps using that runtime (with isolated profiles, of course ...)
Oooh, we could give this core a snazzy name like "Flash" or "Silverlight" or something too.
Once again, history repeats itself.