On Oct 28, 5:46 pm, "[email protected]" <[email protected]> wrote:
> Didn't this option used to be disabled on the developer console? I believe it was disabled, yes. Certainly the console used to say that once locked, an app couldn't then become unlocked. On Oct 29, 2:43 am, westmeadboy <[email protected]> wrote: > Is there any reason to use copy-protection? What about free apps - > even less reason? I use it on my paid apps for the same reason I put a little padlock on my suitcase. It won't stop a determined thief, but it will keep honest people honest. In the case of a paid app, it'll hopefully deter most average users from passing it around to all their friends. On free apps, I don't see any reason to do it, and in fact I personally would think it's a bad idea. I *want* my free apps to be distributed as widely as possible, and if that means users sharing them with each other, great! String --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
