Impact of Framework Choice on your Application: A Reverse Engineering Perspective
summary
Builds a toy "coffee→apps" APK in plain Android, Jetpack Compose, React Native (Hermes), and Flutter, then actually modifies each build to make the counter jump by +100. Uses Frida hooks on JVM and native symbols to intercept increment logic, shows R8/R8-like shrinking moves/merges methods and breaks simple name hooks, uses APKTool for React Native JS bundles and Hermes bytecode patching (disassemble/assemble with hpc), and uses modified engine / native offsets for Flutter with dynamic discovery when names are obfuscated. All edits run successfully; complexity and tooling jump from trivial to full native bytecode work.
AI-written summary · about
chapters (10)
- 0:00Framework reverse engineering
- 1:28Reverse engineering techniques
- 5:00Analyzing Android XML apps
- 8:56R8 shrinking and obfuscation
- 12:28Modifying Jetpack Compose apps
- 17:46Reverse engineering React Native
- 21:00Hermes engine modification
- 24:59Flutter reverse engineering
- 34:10Security and framework limits
- 36:14Q&A
related talks
45mReverse engineering mobile apps: how, why, and what now?
19mSecuring your app: Classic Android vs Other frameworks
47mAttacking Android Applications
34mAndroid with a side of Flutter, please
26mInfiltrate Your Own Expo/React Native App
36mWhat I learnt by building the exact same app in Kotlin (Native Android), Nativescript and Flutter
33mHacking and protection of Mobile Apps and backend APIs
44m Meticulously Modern Mobile Manipulations