The whole process model for electron is almost identical to the process model for WebExtensions (a single process manages renderer processes, which are instances of browser window objects.).
I don't recommend this, but I've done it and it works - your whole electron app can be a main process that literally caches the resources from your site, and then displays them in a renderer view.
Comments
No disrespect, but I think you're either uninformed or misguided on the topic.
The renderer processes in Electron are literally "BrowserWindow" instances... https://www.electronjs.org/docs/api/browser-window
The whole process model for electron is almost identical to the process model for WebExtensions (a single process manages renderer processes, which are instances of browser window objects.).
I don't recommend this, but I've done it and it works - your whole electron app can be a main process that literally caches the resources from your site, and then displays them in a renderer view.
No disrespect, but nope. Nothing you have said here contradicts what I said.
Electron is not a browser. It is a toolkit that lets you use web technologies to build standalone apps.
Any app can embed a JavaScript engine or web renderer and cache code from the web, even on iOS. That isn’t a special feature of electron.
and we would call that a browser
No, we don’t call any app that embeds a web renderer or uses a JavaScript engine ‘a browser’.
Do you have any idea how many apps do this?
I mean yeah, e.g. a lot of recent games use html/js engines for their UI and everyone I know says that the game's UI is a browser
Yeah, but none of them say the game is a browser.