| " but distribution, installation and updating was a headache" I am not sure what headache are you talking about. My product/s are usually single exe with dependencies statically linked and acting in dual role: setup and the end software itself. Installation goes like this: 1) customer clicks on link 2) setup.exe is downloaded and ran. 3) setup copies itself to a proper location and renames itself to yourwonderfulsoftware.exe. 4) When running it may communicate to servers to get whatever data/files/licenses it needs if any. 5) It also checks for new version and if there is any it can self update if you click that "update" button. 6) Before update starts the old version and data are always backed up. Yes it does lack that instant satisfaction experience that comes with good web applications. But then again the if software I want to make looks like a good candidate for Web target way I will implement it as a web app. In hopefully not too distant future Web assembly may make the difference minimal but we will have to wait and see how it goes. |