Or you could require a password from the user, if the Market license check fails. You could tie the password to the IMEI if you wanted, using a simple table in the code.
On Jul 27, 2:14 pm, Trevor Johns <[email protected]> wrote: > Yes, in this case, I think this is the best approach. Subclass > ServerManagedPolicy, and on getting a NOT_LICENSED response from the Market > licensing service, query your own server to see if the user is authorized to > bypass the license check. You'll probably want to sign the response from > your server as well, just to make sure it's not being spoofed. > > -- > Trevor Johns > Google Developer Programs, Androidhttp://developer.android.com > > On Tue, Jul 27, 2010 at 11:32 AM, Open <[email protected]> wrote: > > I just finished reading the docs on Google's new Android License > > Verification Library. > > > I often give out free copies of my applications to beta testers. I > > don't, however, want the beta testers to share the app with their > > friends. What's the best way to give out a device-specific license > > free version? > > > From what I can tell I will need to create a custom policy and then > > maintain a list of authorized devices/accounts in my own backend that > > I can check. > > > Is that what other devs are doing? > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected]<android-developers%[email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
