Community

Sometimes, e.g. when your business need is to capture document information from a wide variety of supported document types, you may end up with the large mobile app, which footprint size may be unacceptable for your user scenario (end-users can't wait long, or end-users will delete your app since it's too big, etc.). Or maybe you want to optimize app footprint in any case.

For Android we can suggest two approaches to fight that problem:

• Android App Bundles: recommended way
• Build multiple APKs

1. Android App Bundles

An Android App Bundle is a publishing format that includes all your app’s compiled code and resources, and defers APK generation and signing to Google Play.

Google Play uses your app bundle to generate and serve optimized APKs for each device configuration, so only the code and resources that are needed for a specific device are downloaded to run your app. You no longer have to build, sign, and manage multiple APKs to optimize support for different devices, and users get smaller, more optimized downloads.

Read more about Android App Bundles with instructions on how to implement them in official Android documentation: https://developer.android.com/guide/app-bundle/

2. Build multiple APKs

If you find out that using Google Play for managing and signing your application is not acceptable for you, you can try to manage them by yourself. This will require you to set up building procedures per each supported platform.

Read more about Building multiple APKs with instructions on how to implement them in official Android documentation: https://developer.android.com/studio/build/configure-apk-splits

Please note that our resource files are architecture agnostic, so you need to optimize only .aar file in the lib folder.  

Still have questions? Let's discuss them here!