If it's possible to implement an idea as a desktop app and as a web app, which way would you go?
I'm a little biased here, as as a user I tend to prefer desktop apps over web apps, for the ability to access information quickly: no need to open a browser, no need to login, more responsive, tray integration, notifications, global hotkeys etc. As a developer, I also have more experience developing desktop apps. But as an ISV I have to worry about enriching not only users, but myself too ;)
If you're looking to make money with your application, I would say that web-based is so much easier because every potential client has access to the application as soon as you public it. Desktop applications require a supply chain that's much more work to create than any programming task I can think of.
It's a tradeoff.
On the one hand, a web application allows you to adopt SaaS style fees as well as allowing for an easier deployment model. On the other hand, a web application requires upkeep in the form of servers and bandwidth costs.
Desktop applications allow for a richer UI, which may make your users happier, but are more difficult to deploy and update.
It all depends on what functionality your application is offering. Some apps just can't be run on the web, because they require local PC data that wouldn't be available from the browser.
From a maintenance point of view a web application is definitely easier to maintain (saving time and therefore costs), because it only runs in one place (your server, so any new releases have to go only there) and it's fairly easy to test the different user configurations possible by testing across different browsers. With a desktop app it would be much harder to do this as each user can have a different hardware/OS setup which could cause all sorts of problems (and could be hard for you to replicate it in a support scenario).
In your case, because your background is in desktop, I'd go with that just because you could probably implement it way quicker, and probably implement it in a better way as well.
I guess it depends on how you plan on monetizing things. With a desktop app, you'd be generating revenue primarily from paid buys. With a web app, you can always charge a monthly fee (or even a tiered fee depending on access levels) and maybe even support a free/trial version with advertising.
Also, why limit yourself to one or the other? Use a framework like Adobe's AIR and give yourself the best of both worlds.
Where do your skill sets lie? If you have a ton of experience building desktop apps and not much familiarity with the web, go desktop first. If you're a web developer, web first. Play to your strengths.
How about designs? Know any web designers that could design your web app for you or would it be easier to blow something out on the desktop?
Is the cross-platform aspect of the web worth it, or are you going to build primarily for Windows or Mac or Linux and be comfortable with that?
There are plenty of considerations. Play to your strengths.
Google says that web apps are the future, and they're probably right. Web apps have the significant end-user advantages of being inherently cross-platform (in most cases) and not requiring installation onto the computers that are going use them (again, in most cases). The flip side, of course, is that they're going to be running on your computers, not your users', so you're going to have to spend a certain amount of money on infrastructure, and probably more than you would spend on distribution. There's also the issue of marketing--you probably won't spend more money on it, but it's a lot harder to get the word out when you can't put a box on an endcap at Best Buy.
In any case, if you have the choice of either, I would do some inquiry into the costs of hosting and scaling your application, and if it's not prohibitive to making a profit, I'd say go for the web app. If you can market it well, you'll reach a much larger user base then you would with a desktop app.
That's my two cents in what is undoubtedly going to be a heated discussion. :-)
I prefer web due to:
1) Cross platform 2) You only have to fix a problem once, which lowers support costs 3) You can onboard fairly easily, and even do nice free trial stuff 4) Rolling out new features to all customers is easier
That really depends on what kind of application you have and what you want to do with it.
Web applications primarily have the following advantages:
On the flip side you have these issues:
So what does this all mean? It all depends. Figure out what issues are most important for you.
Edit: Sorry, I just read that you specifically asked about monetizing your app. You should've mentioned that in the body of your question, too ;) But I think I partially answered that anyway, at least I tried to.
Well, just straightforward easier, it's web, 100%. Sticking ads on your site takes about 5 minutes. Probably a little longer to make it look nice.
That doesn't mean you will make as much as you can on the desktop though. But seriously, if you are talking easy, people write scripts that make websites with ads on them. They make $100 and then take the site down. They do this several times a day. There is no way to make that kind of fast money on the desktop.
The caveat is that on the web you are talking about smaller amounts of money, unless you can make the site popular.
I think this really depends on the type of app. Can a web browser handle whatever you want to throw at it? The new browsers are pretty impressive, but people who are still stuck on IE6 won't be happy. Also, how important is offline data? Google Gears is a bad solution to a messy problem. Safari and Firefox (3.5) both have pretty good support for offline data, but again, people with older browsers can't make full use of it. (Of course, you could always drop support for older browsers.)
The major drawback on the web is that you are responsible for the user's data. The major advantage on the web is that you automatically get a much, much wider audience. Reverse for desktop apps – smaller audience, but less burden on you.
hum... still, the question remains open. let's say I have a Java desktop application that I want to monetize. How do I do this? Java includes HTML renderer tht does not support js and I'm not aware about any framework allowing to display Ads (i.e. banners) in a desktop app including all the monetization/reporting APIs. Does someone know a framework allowing to do so?