So we think mostly about the commercial tools around mobile app security. And first of all, mobile app security is a broad umbrella. But within that, the area where we really started from was mobile app protection. And so protection for us means protecting the application from reverse engineering and tampering. And there's two primary axes for reverse engineering and application. What we call static techniques and attacks and then dynamic techniques and attacks. And there's different capabilities and protection features that are necessary for each of those. So maybe if we just start with the static side first. So static analysis of a binary is all about you download the binary and you can use any number of decompiling tools that turn machine code back into readable, interpretable, human readable code. So that you can understand the logic, the behaviors and spot IP or secrets or information that can be useful knowledge to an attacker. And the primary mechanism for defending against that is code obfuscation. So obfuscating is all about taking that code and manipulating it in different ways to make it so that it's not readable. So that when it's decompiled, it's very difficult for someone to understand. And that's not to say that it's irreversible, but the complexity becomes so high with good quality obfuscation that the time it would take someone to really make sense of the code is often no longer kind of worth the effort and time that they would spend.

And that's the key difference between ProGuard and our open source approach is a lot of companies initially thought, hey, well, let's use ProGuard. It has name obfuscation. Great. Now our code's safe. But a lot of times when you're analyzing an application, you don't necessarily need the real names of a class or a method to understand the behavior and what's going on. I mean, if you're familiar enough with code, you can kind of put two and two together. Sometimes there's decompiling tools that will conveniently, based on the logic contained within a class, it will assign a name of meaningful value and then find all the other things with that same name and rename them for you. So there's a lot of convenience mechanisms if you rely solely on name obfuscation as the primary technique. So yeah, the layers are super important to work together to really provide strong defense. Yeah. And on that last point, LLMs, I'm sure, are very, very good at that as well. The obfuscation deriving meaning from it, I'm sure. So yeah, layering is very important. This, I guess, could be the approach of, I'll just say DexGuard for now. I know we're going to talk about the fact there is both DexGuard and IxGuard, but it's a compiler-based approach, which is different to wrapper-based. And I think that's maybe some developers already understand or have encountered wrapper-based approaches.