Harden Financial Android App

I run a production-ready financial Android app and must lock it down before our next release. The priority is stopping static or dynamic reverse-engineering attempts while keeping performance unaffected. What I need implemented inside my existing codebase: • Code obfuscation that goes beyond standard ProGuard mappings, including renaming, string encryption and control-flow transformations. • Reliable root detection that recognises Magisk-hide tricks and responds gracefully without crashing legitimate users. • Truly secure local data storage, ideally with hardware-backed keystores and in-memory shielding for transient secrets. I prefer custom solutions rather than packaged tools such as DexGuard, so expect to write or integrate your own native components, Gradle tasks and CI hooks. JNI, C/C++, Frida counter-measures and tamper-resistant architectures are welcome if you can document them clearly. You should be based in Pakistan and able to show at least three years of professional Android work that includes security or anti-tamper projects. I’ll share the current source tree once we sign an NDA; from there we will: 1. Agree on an implementation approach and timeline. 2. Deliver a hardened APK/AAB plus a brief technical report that explains every protection layer, how to test it, and how to maintain it in future builds. Acceptance will be based on my own static analysis, runtime tests on rooted devices/emulators and a short penetration review—so please be confident in the robustness of your work. If this sounds like your field of expertise, let’s talk and get started right away.