On 12/3/2012 11:03 PM, William Ferguson wrote:
Without providing info that compromises the security of your setup, I think there would be many here interested in hearing more about your solution John. Could you elaborate?
I don't know how John's set-up works, but I could imagine it working something like this:
1. The app has a place to enter an unlock code, and the email to the user with the code tells and/or shows them how to find it 2. When a user enters the code, the app sends a secure query to a server to check the code (insert proper encryption/https connection here) 3. If the code checks out, then it flips the (also somehow secured) flag to enable Premium mode and disables the code on the server (so it can't be used more than once) 4. [optional] The Google ID of the person who unlocked it (or their email address) gets sent to the server so that it will auto-unlock Premium on their other devices
Similarly, the in-app payment code would flip the secure flag to enable Premium when it got a Premium Purchase notice from Google.
Would there be any interest in paying for a service & library like this? I was thinking about putting something like it together for my next app anyway, and I have the proper server (and security) experience to make it solid. The only question is whether I put in the extra effort to make it into a product that other people can use, or if I keep it simple for my own products.
No one ever did break my last app's copy protection, so I know a few tricks. :)
Tim -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
