Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>What to protect against and what not to protect against:</strong></p> <p>Keep in mind that people will always find a way to get around your trial period. So you want to make it annoying for the person to have to get around your trial period, but it doesn't matter if it's impossible to get around you trial period. </p> <p>Most people will think it's too much work to try and get around your trial period if there is even a simple mechanism. For example people can always use filemon/regmon to see which files and registry entries change upon installing your software.</p> <p>That being said, a simple mechanism is best, because it wastes less of your time. </p> <p><strong>Here are some ideas:</strong></p> <ul> <li>You can do a tick count somewhere in registry for every unique day that is run. If tick count > 30 then show them an expired message. </li> <li>You can store the install date, but take head to check if they have more days available than your trial is supposed to be, then do tell them they are expired. This will protect against people changing their date before installing to a future day. </li> <li>I would recommend to make your uninstall, remove your "days running" count. This is because people may re-evaluate your product months later and eventually buy. But if they can't evaluate it, they won't buy. No serious user would have time to uninstall/re-install just to gain extra use of your product.</li> </ul> <p><strong>Extending trials:</strong></p> <p>For us, when a customer requests a trial extension, we send them an automated email that contains a program "TrialExtend.exe" and a trial extend code. This program contacts our server with the trial extend code to validate it. If the code is validated, their trial period is reset. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload