![]() So, even if as Gartner says, the CACGR of App Shielding is 20%, we know now that the use of App Shielding technologies is not the same everywhere. The second result we got was related to the geographical discrepancies of the app shielding use:įigure 2 Percentage of application using app shielding technology per country The first result, we got, was the number of applications using one of the protection tools from our sample list: out of the 1400+ apps we examined on Google Play Store, at least 565 use one or more shielding product.įigure 1: Percentage of applications using app shielding technology Nevertheless, as a first approximation, we decided it was good enough for an estimation of the market size. On the contrary, if some artefacts are not uniquely correlated with one product, we will have false negative. If some artefacts are removed from the product they belong to, then we will have false negative. Of course, we are totally aware of the scope in time of such an empirical approach. In a first iteration, they created rules to spot 34 security tools from different vendors:Īs a example, for Rootbeer, “A tasty root checker library “, to know if the app uses Rootbeer, we simply check that the app contains:įor some other product, the rules were more complex. To do so, our team of experts wrote rules to identify the artefacts belonging to well-known security tools available in the market. ![]() Second, we had to list the security tool, we would look for. Our goal with this market study was to answer two questions: ![]() As we have a technology dedicated to HCE technology, how many mobile applications are designed to perform physical payment (i.e., integrate HCE technology)?.How many mobile applications integrate security countermeasures, such as obfuscation or runtime application security control such as rooting detection, anti-debugging, anti-hooking, ….That is why we decided to launch our own naïve market intelligence study. What we wanted to know was: how many mobile apps use app shielding technology and so must be tested with an ad-hoc solution? That is cool, better than nothing but it does not give me any clue about the market size. Looking at Gartner report about App Shielding, it is a growing market, as usual with this kind of report, with a CAGR of 20%. But was it worth investing in converting that project into a product to test any mobile application using app shielding technology? In the context of esChecker, thanks to a project with a payment scheme, we knew that we could create a solution to test the security countermeasure of mobile applications using app shielding technologies. However, the worth of your investment into converting a single project in a scalable product will depend on the size of your market. One customer is a customer, two customers are a market. Once the project is mature enough as an entrepreneur, you often wonder if you could replicate it and make it a product you can sell to a market. In the life of a product creation, everything starts with a first use case: One of your customers knocks on your door and asks you for expertise: this is the beginning of a project. When it comes to creating a product, it is as important to identify the pain points you want to solve than to size their intensity: the number of people suffering from it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |