DexProtector Studio

DexProtector Studio is our desktop application, included with every DexProtector license. Studio offers a straightforward GUI where you can control every aspect of the DexProtector protection process. Studio allows you to:

If the DexProtector JAR file is not in the same folder as DexProtector Studio, you will have to specify its location before you can begin using Studio:

You can view and manage your license status by clicking License Info at the bottom right of the opening window.

And if you have not yet activated your license, you can do so here.

We strongly recommend making use of all of the security features provided, as each element of protection adds more security and more resistance against malware, reverse engineering, tampering, and Man-in-the-Middle attacks.

DexProtector configuration is by means of a single XML file, which can be edited directly or via the DexProtector Studio interface.

A default configuration file (dexprotector.xml) can be found in the root folder of the distribution package, but every app (or SDK) has different requirements. We therefore also strongly recommend that you tailor your configuration, in order to target sensitive code and resources for protection, and to enable the Runtime Application Self-Protection and network security mechanisms that DexProtector offers.

DexProtector Studio offers an intuitive interface to guide you through configuring and managing your protection process. It offers descriptions and hints for each protection mechanism in its 'Protection settings' windows, and allows you to apply your chosen settings at a click. These settings are then defined instantly and automatically in the configuration XML file, ready to be applied when the DexProtector process is run.

For more detailed information on the protection mechanisms and how to apply them, it will be helpful also to read through our guide to configuring DexProtector, including a detailed overview of the configuration file, on setting filters to target code and resources for protection, on configuring DexProtector for iOS applications, and on configuring DexProtector for libraries and SDKs (Frameworks).

The first window allows you to specify your DexProtector inputs, in the form of the package you will be protecting, and an initial configuration file, which can be edited later through Studio. You can select either the default configuration included in the distribution package, or a customized configuration XML of your choice.

Here, the file to be loaded for protection is an xcarchive, and a custom configuration file is selected.

After clicking 'Open file and apply preferences', you can manage your protection settings. The 'Protection settings' window gives you an overview of all configuration options; you can manage all protection mechanisms and apply filters through the interface elements:

Or by editing the configuration XML manually. Any changes to the configuration XML made through Studio can be saved at any time, including after the protection process.

Then click 'Run protection' and you can observe the DexProtector process as it occurs. This should only take several seconds.

Afterwards, you can easily view the the protection log, the path to the protected package, and an overview of recent protection results:

And when you are finished, you can save your newly created configuration profile to be referenced, reused, or adapted later: