So far, we have been building offline Electron applications. For offline-first applications, we store all the HTML, CSS, and JavaScript content locally and then embed all the files into the resulting package. Then, you can redistribute the package and release new versions of the application in case you need to change the code to bring new features to your application. We also store all the application data locally.
Another popular way of developing Electron applications is storing resources remotely on a server and using your application as a thin client. In this case, you can reduce the number of feature releases and give your application an evergreen. This means that you deploy new changes to the server and all the client applications automatically get new content on the next restart, for instance, or even in real time.
In this...
