Yeah,

Obfuscation will help you reduce size, and it will also take away some of
the "hints" that people have.  But you can't get past renaming system
functions, and it's easy enough to do analysis to find out what your
methods are calling system wise, which allows someone easily enough to
infer what they need to look at.  (For example, you can find out what part
of your code uses networking, telephony, etc...)  And sure, if someone
wants to figure out what your code is doing it's not too hard, the
bytecode's all there.

kris

On Tue, Dec 6, 2011 at 11:28 AM, a1 <[email protected]> wrote:

> Using obfuscator is always a good idea because it shrink code (ant build
> system from ADT supports proguard), on the other hand do not really count
> on making bytecode temper proof, it's really easy to crack any licencing
> solution even if code is obfuscated.
>
>  --
> 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
>

-- 
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

Reply via email to