AAB is a new publishing format used to upload mobile apps to Google Playstore. This format includes all your app’s compiled code and resources, and defers APK generation and signing to Google Play. AAB is used to optimize the size of your mobile app, by allowing users to download the required assets or files based on their device specifications.
In Creator, we now support two file types for Android:
There are two different keystore files required to generate the appropriate file types:
This is the second-level keystore file used to identify the developers who are responsible for their published apps. Users have to create this keystore file and use it while generating AAB. Learn how to generate upload keystore file
This is the main keystore file used to sign a mobile app to install them in your mobile and tablet devices. Users have to create this keystore file and use it while generating APK. Learn how to generate app signing keystore file
You can codesign your Android apps using either of the below file types.
For example,
Once AAB is generated, we can easily generate APK from it by using the App Signing keystore details.
To generate APK from AAB,
The .apk file will be generated and you can share it with your users.
For example,
You can also code-sign your mobile apps using both the AAB and APK file types.
For example,
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
Write to us:
support@zohoforms.com