On Dec 6, 11:28 am, a1 <[email protected]> wrote: > ..it's really easy to crack any licencing > solution even if code is obfuscated.
That depends on how interwoven the licensing is with the application. I plan on making the effort needed to crack the licensing comparable to the effort needed to understand the workings of the app itself. But what is the value of an obfuscator? If the source code names have been stripped out of the byte code (except for the system calls, of course, which need external linkage) then any variables or methods that I use for licensing will appear just like all the other variables and methods in my app. Their use can only be inferred by their association with suspected licensing system calls, like calls to get the Android_ID or wi-fi MAC address. And these associations can be made as distant as you like, limited only by the complexity you are willing to tolerate in your licensing code and the extent to which you are willing to let that code be interwoven with normal application code. Besides, if I am distributing outside of the marketplace, what other choice do I have? -- 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
