When would you replace an app instead of launching a new app?
You have an existing app and you want to replace it with a new app built with Fliplet
You have an existing app produced with an old version of Fliplet and you want to replace it with an app build in a new version of Fliplet
- If you have created a new version of the app in Fliplet to replace the existing app
The benefit of replacing an app instead of launching a new app:
The user receives the new app automatically, they do not need to install a new app from the app store manually and delete the old app
The app keeps its existing users as they do not have to be requested to take additional steps to install the new app
You can still send notifications to the existing users as the push subscription data from each user can be used by the new app
You can keep the existing user data, if applicable
When replacing an app, there are a few steps that must be followed:
The app must be signed with the same Apple or Google account
The app identifier / bundle must be the same
The version number must be higher than the existing app
After the new app goes live, all push tokens must be migrated from the existing Fliplet app to the new app
Add the existing analytics software tracking tags, such as Google Analytics
Below are the instructions for each of these steps.
1. The app must be signed with the same App Store or Google Play account
You can ensure you are submitting the app using the account by checking the developer account the current app came from.
If you are replacing your app with an app from Fliplet Studio version 1, please contact Fliplet to confirm your app’s details.
If it is incorrect the app will appear as a new app on the app store.
2. The app identifier / bundle must be the same
To confirm the identifier/bundle access the existing app information and check it’s bundle ID. It will be something like com . organisation .app-name for example, com.Fliplet .FlipletViewer.
If you are using the latest version of Fliplet Studio, follow the following instructions. If you are replacing your app with an app from Fliplet Studio version 1, please contact Fliplet to confirm your app’s details.
Go to Publish –> Publish to Apple devices –> App technical details –> Bundle ID
If the identifier doesn’t match perfectly the device and app store will not know to replace the existing app and the user will not receive the update.
3. The version number must be higher than the existing app
If the version number is the same or lower the app store will not accept the app and the device will not install the update automatically as the device will think it already has the app.
You can see the current version number of looking at the app’s details on your device or at the version information on the app store.
4. After the new app goes live, all push tokens must be migrated from the existing Fliplet app to the new app
If you do not migrate user’s push tokens you will not be able to send them push notifications. To complete this step file a support ticket with Fliplet at firstname.lastname@example.org and we can process this request for you.
5. Add the existing analytics software tracking tags, such as Google Analytics
If you do not use the existing analytics settings, analytics data will not be tracked or it will appear in a new analytics account meaning you cannot assess historic usage data for you app before the upgrade.
If you have any questions about replacing your app, contact Fliplet and we can advise you on the steps you need to take and how to take them.