06-01-2012 09:32 PM - edited 06-01-2012 09:33 PM
key license model, what is the best way to prevent fraude? I mean if someone buys my app and I am going by the single model, can't they have their mom or dad download the same app and use the same serial key?
Isn't there a way around this and still be able to use the single model? Is it possible to use various keys for the single model?
The only other possibility I see in this is to just change the key every once in a while, but I am looking for other solutions.
Thank you very much.
06-01-2012 09:47 PM
Long story short - you have several options:
1) If you use the try&buy model without own license mechanism - you need to provide two binares, one trial and one full version, App World will handle the rest. However (as per many thread in this forums) this approach is sometimes buggy and often leads to angry customers
2) You can use your own license mechanism, but then you need to implement license key validation in your app. In this case you need to provide a single binary, which is actually the trial version. Once the user purchase the app, he/she receives registration key, enters the key in the app, and the app validates the key.
2.1) Static key - one single key for all app downloads
2.2) dynamic licensing - app key is based on device PIN (and other stuff), you need an own server to send the key to App World
3) In-app purchase - you need to release a single binary with a limited (basic) functionality or time limited full version. Once the user purchases the app, he/she gets the full functionality unlocked. Payment is handled by App World
Choose an option
could someone elaborate on number 2? is it possible to use your own license mechanism? Cause this way I can make several license keys and won't have to depend on to have to use a single one.
Help is appreciated.
06-02-2012 09:09 AM
thanks for replying! hmm......that's very unfortunate, so it's impossible to present a trial version to the public now?
could you elaborate on how to use the single license key mode but prevent fraud the best way possible, is it possible to use a variety of keys with the single model?
06-02-2012 12:02 PM
06-02-2012 12:14 PM
The whole thing with keys is that you need to map the key with the BBID.
not with the single license key model, there is no additional BB info or e-mail required for anything, it just uses a single pin that every end user can use. I just wanna know how much further this method can be expanded, single license is marginally secured but once someone else knows the key it basically is leaked. I would like to know someone's experience with the single license model and what the possibilities are to expand this feature and use just more than a single key like the name says...I'm getting the feeling there isn't.
The thing is I wanna custom provide the keys to my end users, I don't want RIM to be a part of this, at all. And I don't wanna make use of the dynamic code licensing model, I want to strictly use the single license model!
Help is very much appreciated.
06-02-2012 12:21 PM
08-21-2012 12:24 PM