Optimize File Size via the Favor App's Size Option

Last updated January 15, 2023 by Appdome

Learn to Prevent obfuscation of publicly available components in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

Why Prevent Obfuscation of Publicly Available Components?

Obfuscation reduces the efficiency of compression algorithms, so obfuscating all the code in the app may increase its file size significantly. Excluding publicly available elements for obfuscation decreases the size of the built app.

Which Libraries are Excluded from Obfuscation?

If you enable Favor App Size, the following libraries will remain unobfuscated:

Open Source Libraries:

Libraries Comment
libstlport_shared.so https://developer.android.com/ndk/guides/cpp-support
libiconv.so, libzbarjni.so https://github.com/dm77/ZBarScanner
libtool-checker.so https://github.com/scottyab/rootbeer
libcrashlytics.so, libcrashlytics-envelope.so https://try.crashlytics.com/sdk-android
libfirebase.so https://github.com/firebase/firebase-android-sdk
libmpdf.so https://github.com/mpdf/mpdf
libj2v8.so https://github.com/eclipsesource/J2V8
libjniPdfium.so, libmodpdfium.so https://pdfium.googlesource.com/pdfium
libopencv_imgproc.so, libopencv_core.so, libopencv_java3.so https://opencv.org

Xamarin Libraries

libmonodroid.so, libmono-btls-shared.so, libmonosgen-2.0.so, libe_sqlite3.so

React Native

libfb.so, libfolly_json.so, libglog.so, libglog_init.so, libgnustl_shared.so, libicu_common.so, libimagepipeline.so, libjsc.so, libprivatedata.so, libreactnativejni.so, libyoga.so. libc++_shared.so

Unity

libunity.so, libil2cpp.so, libcri_ware_unity.so, libgpg.so

Cordova

libxwalkcore.so, libxwalkdummy.so, libsqlcipher.so

IMPORTANT: Some applications which come with anti-tampering might clash with Appdome’s binary code obfuscation. Read this article to learn about Appdome’s Anti-Tampering functionality.

Preventing obfuscation of publicly available components on Mobile apps by Using Appdome

On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Prevent obfuscation of publicly available components without an SDK or gateway:

  1. Upload the Mobile App to Appdome.

    1. Upload an app to Appdome’s Mobile App Security Build System

    2. Upload Method: Appdome Console or DEV-API
    3. Mobile App Formats: .ipa For iOS device or .apk or .aab
  2. Build the feature: Binary Code Obfuscation > Favor App's Size.

    1. Building Binary Code Obfuscation > Favor App's Size by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Binary Code Obfuscation > Favor App's Size feature as shown below:
      2. fusion set that contains Binary Code Obfuscation > Favor App's Size

        Figure 1: Fusion Set that will contain the Binary Code Obfuscation > Favor App's Size feature
        Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).

      3. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Binary Code Obfuscation > Favor App's Size feature via Appdome Console, to add the Binary Code Obfuscation > Favor App's Size feature to this Fusion Set.

      4. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set, as shown in Figure 1 above, and get the Fusion Set ID from the Fusion Set Detail Summary (as shown below): fusion Set Detail Summary image

        Figure 2: Fusion Set Detail Summary
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Cirlce CI or other system:
        1. Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
        2. Look for sample APIs in Appdome’s GitHub Repository
    2. Building the Binary Code Obfuscation > Favor App's Size feature via Appdome Console

      To build the Binary Code Obfuscation > Favor App's Size protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Security Tab > TOTALCode™ Obfuscation section
      2. How: Toggle (turn ON) Binary Code Obfuscation > Favor App's Size, as shown below. Binary Code Obfuscation > Favor App's Size option

        Figure 3: Prevent obfuscation of publicly available components option

      3. When you select the Binary Code Obfuscation > Favor App's Size you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Binary Code Obfuscation > Favor App's Size

        Fusion Set applied Binary Code Obfuscation > Favor App's Size

        Figure 4: Fusion Set that displays the newly added Binary Code Obfuscation > Favor App's Size protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Binary Code Obfuscation > Favor App's Size protection is now added to the mobile app
  3. Certify the Binary Code Obfuscation > Favor App's Size feature in Mobile Apps.

    After building Binary Code Obfuscation > Favor App's Size, Appdome generates a Certified Secure™ certificate to guarantee that the Binary Code Obfuscation > Favor App's Size protection has been added and is protecting the app. To verify that the Binary Code Obfuscation > Favor App's Size protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below: Binary Code Obfuscation > Favor App's Size shown in Certificate secure

    Figure 5: Certified Secure™ certificate

    Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that Binary Code Obfuscation > Favor App's Size has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Binary Code Obfuscation > Favor App's Size and other mobile app security features are in each build of the mobile app

Prerequisites to Using Binary Code Obfuscation > Favor App's Size:

To use Appdome’s mobile app security build system to Prevent obfuscation of publicly available components , you’ll need:

Using Appdome, there are no development or coding prerequisites to build secured Apps by using Binary Code Obfuscation > Favor App's Size. There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.

Releasing and Publishing Mobile Apps with Binary Code Obfuscation > Favor App's Size

After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:

All apps protected by Appdome are fully compatible with any public app store, including Apple App Store, Google Play, Huawei App Gallery and more.

Features Similar to Binary Code Obfuscation > Favor App's Size

If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.

Thank you!

Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.

NEED HELP?

let's solve it together

TomMaking your security project a success!
By filling out this form, you opt-in to recieve emails from us.