Well, I kind of agree that using an own server for protecting your app could be helpful. You could assign individual passwords to each user, they have to log in with your app and your server validates the login credentials. You could also do it "iPhone"-style by asking your testers for their IMEI numbers<http://android-developers.blogspot.com/2011/03/identifying-app-installations.html>and hardcode all these numbers into your app. Then, when your app starts, it reads the IMEI number on the device it is running on and checks that number against the list of allowed numbers. On top of all of that you could limit your app to run up to a certain date like July 25th 2012. After that it cannot be started anymore.
In any case I would make proper use of ProGuard<http://developer.android.com/guide/developing/tools/proguard.html>and sign the app with your own, self-made certificate before handing it out to your testers. You can combine any of these techniques but it won't prevent anybody from trying to steal your work or getting inspired by your ideas. By the way, I would try making these copy-protection checks at several places at once. Duplicate the code, try to obfuscate the list of allowed IMEI numbers and so on. -- 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
