If you need to update the native features of your website-based app (like changing the app icon, adding push notifications, or changing the splash screen), you must generate a new AAB file and submit it to the Google Play Store as an update.
However, the Play Store will reject your new file if it is not versioned correctly.
In this guide, we will explain the difference between the two types of Android versions—Version Code and Version Name—and how to set them correctly when updating your app.
The Two Types of Android Versions
When you look at the settings inside an online website-to-app converter, you will usually see two fields related to versioning. They serve very different purposes.
1. The Version Name (The Public Version)
The Version Name is a string of text that is shown to the public on your Google Play Store listing.
It is used to tell your users what release they are downloading. You can technically write whatever you want here, but the industry standard is to use semantic versioning (e.g., 1.0.0).
1.0.0(Major release . Minor feature . Bug fix)- If you change your logo, you might update the Version Name to
1.1.0. - If you completely rebuild the app, you might update it to
2.0.0.
Google's Rule: Google does not care what you put here, as long as it helps the user understand the release.
2. The Version Code (The Private Version)
The Version Code is a hidden integer (a whole number) used exclusively by the Android operating system and the Google Play Store to determine which version is the newest.
Users never see the Version Code.
Google's Rule: The new Version Code must always be higher than the previous one. If your last upload had a Version Code of 4, your next upload must be 5 (or 6, or 100). If you try to upload a file with a Version Code of 4 or lower, Google will reject it, stating that you cannot downgrade an app.
How to Version Your App During an Update
When you need to generate a new APK or AAB to update your native features, follow this simple process:
- Check Your Current Version: Log into your Google Play Console, click on your app, and look at your current Production release. Note the Version Code that is currently live. (Let's assume the live Version Code is
1and the Version Name is1.0.0). - Open Your Converter: Go to your online web-to-app converter's dashboard.
- Increment the Version Code: Find the "Version Code" field and change it from
1to2. - Increment the Version Name: Find the "Version Name" field and change it from
1.0.0to1.1.0(or1.0.1if it is a tiny change). - Generate: Click the button to build your new AAB file.
When you upload this new AAB to the Play Store, Google will see that Version Code 2 is mathematically higher than Version Code 1, and it will accept the file as a valid update.
A Reminder About Content Updates
Remember, you do not need to generate a new version of your app if you are just changing content on your website!
Because your app is a WebView, any changes to your website (like new products, blog posts, or CSS colors) will automatically appear in the app the next time the user opens it. You only need to deal with Version Codes when you are changing the app's native shell (icons, names, or loading screens).
Conclusion
Versioning an Android app is a simple numerical progression. Keep your public Version Name logical for your users, and always ensure your hidden Version Code increases by at least one whole number with every new upload.