Break your app before someone else does
summary
Concrete checks and tools decide whether an app survives attack: pull any APK with adb shell pm list packages then adb pull and inspect with aapt to list contents and dump strings; decode with apktool d -f to read AndroidManifest and resources, convert classes.dex to smali, modify and rebuild (must re‑sign; debuggable build possible), or use Charles proxy to intercept and edit HTTP(S) traffic. Use Google Play Alpha/Beta and the pre-launch report (about 10–12 devices) and Fabric crash reports to catch the corner cases that slip through.
AI-written summary · about
chapters (4)
related talks
38mBreak your App before Someone Else Does
43mBreak your app before someone else does
38mAdvanced Techniques for Protecting Android Apps
44mAuditing Your APKs Like a Black Hat Hacker
42mAttack & Defend Mobile Apps
43mAttacking Android Applications
38mReverse Engineering is not just for hackers
01h 07mHow to attack (and secure) an Android app: an introduction