cloudflare DNS IP
Budget: $30 – $250 USD
On changing the backend cloudflare DNS IP by making copy of backend server, when DNS IP is changed then associated mobile app with server is showing errors and stopped working. To make it work we need to uninstall and install the app again, if app is installed as update it is not working. Need to find a solution for this scenario where app will be installed as an update to older app and after changing the DNS IP with same server backend, app should work properly
Deployed on AWS EC2 Technology and backend is node js and php.
1. Using Guls existing bundle id in app store and playstore by pushing new technology of Captain codes and the brand name change in to Captain.
Example is, the existing customers who has Guls app in their phone, just open the app it should go as an update and replacing the Guls in to Captain app. Without another hassle.
Our technical team suggestion of this change, we push the code of Captain in both app store and play store. We change the brand name from Guls to Captain and the required screenshots and other details. So the app become Captain here. The existing Captain app in app store and play store we will remove the same before pushing the code to avoid any issue raise from the app store and play store.
2. Just pointing the customers to the existing captain app in app store and playstore, to use the app as an update
Example is, the existing customers who has Guls app in their phone, just open the app it should go as an update and replacing the Guls in to Captain app. Without another hassle.
For these, how we manage both backend and the playstore and app store code push also.
both the apps are live in app store and play store. We don’t any sensitive issue with app store and play store. The migration should be smooth and easy. There could be minimum downtime.
Gus-App store https://apps.apple.com/us/app/guls-%D9%82%D9%84%D8%B5/id1396948609
Guls – Play Store https://play.google.com/store/apps/details?id=com.guls.passenger
Captain – App store https://apps.apple.com/us/app/captain-%D9%83%D8%A7%D8%A8%D8%AA%D9%86/id1639088529
Captain - Playstore https://play.google.com/store/apps/details?id=com.captain.customerapp
Deployed on AWS EC2 Technology and backend is node js and php.
1. Using Guls existing bundle id in app store and playstore by pushing new technology of Captain codes and the brand name change in to Captain.
Example is, the existing customers who has Guls app in their phone, just open the app it should go as an update and replacing the Guls in to Captain app. Without another hassle.
Our technical team suggestion of this change, we push the code of Captain in both app store and play store. We change the brand name from Guls to Captain and the required screenshots and other details. So the app become Captain here. The existing Captain app in app store and play store we will remove the same before pushing the code to avoid any issue raise from the app store and play store.
2. Just pointing the customers to the existing captain app in app store and playstore, to use the app as an update
Example is, the existing customers who has Guls app in their phone, just open the app it should go as an update and replacing the Guls in to Captain app. Without another hassle.
For these, how we manage both backend and the playstore and app store code push also.
both the apps are live in app store and play store. We don’t any sensitive issue with app store and play store. The migration should be smooth and easy. There could be minimum downtime.
Gus-App store https://apps.apple.com/us/app/guls-%D9%82%D9%84%D8%B5/id1396948609
Guls – Play Store https://play.google.com/store/apps/details?id=com.guls.passenger
Captain – App store https://apps.apple.com/us/app/captain-%D9%83%D8%A7%D8%A8%D8%AA%D9%86/id1639088529
Captain - Playstore https://play.google.com/store/apps/details?id=com.captain.customerapp