Vancouver, British Columbia. - July 21, 2004 - If the software you publish has never been cracked, pirated or just plain stolen - you should consider yourself very lucky.
July 22, 2004 (Press Release) --
SoftwareShield Technologies Inc. released research results today that examined how software publishers license and protect their titles. The survey sampled over two hundred North American software companies, revealing valuable information about these publishers.
"Past research focused primarily on the financial losses from piracy. However, our research focuses mainly on who is getting cracked and why. The results are shocking. We decided to release some of the more relevant findings so that software publishers might be better prepared in the future." says Zack Wickes, president of SoftwareShield Technologies Inc.
The study showed that a remarkably high number of publishers (88%) who distribute their products electronically have had cracks or pirated versions of their titles released on the Internet at one time.
Of these publishers, the vast majority (92%) relied on their own developers to build their software licensing and protection systems "in-house". Further, for these same respondents, almost three-quarters (71%) reported that licensing and protection systems were either the last functional requirement implemented, or were over the projects time budget and had to be rushed.
In dramatic contrast to those who have been victims of piracy above, just over half of those publishers who had never experienced illegal cracks of their titles reported they used a third-party licensing or protection software development kit (SDK). More often than not, these publishers purchased the SDK in the first half of the product development cycle or it was already owned from previous projects or titles.
The other half of publishers who had lost nothing to cracks or pirated titles relied on a solution developed in-house. Interestingly however, only 5% of these companies reported leaving the licensing and protection "until the last minute".
Publishers should pay careful attention to two key conclusions from this research:
1. Using a good third party licensing and protection solution can reduce a publisher's probability of a crack appearing for their titles by up to 40%.
2. Leaving the design and implementation of in-house licensing solutions until the last minute or under-estimating the resources required always results in a less effective system. Even if you decide to build your own licensing and protection systems, do not leave it to the end of your project or under-estimate your requirements.
"The decision for most publishers is clear: To maximize profits, reduce costs and enhance security, publishers should buy a good software licensing SDK. Whether you purchase the SoftwareShield SDK or the competitions, the important thing is to buy a third-party solution, as early as possible in your development cycle - your project ultimately will be better off" says Wickes.
The SoftwareShield System SDK addresses this growing need from software publishers worldwide. Publishers use the SDK to electronically generate and enforce their software licenses and guard against unauthorized use by implementing a wide variety of built-in product activation algorithms or copy protection - all from a single binary file.
Check out the SoftwareShield System SDK at http://www.softwareshield.com.
"Past research focused primarily on the financial losses from piracy. However, our research focuses mainly on who is getting cracked and why. The results are shocking. We decided to release some of the more relevant findings so that software publishers might be better prepared in the future." says Zack Wickes, president of SoftwareShield Technologies Inc.
The study showed that a remarkably high number of publishers (88%) who distribute their products electronically have had cracks or pirated versions of their titles released on the Internet at one time.
Of these publishers, the vast majority (92%) relied on their own developers to build their software licensing and protection systems "in-house". Further, for these same respondents, almost three-quarters (71%) reported that licensing and protection systems were either the last functional requirement implemented, or were over the projects time budget and had to be rushed.
In dramatic contrast to those who have been victims of piracy above, just over half of those publishers who had never experienced illegal cracks of their titles reported they used a third-party licensing or protection software development kit (SDK). More often than not, these publishers purchased the SDK in the first half of the product development cycle or it was already owned from previous projects or titles.
The other half of publishers who had lost nothing to cracks or pirated titles relied on a solution developed in-house. Interestingly however, only 5% of these companies reported leaving the licensing and protection "until the last minute".
Publishers should pay careful attention to two key conclusions from this research:
1. Using a good third party licensing and protection solution can reduce a publisher's probability of a crack appearing for their titles by up to 40%.
2. Leaving the design and implementation of in-house licensing solutions until the last minute or under-estimating the resources required always results in a less effective system. Even if you decide to build your own licensing and protection systems, do not leave it to the end of your project or under-estimate your requirements.
"The decision for most publishers is clear: To maximize profits, reduce costs and enhance security, publishers should buy a good software licensing SDK. Whether you purchase the SoftwareShield SDK or the competitions, the important thing is to buy a third-party solution, as early as possible in your development cycle - your project ultimately will be better off" says Wickes.
The SoftwareShield System SDK addresses this growing need from software publishers worldwide. Publishers use the SDK to electronically generate and enforce their software licenses and guard against unauthorized use by implementing a wide variety of built-in product activation algorithms or copy protection - all from a single binary file.
Check out the SoftwareShield System SDK at http://www.softwareshield.com.
Email
Print
SPAM
