Freeware or Payware

I'm still far from version "1.0", but my .NET class libraries for Documentum are nearing the point where demo applications can be created.

But I'm torn, should I make these libraries freely available, or should I try my luck and charge a fair market price.

On one hand I've greatly benefited from the vast library of free software - Back in my UNIX days I cut my teeth on Linux, GCC, Perl, Emacs, and Apache.  More recently I've been using NUnit and CodeSmith - great tools, both of them.

But development cost money  - most significantly VS.net licenses and the cost of my time.

I'd like to get some recognition of this - whatever that means,  and the freeware approach is likely to have a higher user adoption rate, a freeware approach also has the benefit that I can walk away from it at any point. 

The commercial approach is more likely to yield a better product, and I think I'd be more pleased with a successful commercial venture then a successful freeware venture. I might even make some money.

Thoughts anyone?

 

1 Comment

  • Why don't you release v1.0 as a free version to increase your adoption rates and then start charging for upgrades? If you explain that future versions will not be free, nobody will be surprised or angered by a price for later versions.

Comments have been disabled for this content.