![]() I imagine this can't work for your purposes since you have a single, standalone, polished application, but hopefully this could help others. If an individual begins regularly releasing updated versions of the software, I can simply ban their user account which was used to purchase the plugins. This requires lots of coordination from pirates, which has not happened yet. If you want to release your set of plugins to the world, pirates will have to match the versions of those plugins to the versions of their application, and if there are other plugins in the internet, they will also have to match. If you're a paid customer, your plugins will also be updated, but if you aren't, now none of your plugins work. Since the barrier to upgrade the application is virtual nothing (free, click of a button), almost everyone updates. I use the semantic versioning, so releases look like 67.0, 67.1, 68.0, etc. When the application updates, the plugins also update. The main application software is free, while the plugins (the real meat of the software) are purchased individually. I release software binaries often, say every two weeks, and the software self-updates with permission from the user. My company deals with piracy in the following technical way, and it works well enough for potential buyers to stay buyers. TL DR - They embraced the piracy / understood those that won't pay never will, those that may can be persuaded, so made something educational and thoughtful out of it. Except, he said as you read down, the way the author explained it really highlighted how much effort he put into making it, and at the bottom copy saying something like "we hope this was useful and avoids you using a crack which might damage your machine, we also hope you realise the effort that goes into making software and will consider paying just $xx dollars which goes towards feeding my family and making more software".įriend was so impressed he just got out his card and bought it. On the page was complete and detailed instructions on how to crack it yourself using a hex editor or decompiler (or whatever!). So the story went - the top link was one to their own website with full instructions on how to crack the app - something like - or whatever. I have faith that some of my pirate users can become my clients one day or another and I would like to take care of this issue myself rather than letting people going to underground forums and download virus.Ī while back a friend of mine told me he installed a 'clean my Mac' application, thought it was decent and went looking for a crack. ![]() I spent my childhood pirating stuff and now my livelihood is selling software. PS : I didn't say Piracy was bad in itself. Should I add an infinitely renewable 15 days trial instead of a limited features trial ?ĭo you know of projects that went open source / free software and how they handled it ? What if I distribute the pirated version myself ? Wouldn't that look weird to paying customers ? Could I add a "I cracked your software, is it wrong ?" in the FAQ and try to not show it if I detect the software is not cracked ? ![]() ![]() I feel like I won't ever be able to convert them to paying customers. The thing is, theses users don't come to my product page for getting updates for example, so I think it's a loss for me because I can't reach them and talk to them. Hi, I'm selling a software and cracks are given in forums on the internet. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |