Manual obfuscation works fine, using an Ant script and ProGuard. It is
not that difficult to set up.
Few things to consider:
* There were some problems with optimized code: Sometimes optimized
code throws errors when converting to dex code.
* All class names that are defined in the Manifest or used as custom
widgets in layout files should of course be excluded from obfuscation.
In our application this is quite a lot (activities, content providers,
widgets), so this somehow prevents complete obfuscation, and it is
easier to guess from the decompiled class names what they are good
for.
Other than that, I don't think there is anything wrong with
obfuscation. It also decreases the apk size slightly, by using shorter
strings for class and method names ("a", "b", "c", ..). Smaller file
size is always good on mobiles :-)
Let me know if you need help in setting up the ant script.
Peli
www.openintents.org
On Sep 24, 10:49 pm, UBZack <[EMAIL PROTECTED]> wrote:
> Does anyone know if there are plans to include an option to obfuscate,
> or encrypt class files (before they are then converted to .dex files)
> within the ADT plugin for eclipse? I've been searching the Android
> group for a while now, it seems that people are manually obfuscating
> their class files, then manually converting them to dex files, which
> is fine if you're building using ant, but it would be really great to
> be able to have the eclipse ADT automatically do this process.
>
> Additionally, does anyone have some idea what exactly is Google's
> philosophy towards obfuscation/class-encryption in Android?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
