I've considered using an obfuscator. As to maintainablity, i figured this is something you run on the code prior to creating a release, and you would never work with the jumbled code for developement. I.e. its part of the build process prior to release, the code itself for developement is always the regular code not jumbled by an obfuscator.
Mike On Tue, Sep 7, 2010 at 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- 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
