Re: protecting time-limited demos
Re: protecting time-limited demos
- Subject: Re: protecting time-limited demos
- From: mathew <email@hidden>
- Date: Sat, 19 Apr 2003 15:40:33 -0400
On Thursday, Apr 17, 2003, at 14:42 US/Eastern, Ron Phillips wrote:
If the consensus was: "Yep, that what most people use and it works
great and here's how" then I would jump on it. So, how does one feel
good about this before writing the big check?
There's no one right answer. You need to make some non-technical
decisions and set your requirements:
How hard you want it to be to pirate your software? Bear in mind that
"impossible" is not an option.
How much are you willing to annoy registered users? In general, the
stronger you make the protection, the more annoying it is to your
customers.
How many sales are you willing to lose? Software sales against
strength of copy protection is kind of a bell curve... Zero protection
means few sales, but too much protection means few sales as well,
particularly if you have competitors who don't protect their software
as intrusively.
Looking at it another way, what's your pricing strategy? Few sales and
high profit on each sale, or many sales and low profit on each sale?
How much are you willing to spend? Stronger protection is harder to
build and harder to debug. The strongest protection of all involves
dongles, and has a per-seat cost.
Are you willing to insist that the user has a working network
connection? Every time the program is run, or just at least once?
Do you want to lock the software to a single machine, a single user, or
a single concurrent user?
Once you've decided those things, then you can start investigating
which technical approaches meet your requirements.
mathew
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.