Examples of using Version codes in English and their translations into Indonesian
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Ecclesiastic
All of the cars except for the first have unique version codes.
This scheme for version codes is just a suggestion for how you should establish a pattern that is scalable as your application evolves.
Android has version names and version codes.
For example,when the application version name is 3.1.0, version codes for an API level 4 APK and an API level 11 APK would be something like 0400310 and 1100310, respectively.
Because the screen sizesoverlap(both APKs support large screens), the version codes must still be in order.
In this case,the API level is the only supported filter used, so the version codes must increase in correlation with the API level support for each APK, so that users get an update when they receive a system update.
If you have one APK that's for API level 16(and above) and ARMv7 CPUs, and another APK for API level 21(and above) and ARMv5TE CPUs,then the version codes must increase in correlation with the API levels.
You must be careful about assigning version codes when publishing multiple APKs, because they must each be different, but in some cases, must or should be defined in a specific order, based on the configurations that each APK supports.
The recommended one can be found on the Version Codes area of our developer guide.
A suggested scheme for your version codes, using the first two digits for the API Level, the second and third digits for the minimum and maximum screen size(1- 4 indicating each of the four sizes) or to denote the texture formats and the last three digits for the app version. .
If you have one APK that's for API level 16(and above) and small- large screens, and another APK for API level 21(and above) and large- xlarge screens,then the version codes must increase in correlation with the API levels.
You can use any scheme you want, but you should carefully consider how futureversions of your application will need to increase their version codes and how devices can receive updates when either the device configuration changes(for example, due to a system update) or when you modify the configuration support for one or several of the APKs.
If you have one APK that's for API level 16(and above) and small- normal screens, and another APK for API level 21(and above) and large- xlarge screens,then the version codes do not need to increase in correlation with the API levels.
In order to allow different APKs to update their version codes independent of others(for example, when you fix a bug in only one APK, so don't need to update all APKs),you should use a scheme for your version codes that provides sufficient room between each APK so that you can increase the code in one without requiring an increase in others.
Because a device receives the APK with the highest version code when there is an overlap in coverage between two APKs,you should order the version codes among your APKs so that the APK with the preferred compression format has the highest version code. .
Note: The size of the version code increase is irrelevant;
Le last two letters stand for the MIUI version code mounted on the device.
Note: When you increase the version code for an APK, Google Play will prompt users of the previous version to update the application.
As such, the version code for the APK that supports API level 21 and above must be higher.
You cannot activate a new APK that has a version code lower than that of the APK it's replacing.
Thus, to avoid unnecessary updates, you should not increase the version code for APKs that do not actually include changes.
Armadillo is basically the version code name for Fuchsia, which is the operating system- kind of like Nougat, which is the version name, for the OS known as Android.
We suggest using a version code with at least 7 digits: integers that represent the supported configurations are in the higher order bits, and the version name(from android: versionName) is in the lower order bits.
That way, a normal size device will receive theappropriate update when you make the change, because the version code increases from the existing APK to the new APK that now supports the device.
For example, say you have an active APK for screen sizes small-normal with version code 0400, then try to replace it with an APK for the same screen sizes with version code 0300.
This ensures that if a device receives a system update that then qualifies it to install the APK for higher API levels,the device receives an application update because the version code increases.
This ensures that when a device receives a system update, Google Play can offer the user an update for your application(becauseupdates are based on an increase in the app version code).
This is important because a user's device receives anapplication update from Google Play only if the version code for the APK on Google Play is higher than the version code of the APK currently on the device.
For example, if you have different APKs based on screen size, such as one for small- normal and one for large- xlarge, but foresee a time when you will change the APKs to be one for small and one for normal- xlarge,then you should make the version code for the large- xlarge APK be higher.