I think he means just obfuscate one jar, rather than the entire application.
On Oct 5, 7:20 pm, Lance Nanek <[email protected]> wrote: > Why would you think a JAR provides any obfuscation at all? I open them > as ZIP files all the time. Not to mention that Android doesn't even > run Java bytecode. Any JAR you put in your project's classpath is just > a source for Java bytecode that gets converted to Dalvik bytecode and > put into a file in the APK when you build your project. > > On Oct 5, 11:26 am, Moto <[email protected]> wrote: > > > I'm a bit scared about obfuscating my application completely. I'm > > afraid to run into issues where I can't figure out a bug because lines > > and function names wont match. Please correct me if I'm wrong... > > > I thought maybe the simplest way to protect important parts of my code > > is to create a jar of the important files. I know and understand that > > jars are good only for classes and no xmls or other Android dependent > > parts. I believe it would be simple this way since I would not have to > > worry about obfuscating too much and breaking my project. Also, could > > be helpful for distributing to clients a library which they can't > > decompile. > > > In terms of obfuscating jars maybe I could do the same to the Market > > Licensing code to protect my paid application from pirating? > > > What are your thoughts on my approach? Maybe bad idea? What > > experiences have you had with obfuscating your application? Is it not > > as bad as I think? > > > Thanks, > > -Moto -- 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
