implementation = authentication :) On Nov 30, 1:56 pm, LambergaR <martin.s...@gmail.com> wrote: > You could implement an oauth-ish implementation. Basically, that would > mean: > - user has to register on-line and purchase the application > - at the first application run, user is redirected to web (using > webview for example) and is required to login > - application should send some information to the system (app version > or an ID that would change accordingly) > - system generates a unique ID and returns it to the application > - application is able to check if the key is valid > > Cracking this kind of protection would be fairly simple, but on the > other hand, the solution is quite easy to implement.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en