4 ms·
I always thought that deploying web apps as desktop apps is a great thing to do. As in, not bunch it up into electron, but using shell scripting to start a loca
by kumarvvr 5y ago
I always thought that deploying web apps as desktop apps is a great thing to do. As in, not bunch it up into electron, but using shell scripting to start a local only web server and send a command to the OS to open a localhost page.
The advantages are that you don't need bloated software to do stuff, you have the full power of the OS, because you have a local webserver running, you have access to the file system, etc, you have the choice to use any programming language and framework (not be limited to JS), etc.
I keep thinking why people don't go this way. Are there any glaring mistakes to this approach I am unable to see?
- ferdowsi 5y agoMost consumers don't want anything to do with shell scripting or npm install.
- kumarvvr 5y agoThey don't have to do that. You can have a tiny OS specific program that takes care of the starting part and hide the terminal window and other stuff from the user and simply open a web page. Or, even a full web browser view embedded inside a custom window. (If users expect a non-browser UI)
- nooorofe 5y agoAlmost nobody argues that Web application is easier option for developer. As a user I don't want 500M program to do the same what 30M program did before. It is a real example my company is replacing WebEx with MS Teams. And it is not a single program, more and more like those. Electron is "bloated software". Usability is another issue: web UI elements appears from nowhere, there is no single way to find where is settings button...