Packaging the Application for Stores

Use the ‘Store Information’ page to make sure you have collected the appropriate material for publishing to stores. When you are ready to publish to one or both App Stores, go to the Umajin App Creator (enter your credentials if needed) then select the application that you want to publish.

When the application has loaded into the Editor, click the Publish button.  Next, you can choose the way you want to publish your app.

In this section, we will be talking about the Publish to App Stores option in detail.

When publishing to App Stores, you will need to provide screenshots, marketing images and information for presentation on their Product pages.  Some of the images needed can be generated for you by the Umajin App Creator.  After you select Publish to App Stores, you are presented with a settings screen which will need to be completed before proceeding to the publish system using the Cloud Service.

The Android and iOS icons and the Android banner image must be exactly the right format and size.  The iOS documentation has very specific guidelines for their icons and other design elements which are documented at the following link: https://developer.apple.com/ios/human-interface-guidelines/graphics/

Note: These (and other) store requirements may change over time. It is up to you to stay current with respect to the requirements and their impact on acceptance through the submission process.

The Screenshots and the Launch Image are generated from the pages within your application so you should choose these from the list of pages in your app.  If you want to stylize a page, exclusively as a marketing screenshot for the Stores, just create a page in the app which is not hooked up to any navigation and add the elements required.  You must make sure that the page is responsive to size changes – as the screenshots that are produced are automatically resized for the various device size requirements of the Stores when created – you can use the Devices dropdown in the main editor window to determine resizing states.

Once you finish selecting the images and entering the information on this page, click ‘Next’ and your images will be exported for publishing.  Along with the images, the app is readied for publishing.

The above dialog indicates that the process can proceed to the online portion of the publishing process. Clicking the OK button will open your default browser and direct you to the publishing page online.

Here, you will first select the target platform(s).  You can publish on either Apple, Android or both platforms.  You will need to enter the information that you gathered in the ‘Information for Publishing to Stores’ section of this guide.

Apple iOS Information

In the Apple iOS section, you are presented with input fields for the information that you have collected in the Apple section of the ‘Information for Publishing to Stores’ section of this guide.

You need to add the following (use the checklist as a guide):

  1. App Name – this will be filled out already, it must be the same as the name in the Store information you submitted to the Apple developer site.
  2. Reverse URL – enter the Reverse URL that you submitted to the Apple developer site. It is usually com.<yourcompanyname>.<theappname> unless there is already an app on the store with the same reverse URL.
  3. The Version of the app – this will be automatically filled in for you and should not be changed unless this app is replacing an app of the same name/cert on the store. If that is the case then the version needs to be greater than the last version of the app it is replacing.
  4. Google Map iOS Key – if you have a Google Map component in your application then you will need to apply for a Google Maps API key and enter it correctly in this form field. To apply for a Google Map API Key, go to https://developers.google.com/maps/documentation/android-api/signup
  5. Code Sign Certificate – Pick the certificate (p12) that you attained through the Apple Developer site and it will be uploaded for publishing.
  6. Code Sign Password – Enter the password that you assigned to the certificate in the Apple Developer site.
  7. Apple Push Certificate – If you wish to send push notifications to users of your app then you need the Apple Push Certificate. If you don’t then leave this empty.
  8. Apple Push Password – Enter the password that you assigned to the Apple Push certificate above.
  9. Distribution Provision Profile – Add the provisioning profile (<appname>.mobileprovision) that you attained from the Apple developer site.
  10. Ad-hoc Provision Profile – If you indicated an Ad-hoc provision in the Apple developer site then add the provision file here.
  11. Device Family Targeting – here you can indicate whether you want your app to be available to iPhones, iPads or both. Note: your app will only show in the App Store of the family group you choose.  If you want your app to be available to all iOS devices then choose ‘Both iPhone/iPad’ in this option list.
  12. Click ‘next’ to progress through the publishing process.

Android Information

In the Android section, you are presented with input fields for the information that you have collected in the Android section of the ‘Information for Publishing to Stores’ section of this guide.

Add the following (use the checklist as a guide):

  1. App Name – this will be filled out already, it must be the same as the name in the Store information you submitted to the Apple developer site.
  2. Reverse URL – enter the Reverse URL that you submitted to the Apple developer site. It is usually com.<yourcompanyname>.<theappname> unless there is already an app on the store with the same reverse URL.
  3. The Version of the app – this will be automatically filled in for you and should not be changed unless this app is replacing an app of the same name/cert on the store. If that is the case then the version needs to be greater than the last version of the app it is replacing.
  4. The Android Keystore Alias that you used in the keystore file creation step (e.g. app_alias in the example in the ‘Information for Publishing to Stores’ section)
  5. GCM SenderID/ProjectID – Enter the ProjectID that you discovered from creating the Android project.
  6. Code Sign KeyStore – Pick the keystore file (e.g. keystore) to upload for this app.
  7. Code Sign Password – Enter the password that you assigned to the above KeyStore here.
  8. GCM Browser Key
  9. GoogleMaps Android Key – if you have a Google Map component in your application then you will need to apply for a Google Maps API key and enter it correctly in this form field. To apply for a Google Map API Key, go to https://developers.google.com/maps/documentation/android-api/signup
  10. Click ‘next’ to progress through the publishing process.

Payment for Publishing

The next step will be to pick a payment period from the options available.  Umajin App Creator requires pre-payment for publishing your app.  You can pick either a recurring monthly or annual fee depending on your need.  App developers and Enterprise users should contact us for more information about pricing details.

After you have chosen a payment option, you are asked to confirm your information and are then sent to a PayPal screen to enter your details for payment.  This is the last step in the process for publishing.

What happens next?

Our build servers will then build your app with the relevant information you have given us and report back the result.  This will either be a link to the package(s) for Store deployment or a failure notice.  This process can take some time, so in the meantime, you should add all the marketing information for your store submission into the respective Store Developer sites, if you haven’t completed it already.