4 ms·
One of my two small companies develop Windows development libraries for use in desktop and server applications and I see the native desktop apps doomed, except
by wslh 11y ago
One of my two small companies develop Windows development libraries for use in desktop and server applications and I see the native desktop apps doomed, except if you are targetting the enterprise (best in niche markets) and you know how to sell to enterprises.
Rule of thumb #1: if you can build the same application for the desktop or the web, choose the web. Don't think more. My company does Windows drivers and some other operating system internals stuff that is impossible to offer as a web app and this is the reason I can't follow this rule.
My last suggestion is trying to attach your app to other revenue streams such as trainings, customization, integration with other apps, and any other service that make you escape from selling individual (and probably cheap) units of your product.
- jventura 11y agoThe application that I want to build is for a niche market (but not for companies), that is why I am in doubt between desktop and web. One thing that makes me want to stay way from web is that if this thing does not work, I would like people to continue using the application, even if I don't update it anymore. If it runs on a server, I will not be able to stop the server until everyone stops using the application for some time. I know some people kill services without thinking too much, but this is a very small niche and my name is relatively known there.. The other reasons of wanting to stay way from web-only is that then I have to take care myself of everyones' data (think application data, settings, etc.); front-end web developments is a pain for me (too many options, none good) as I'm mainly a backend developer; and then there's the latency problem. As I think I said above, my application is something like a productivity application, where everyone does his own thing and there's no intrinsic need for "social" or "sharing" things. The only reason I can think for web is discoverability, hence my doubts, if "discoverability" beats everything else (for desktop apps)..
- wslh 11y agoHow long will it take to develop your desktop application? If it is just a few weeks or very few months go for it and test the market. If it doesn't work after spending some marketing efforts move away. Indeed nobody can predict your success. Again, I think it is very difficult to attack the desktop market even if you target a niche market for end users. Enteprises uses are a different story. One more thing if you insist: look at the OSX desktop market too because the dynamics of the end user consumption are different from Windows.
- jventura 11y ago> One more thing if you insist: look at the OSX desktop market too because the dynamics of the end user consumption are different from Windows. Definitely, even more as I develop primarily on a Mac.. Thanks!
- antaviana 11y agoIf it is not for work and you are not sure, go desktop with pyramidal approach (don't plan for upgrades, just include them, so that everyone has the latest). If it works well, then plan for the upgrade circus, or if your market allows it, subscriptions. If it goes south and you get tired of it, just release a final free "sunset" edition.