Trial versions of software or Free and Paid versions?

[Guru101]

I was wondering what most computer users prefer when it comes down to determining whether or not they want to purchase a license for a software application. Which of the following would they prefer?

A. The application be fully functional, but only for a specific period of time. After that, the person must purchase a license. For example, a 30 day trial period of the application.

OR

B. 2 Different versions of the applications are released. For example a "Basic" edition and a "Professional" edition. The Basic edition is free, but only allows access to certain features of the application. The Professional edition allows access to all the application's features.

[Shuja Ali]

I would go with the second one.

[S_M_A]

Second one for me too but I prefer a non-profit clause if possible/applicable. I have no problem paying for software that I find useful on a every day basis but very often the price is just not resonable for a home pc where you maybe run it a few times a year.

[PeejAvery]

2nd option for me as well.

1. If you have a trial version, there is always the ability to crack it and there goes your income from that project. With the second option, you don't have those features built-in to unlock.

2. Trial-ware always leaves remnant files on the machine in order to determine if the application was pre-installed. I don't like clutter on my drive of worthless (to me) files. The second option would have no reason to leave files event after uninstall.

[HanneSThEGreaT]

I'll quote one of my articles ( Protecting Visual Basic .NET Source Code and Applications (http://www.codeguru.com/csharp/.net/net_general/netframeworkclasses/article.php/c11817__2/) ) :
Trial Applications
Definition
Trial applications allow only a specified limit in which the application can be used. Once the time limit expires, the application is unusable.

Goal
The whole purpose of Trial applications is to let user evaluate your application, but only for a specified time frame. Once the Evaluation period expires, the users must purchase your program.

Example
How exactly can we prevent unauthorised use of our applications?
Well, the first thought that comes to mind would probably be to create Registry entries storing the dates; then, of course, when the Registry date is a specified number of days later than the current date, disallow continuation of the application. Unfortunately, the chance that someone with enough patience can figure out where you saved the information is still there.

What about saving the Registry entries deeper in the Registry, in a more obscure place in the Registry?
That idea might work to prevent people with little patience to figure it out, but it might not work for cracking software.

Okay, let's leave the Registry. Why not store the date values or the number of times the application is accessed in a file?
If you disguise your files well enough, it may work.

The included example ( in the article ) firstly creates a folder named Sys.Dll, and then it sets the folder attributes to Hidden. By setting a file or folder to Hidden, the normal computer user will not see it. However, if you have your computer set up to be able to see hidden files, you will see the folder. A name like Sys.Dll, of course, will make any person think twice about opening it up, and "play around."

The next step is to create a file (with an obscure name and extension)—for example, sys.trx—and store the number of times your application is run in that file. If the user has run your application a specified number of times, exit the application.

Although my methods of protecting against misuse may not be the best, my goal with this article was just to provide a bigger overview of this topic, and to give you a clearer picture of what steps you can follow when you want to protect your code, as well as your applications.

So, it's the second option for me too :)

[GremlinSA]

I'd go for the second option too...

But just a small note... In the Basic edition, do not just disable the menu items for the advanced opptions... Remove the code, completely.. Purchase/Registration of the application will require a new program...

One option for this is to have most of the Advanced options code sitting in a seperate DLL.. When the application starts it simply checks for the DLL file, and if there (and it tests ok), enable the advanced features.. This way Upgrading to the PRO version is simply adding the new DLL to the Applications directory...

Most hacker sites Handle cracking unlock Codes, Patches to enable hidden code, and the sort. but wont distribute full Apps.. Main reason why piracy laws cant close them down... So these sites tend to shy away from putting any copywriten file's up for download...

Gremmy...