12-02-2008 02:00 AM
I have goggled internet and this forum for a convenient way to restrict application to a device. But I didn't get much.
So I'd like to create this thread to discuss it. You are welcome to post any idea!
I ask this question because I wrote a small tool, it doesn't connect any server. Now I want to sell it. I hope I can find a convenient way to protect my app from illegal copy/installation. As you may know, BlackBerry developers can easily parse .jad file, download .cod files, or even export .cod files from device to desktop, then install it to other devices.
So the main target is to prevent app crack from blackberry developers, and the approach is simple, convenient.
There are two scenarios:
- The application does not talk to server.
- The application may talk to server on first use.
Any feedback is welcome and appreciated.
12-02-2008 05:38 AM
12-02-2008 06:08 AM
I agree completely with everything that Simon says, just wanted to add a few other, hopefully helpful, thoughts.
Possible options for unique identifiers include:
a) PIN - easy to get to, but if the user's device breaks or they upgrade, then they have lost their license
b) Telephone number - I think this is good for consumer devices, but is only available in the later levels of OS
c) email address - be aware that users can have multiple email addresses. I think the default email is a good identifier for the corporate market, for example you could license all users in one company using a wild card like "*@theydomain.com"
I suspect there probably has to a 'license' issued (i.e. some Server communication), so the first issue is how to integrate this with the purchase payment - in other words, only supply licenses to those users who have paid. This is the step that has caused us the most difficulty.
Once you have proof of purchase, then you can be proactive, by sending an email or SMS for example, or reactive by letting the application link to a Server. However note that if your application listens for SMS/emails or attempts to http connect to the Server, it could pop-up a Permissions Dialog, which is really only required for this license process.
Two other things to consider:
a) Are you going to offer a trail period?
b) How are you going to market this application?
12-12-2008 02:21 PM
Thanks Simon and Peter for reply.
To answer Perter's questions:
- The license solution is my first choice too.
- I prefer PIN and Phone#.
- Yes, there will be a trail version.
- I plan to sell it on my own website, and popular sellers like Handango, crackberry, RIM app store.
However Handango simply refused my application without telling any reason. And no reply to my further requirement. I really doubt their attitude to individual developers.