Tips & Hints for
Shareware/Freeware Authors

Written by Matthias Kahlert, mkahlert@kagi.com
http://www.GeoCities.com/SiliconValley/Pines/8031/index.htm


General Information: Registration Codes

If your application is finished you should think about registration codes. Here are some ideas how this codes might be built...

Also think about how to call this code inside your application and documentation. Not every term is suitable for every kind of code. For example:


None

The easiest way is to set up a checkbox titled "I paid". If the user checks it, the "Please pay your shareware fee" dialog will not appear any more.

Secret Actions

You can put a complete input dialog for the registration key into your application, but no value entered there will ever unlock the program. Instead of entering something the user has to do any secret action to unlock it.

For example:

Universal Code

You can create one single registration code that you give to every user. All users get the same code...

Random Code

The secret registration code might be randomly constructed. Just some specific characters in the code are derived from other characters, so that your software can check if the code matches the given pattern.

For example:

Based on User Data

The registration key may be based on the data you get from the user. It is very common to create the key out of the name of the user... Just play around with the ASCII values of the chars, multiply them, add, convert, invert, etc. You may also include the number of licenses (site licenses) into the key.

Unlocked Version

If a user registeres for your software, just send him an unlocked version of it or give him instructions on how to download that version from your homepage. If you have your own web server you can also set up a folder where the user needs to login in order to get access to it's contents. But be careful that that unlocked version will not get around in shareware archives or CD-ROMs!

Annotations

Do you have any new ideas or aspects? Please let me know. Just send an e-mail to
mkahlert@kagi.com.


Modified on 7. June 1997


Back
1