Publicly distributed apps
Summarize
Summary of Publicly Distributed Apps
This guide covers the process for distributing branded iOS and Android applications through public app stores. It highlights the timeline and steps involved in requesting and deploying these apps using ServiceNow's Mobile Publishing feature.
Show less
Key Features
- Simultaneous Delivery: When requesting both iOS and Android apps, all builds are delivered at the same time within a one-week timeline.
- Expedited Testing: To speed up delivery, it is recommended to test the Android app first while the iOS app is being built, using existing mobile apps from the ServiceNow Store.
- Branding Compliance: Both iOS and Android apps adhere to the branding guidelines set by Apple and Google, respectively.
- Request Process: Complete the branded app request form in Mobile Publishing to initiate the build for both platforms.
Key Outcomes
For iOS apps, after submitting the request, you will receive an XCode archive file (.xcarchive) to update and re-sign, generating an iOS application archive file (.ipa) for testing and deployment on the Apple Store. This process typically takes about one week.
For Android apps, after completing the request, you will receive an Android App Bundle file (.aab). Following successful testing, you can approve the build for deployment on the Google Play Store, usually taking about a week or even a few hours.
Public distribution can be used to distribute iOS or Android branded applications on public app stores.
- If you select iOS & Android as your Operating System (OS) when you request your branded mobile app, all builds are delivered to you at the same time. This means that both your Android and iOS apps are delivered to you within the publicly distributed iOS delivery timeline of 1 week.
- If you have an implementation date deadline within days, it's suggested that you request the Android app first, test it, and approve its branding. Then submit your iOS app request.
- Another way to expedite delivery of your branded app is to test the mobile workflows and functions using the mobile apps that are available on the ServiceNow® Store while your branded app is being built. Your branded app uses all the same workflows and mobile app functions as the apps that are available on the ServiceNow Store. Then when your branded app is available, you only need to test the branding, the login flow for pre-filled instance URLs, push notifications, and the app store listings.
iOS branded apps for public distribution
The ServiceNow® branding program complies with the suggested practices from Apple for branded app releases. Mobile Publishing enables you to request a branded iOS app that can be distributed on the public Apple Store. After you complete the request form, your ServiceNow instance builds the app and provides a link from where you can download an XCode archive file (.xcarchive). Then you download the XCode archive file, update it, and re-sign it to generate an iOS application archive file (.ipa). After the .ipa file is generated, you upload it to Apple Connect for testing. When testing is completed, you approve the build and can deploy your branded app with the public Apple Store.
Android branded apps for public distribution
The ServiceNow branding program also complies with the suggested practices from Google for branded app releases. Use Mobile Publishing to request a branded Android app that you can upload and distribute with the Google Play Store. After you complete the branded app request form in Mobile Publishing, your ServiceNow instance builds the app. Then it provides a link from where you can download an Android App Bundle file (.aab). Download the AAB file and test it. If the tests are successful, you approve the build and can deploy your app with the Google Play Store.