Actually most obfuscators will make your code faster and smaller. It's also not any more difficult to maintain, as it only changes the compiled version, not the original source code. As for effectiveness, it will definitely slow people down and make it less worthwhile, but of course nothing is completely secure if someone wants your code badly enough. You just have to make it difficult enough so no-one wants to spend so much time reverse engineering your code when it would be easier for them to write it themselves from scratch.
On Sep 7, 11:19 am, DanH <[email protected]> wrote: > You can use an obfuscator (and, in fact, many Android experts > recommend doing so). But it makes your code slower and larger and > more difficult for you to maintain, and is of dubious effectiveness if > someone really wants to "crack" your code badly enough. > > On Sep 5, 11:38 pm, xc s <[email protected]> wrote: > > > > > My English is just so-so . I dont 'want to other people > > reversepengineering. my android app. how should I do? -- 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
