How We Can Publish Your New App as an Update

We regularly help customers - that already have an app - switch to an app created by us. There can be many reasons for this. The most common ones we hear are:

• the existing app is outdated
• the existing app contains bugs that can't easily be fixed
• they no longer want to separately maintain both their website and app

It's always great if you let us know what your reason is, so we can make sure that we can fulfill your expectations.

How it works

Android (Google Play Store etc.)

To publish your app as an update, the new app needs to have the same digital signature as the old app. For that, you will need the following information:

• Your keystore. Usually a file with the file type .jks
• Your key password (keypass)
• Your keystore password (storepass)
• Your key alias

Once you have all of that, you can send it to us, so we can sign the app for you. If you'd rather sign your app yourself, see our guide on signing app bundles yourself. You can skip the section about generating keys, as you need to use your existing ones.

Apple App Store

To publish your new app as an update in the Apple App Store, you need to invite us to your existing Apple Developer Account.

Depending on the account type and other individual circumstances, we might need more information from you. We will let you know if that's the case.