Even with obfuscation you tend to just end up with the code, but all the identifiers are replaced with a, b, c, etc.. I've still been able to figure Bluetooth protocols and other things without much trouble. For pirates, impersonators, and malware creators, they often just have to find free/pro/goods counter/license check/sig check or add in a call to their own extra code to run. So a little tougher for them, but not the end.
Comments
No, but you can disassemble them to see the Dalvik bytecode[1], which is not too hard to understand.
[1] http://source.android.com/tech/dalvik/dalvik-bytecode.html
You can actually reverse engineer an entire app to java code and see all the resources such as strings and images. Just takes around 10 minutes http://stackoverflow.com/questions/3593420/android-getting-s...
You can prevent this by obfuscating your code in eclipse with proguard, however most apps are not obfuscated.
Even with obfuscation you tend to just end up with the code, but all the identifiers are replaced with a, b, c, etc.. I've still been able to figure Bluetooth protocols and other things without much trouble. For pirates, impersonators, and malware creators, they often just have to find free/pro/goods counter/license check/sig check or add in a call to their own extra code to run. So a little tougher for them, but not the end.