How do I have several working versions of the same app with the same applicationId or package?

MIT App Inventor Help
7

I. This is and always has been my approach:
When I want to create a new app with the name "appName", I start with the first version, which means that it is named appName1_1. Then the 2nd version follows appName1_2 etc. (The first number is for the PlayStore version, the second is the development number.)

As a result, I am not forced to delete the previous version each time in AI2, but do it later for all together except for the last version (Play Store), e.g. appName1_v5. All versions up to the final version (App / Play Store version) are saved on the PC and in the cloud. The final version is then given the originally intended name "appName". After this version is published in the Play Store I remove it from AI2, because I already have this version in AI2 (the latest version → Play Store).

If updates need to be made for the Play Store later, I do the following:
Let's say I'm at release 47. The first version of the new release is given the name appName47_1, then appName47_2, etc. The final version of this update is then again given the name appName.

I've made more than 600 releases in the Play Store this way so far (all AIAs generated this way may be about 3000 - 4,000).

Note: If we could change / set the → packageName in AI2 (as is possible with Kodular) it would of course make things easier.

Possible question: Why do I split a release into versions?
Answer: For example, when a certain milestone has been reached or an essential part of the app has been completed and I first want to test whether the app (APK) works properly. This is followed by a new version with further optional features. I always want to know which version I can revert to that worked flawlessly. But there are other reasons that have emerged after my seven years of experience with App Inventor.

II. PackageName and updating an app:
To be able to update an app in the Play Store, three requirements must be met:

  1. The same packageName is used as for the first release.
  2. The keystore must be identical
  3. The app version number must be higher than the current app version

Changing the packageName afterwards is not that easy. I've done it several times. You have to proceed very carefully, otherwise the app will be unusable afterwards and a crash will occur.

1 Like
Change app logo