Ask HN: Pros and cons of web app vs. desktop
Are there any pros of first shipping a web app before moving to desktop and then mobile?
1 comments
Without knowing more about your application, it is a little hard to say.
If we can assume for example that in all cases, your service is "cloud based" and what we are looking at is just how the client is implemented and that your app is even a candidate to be implemented in basic web stacks (your not going to need WebAssembly or a runtime based on it) then...
Traditional "web app" gives you the greatest portability and control over releases/deployments. Your clients are almost certainly going to all be on the same "version" of your app (whatever your web server is serving up).
While server certificates might be a hiccup, that is generally much easier than working through being able to sign your code. There is also more implied trust via the browser sandbox rather than running code more natively.
You also will not have to deal with distribution stores that will take 10% to 30% of your revenue.
If we can assume for example that in all cases, your service is "cloud based" and what we are looking at is just how the client is implemented and that your app is even a candidate to be implemented in basic web stacks (your not going to need WebAssembly or a runtime based on it) then...
Traditional "web app" gives you the greatest portability and control over releases/deployments. Your clients are almost certainly going to all be on the same "version" of your app (whatever your web server is serving up).
While server certificates might be a hiccup, that is generally much easier than working through being able to sign your code. There is also more implied trust via the browser sandbox rather than running code more natively.
You also will not have to deal with distribution stores that will take 10% to 30% of your revenue.