> Is it possible to "lockdown" the Google Chrome engine in our electron apps so that future chrome changes don't break our apps? Don't upgrade the Electron ver

> Is it possible to "lockdown" the Google Chrome engine in our electron apps so that future chrome changes don't break our apps? Don't upgrade the Electron version? Electron bundles it's own chromium. It won't auto upgrade on you unless you bump the Electron version. > What is the process of developing - how do we launch our apps, compile our apps, change them and re launch? If most of your code runs in the renderer process all the standard web reloading techniques should work similarly. If you change the main process js you may have to restart or find some specific solution. But you probably won't be doing much in the main process. The development workflow can be nearly identical to web dev. The most notable difference is you have access to Node APIs from the renderer process. Makes some things easier but also has security implications. Don't use any Electron specific features unless you need them and porting to web should be trivial.