eCommerce
Restaurant
Grocery
Pickup & Delivery
Online Courses
Employee Communication
Content Creators
Bookings
Newspaper
Radio
Schools
Events
Travel guide
Faith
Organizations
Custom apps
PRODUCT RESOURCES
TOPICS
TECHNOLOGY
MOBILE APPS RESELLERS
DISCOVER
Updating Your GoodBarber App
Written by GoodBarber Team on
Oh no... you just submitted your app to the stores, and now you remember that you forgot to use the new CMS sound section after all! And going through all that trouble of submitting the app again?
You can breathe easy, since you don't need to! Only a handful of modifications require you to re-build your app and submit the update to the stores - and even something big like adding a content section isn't one of them!
You can breathe easy, since you don't need to! Only a handful of modifications require you to re-build your app and submit the update to the stores - and even something big like adding a content section isn't one of them!
On your smartphone, you very likely receive update notifications for the apps you've installed on a very regular basis. There's no doubt that keeping an app fresh and up to date is very important and crucial if you want to keep your audience interested. However, submitting updates to the stores can be time-consuming. That's why we've GoodBarber in such a way that keeps updates to the stores to a minimum. The easier it is to make any changes, the less reason you have not to make them... and the more your users are likely to remain loyal!
Update Without Leaving Your Backend
Whenever you make any changes to your application, they are not applied immediately right after you make them. They are first all recorded in the changelog, and are applied only when you want to. Doing so is a straightforward process in your backend, and can be done with only a few clicks. Simply go to Publish > Update > Changelog. There, you will see a list of all of the modifications you have undertaken since the last time you updated the application, sorted by date. If you want to know more about the modifications made on a specific day, simply click on "See the details".
You will notice that under the column "type" there are two different symbols with different colors accompanying the modifications in the log. Those that are besides the green smartphone icon are modifications that can be applied directly from the backend without needing to rebuild. The black cloud symbol, on the the other hand, indicates that the modification needs re-building and submission to the stores to become effective. Specifically, these are the three types of modifications that need re-building:
- The application's icon
- The application's splashscreen
- Any changes under Design > Options
This is what your backend looks like before updating. As you can see, there are seven modifications that can be applied right away, and one modification that needs re-building.
You will notice that under the column "type" there are two different symbols with different colors accompanying the modifications in the log. Those that are besides the green smartphone icon are modifications that can be applied directly from the backend without needing to rebuild. The black cloud symbol, on the the other hand, indicates that the modification needs re-building and submission to the stores to become effective. Specifically, these are the three types of modifications that need re-building:
- The application's icon
- The application's splashscreen
- Any changes under Design > Options
This is what your backend looks like before updating. As you can see, there are seven modifications that can be applied right away, and one modification that needs re-building.
In order to apply the modifications that can be applied immediately, i.e. those next to a green symbol, simply click first on the white "Update now" button, and then on the green "Update" button that will appear.
Now, whenever your users re-launch your application, they will automatically be using the modified version. In addition to keeping the update process simple for you, this has the added advantage that you needn't annoy users with the download of yet another update of your app!
This is what the changelog will look like after you've clicked on update. Of the formerly eight modifications, there is only one left: a modification made under Design > Options, next to the black cloud symbol, that will need re-building an re-submission to become active.
Now, whenever your users re-launch your application, they will automatically be using the modified version. In addition to keeping the update process simple for you, this has the added advantage that you needn't annoy users with the download of yet another update of your app!
This is what the changelog will look like after you've clicked on update. Of the formerly eight modifications, there is only one left: a modification made under Design > Options, next to the black cloud symbol, that will need re-building an re-submission to become active.
Here we go again...
If you took care of the submission process yourself, you'll already have some idea of what's awaiting your (we hope that doesn't scare you off too much). The process for submitting an update somewhat resembles that of a first submission, although it is considerably simpler.
You will of course also already have gone through the steps of creating your Developer Account with Apple and/or Publisher Account with Google. Just like with a first submission, the submission of an update also requires that you first build the app, and then submit it to the respective store. However, re-building the app is far simpler than building the app for the first time. This is because you already gave us all of the necessary information for building the app the first time around (for example the KeyStore, Package Name, Distribution Certificate, Push Certificate, etc.).
While re-building is therefore quite a bit simpler than building, the actual submission process to the stores is very similar to that of a first submission.
You will of course also already have gone through the steps of creating your Developer Account with Apple and/or Publisher Account with Google. Just like with a first submission, the submission of an update also requires that you first build the app, and then submit it to the respective store. However, re-building the app is far simpler than building the app for the first time. This is because you already gave us all of the necessary information for building the app the first time around (for example the KeyStore, Package Name, Distribution Certificate, Push Certificate, etc.).
While re-building is therefore quite a bit simpler than building, the actual submission process to the stores is very similar to that of a first submission.
Submitting an iOS Update
Let's start with the submission process for an iOS update.
When you submit an update for your iOS app, you will need to log on to your iTunes connect profile, where you will see a list of the apps you've published. If the app is currently published, you will see a small green dot next to the version number. Next to "Metadata and Uploads" you'll need to click on "Details", and then "Edit". You can then change the information you provide about you app in the stores, including the description and the screenshots. Be sure that the screenshots are up to date and correspond to the new version of your app! Also be aware that when you submit an update, it's mandatory to specify the changes.
When you're done, click on "save", and the status will change to "ready to upload binary". To upload the new binary (IPA) that you've just created in your backend, upload the binary through the software called Application loader (provided by Apple). You'll then see two versions of your application side-by-side on your iTunes connect account: the current version, with a green dot and the status "ready for sale" (the 1.0 version, for example) and the new version (1.1, in this case) with an orange dot and the status "Waiting for review". With Apple, you can also choose whether or not you want the new version to be automatically published after approval, or whether you prefer to publish it yourself. This review can take anywhere between 7 and 20 days. Just as with a first submission, your backend will be locked until the app has been downloaded by at least five users.
When you submit an update for your iOS app, you will need to log on to your iTunes connect profile, where you will see a list of the apps you've published. If the app is currently published, you will see a small green dot next to the version number. Next to "Metadata and Uploads" you'll need to click on "Details", and then "Edit". You can then change the information you provide about you app in the stores, including the description and the screenshots. Be sure that the screenshots are up to date and correspond to the new version of your app! Also be aware that when you submit an update, it's mandatory to specify the changes.
When you're done, click on "save", and the status will change to "ready to upload binary". To upload the new binary (IPA) that you've just created in your backend, upload the binary through the software called Application loader (provided by Apple). You'll then see two versions of your application side-by-side on your iTunes connect account: the current version, with a green dot and the status "ready for sale" (the 1.0 version, for example) and the new version (1.1, in this case) with an orange dot and the status "Waiting for review". With Apple, you can also choose whether or not you want the new version to be automatically published after approval, or whether you prefer to publish it yourself. This review can take anywhere between 7 and 20 days. Just as with a first submission, your backend will be locked until the app has been downloaded by at least five users.
Submitting an Update to Google Play
Just like with Apple, the process for submitting an updated application to Google Play is similar to that of a first submission. Log on to your Google Publisher Account and, and you'll see the list of your applications. Click on the one you want to update. Then, in the tab "APK" click on "Upload new APK to production". After you've uploaded your new APK, you can then specify what's new about the new version and make changes to the store listing and the pricing and distribution, if you wish. Then, just as with a new app, click on "Publish" in the top right-hand corner of the page. After review, which will take several hours, the old version will automatically be replaced with a new version.
While the new version of your app is under review, your users will simply continue to use the former version of your application. There will be no noticeable change for them until the new version is approved.
While the new version of your app is under review, your users will simply continue to use the former version of your application. There will be no noticeable change for them until the new version is approved.
We Can Take Care of it, too...
We understand that submitting updates can be time-consuming and probably isn't your favorite thing in the world to do. That's why we've designed GoodBarber in such a way that updates to the store are kept at a minimum, and you can apply the vast majority of updates with the click of a button from your backend. Remember that you needn't bother if your changes don't concern one of the three areas mentioned above!
However, even if you don't need to submit an update to the stores very often, keep in mind that if you decide to purchase the GoodBarber Takes Care option, we'll not only take care of the initial submission - we'll also take care of the submission of all subsequent updates to the stores. Over the (hopefully long) life of your app, that could still add up and potentially save you a good bit of time and hassle...
However, even if you don't need to submit an update to the stores very often, keep in mind that if you decide to purchase the GoodBarber Takes Care option, we'll not only take care of the initial submission - we'll also take care of the submission of all subsequent updates to the stores. Over the (hopefully long) life of your app, that could still add up and potentially save you a good bit of time and hassle...