Engineering notes
The work behind
the protection.
Investigations, design decisions, and the limits that matter when you build a security product.
Android security through a single Gradle plugin.
Bytecode instrumentation, dependency-firewall tests, and a real Frida investigation. What held up, what failed, and where the response stops.
Read the investigation ↗What secure mobile delivery actually requires
Secure mobile delivery is not just a scanning step. It requires visibility across source, dependencies, binaries, runtime posture, and release decision-making.
Mobile engineering is entering a new era. Our tooling needs to catch up.
Why secure mobile delivery now requires better visibility across source, shipped binaries, runtime conditions, and engineering decision-making.
Application security needs engineering intelligence, not just scanners.
Why modern teams need security findings with architecture, dependency, and release context instead of isolated alerts.
Runtime integrity is part of release confidence, not a separate add-on.
Why runtime protection, instrumentation-aware posture, and tamper resistance need to be discussed in the same workflow as application risk.
Follow the work.
Get engineering notes and product updates by email.