What is the best anti-crack scheme for your trial or subscription software?

Posted by gmatt on Stack Overflow See other posts from Stack Overflow or by gmatt
Published on 2010-04-29T04:08:52Z Indexed on 2010/04/29 4:17 UTC
Read the original article Hit count: 306

Filed under:
|
|
|

Writing code takes time and effort and just like any other human being we need to live by making an income (save for the few that are actually self sustainable.) Here are 3 general schemes to make a living:

  1. Independent developers can offer a trial then purchase scheme.

  2. An alternative is an open source base application with pay extensions.

  3. A last (probably least popular with customers) scheme is to enforce some kind of subscription. Then the price of the software pales in comparison to the long term subscription fees.

So, my question would be a hypothetical one. Suppose that you invest thousands of hours into developing an application. Now suppose you can choose any one of the three options to make a living off this application--or any other option you want--and suppose you have a very real fear of loosing 80% of your revenue to a cracked version if one can be made. To be clear this application does not require the internet to perform all its useful functions, that is, your application is a prime candidate to be a cracked release on some website.

Which option would you feel most comfortable with defending yourself against this possible situation and briefly describe why this option would be the best.

© Stack Overflow or respective owner

Related posts about cracking

Related posts about trial