---
sourceDocument: Zurich Mobile Configuration and Navigation
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/mobile

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Test and publish a new branded Android app for private distribution

# Test and publish a new branded Android app for private distribution {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Test and publish a new branded Android app for private distribution

This guide outlines the essential steps ServiceNow customers need to follow to test, configure, approve, customize, publish, and maintain a new branded Android app intended for private distribution.
It ensures your mobile app aligns with branding requirements and integrates properly with your instance and notification services before distribution.
Show full answer Show less  

## Test the app

After your app build completes successfully, download the Android APK file from the Request details page in Mobile Publishing. Distribute this APK to testers via email so they can install it on Android devices or emulators. Verify the app's branding elements---including name, icon, splash screen, and theme---are correct, and confirm that the login instance, EULA, and privacy policies appear as specified. Use the same APK file for deployment as for testing.

## Set up the app

Once testing is successful, optionally configure additional settings to enhance app functionality:

* Set up push notifications by adding your Google Firebase Cloud Messaging OAuth token to the app's push application record.
* Test push notifications using provided tools.
* Configure deep links by setting up an `assetlinks.json` file on each instance.

## Approve or reject the app

You have 90 days after the app status is set to "Ready for testing" to review it:

* Reject the app if branding or configuration changes are needed, then duplicate the request to modify and resubmit.
* Approve the build to proceed with publishing to end users.

## Customize your app's workflows

Use Mobile App Builder to tailor the app's workflows according to your organization's requirements before publishing.

## Publish and distribute your app

After testing, setup, and customization, upload your APK to your chosen private distribution channel, such as:

* Managed Google Play Console
* BlackBerry Portal (for BlackBerry MAM users)
* Microsoft Intune (syncing from Google Play)

Follow the respective platform documentation for publishing procedures.

## Keep your app updated

Regularly update your app, ideally before updating your ServiceNow platform version or at least annually, to maintain push notification functionality and access the latest mobile features supported by ServiceNow.  
Learn the next steps to test and publish a new branded Android app for private distribution after you request it in Mobile Publishing.

## 1. Test the app {#testpubnu-andapp-privdist__section_d3y_pw1_j2c}

After the build successfully completes and your app is ready for testing:

1. Navigate to the Request details page by selecting AllMobile BrandingManage Mobile Publishing AppsYour recent app requests.
2. Select the card for your mobile app build request. The Request details page appears.
3. Select the Android testing file link and the APK file is downloaded to your local system for testing:

4. Send the APK file to your testers via email so they can open the file on their Android device or in an emulator.

   See [KB0727776](https://support.servicenow.com/nav_to.do?uri=/kb?id=kb_article_view&sys_kb_id=2f6ebf4047e7c250b7832920326d4347) for information about how to install a mobile simulator and APK file on your computer so you can test the Android testing file.
5. Check the following items on your app:
   * App has the correct name, icon, splash screen, branding, and theming. For more information, see [Create a theme with Theme Builder](https://www.servicenow.com/docs/access?context=tb-create-theme&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US).
   * App uses the default instance you specified for login if you selected the instance pre-fill option when you requested the branded app.
   * EULA and privacy policy listed in the mobile app Settings tab under Legal link to the policies you specified.

   {#testpubnu-andapp-privdist__ul_bm5_jy1_j2c}  
   Important:  
   The APK file that was used during testing should also be used for deployment.
{#testpubnu-andapp-privdist__ol_x2f_tw1_j2c}

## 2. Set up the app {#testpubnu-andapp-privdist__section_ozd_ry1_j2c}

After testing completes successfully, you can set up your app for use. These configurations are optional.

1. Set up push notifications by adding your Google
   Firebase Cloud Messaging HTTPv1 Oauth token to your app type's push application record.

   See [KB1639289](https://support.servicenow.com/nav_to.do?uri=/kb?id=kb_article_view&sys_kb_id=68456c07471d86d030fba325126d43e5) for detailed instructions.
2. Test push notifications using an out-of-the-box push notification.

   See [KB0829093](https://support.servicenow.com/kb?id=kb_article_view&sys_kb_id=b5e4111cdba5d010feb1a851ca961909) for detailed instructions.
3. Set up deep links for your app by configuring an `assetlinks.json` file on each instance.

   See [KB1648690](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1648690) for detailed instructions.
{#testpubnu-andapp-privdist__ol_hjv_5y1_j2c}

## 3. Approve or reject the app {#testpubnu-andapp-privdist__section_mw4_h1b_j2c}

Once the status of your app is Ready for testing, you have 90 days to make sure the app meets your branding requirements:

* Reject the app to edit the branding, app name, app type, or any third-party information. Use the Duplicate option to copy information over to a new app request after you have rejected the app.
* Approve the build to move forward with publishing the app to your end users.
{#testpubnu-andapp-privdist__ul_rz1_l1b_j2c}

## 4. Customize your app's workflows {#testpubnu-andapp-privdist__section_fpt_s1b_j2c}

Use Mobile App Builder to customize your app. See [Mobile App Builder](https://www.servicenow.com/docs/n8gATw84q~Lhhm1j9E57dw "The ServiceNow Mobile App Builder (MAB) is a configuration tool to build and manage screens and records that make up workflows within ServiceNow mobile apps. The organizational layout and navigation options in the Mobile App Builder facilitate a faster and more intuitive creation of ServiceNow mobile applications.") for detailed information about how you can customize your branded app.

## 5. Publish and distribute your app {#testpubnu-andapp-privdist__section_wf1_1bb_j2c}

After you have tested your app, set it up, and customize its workflows, you are ready to publish your branded Android app for private distribution. Upload your APK file to your private distribution site, the managed Google Play Console, or your enterprise mobility management (EMM) provider:

Google Play Console:
:   To publish your private branded Android app from the Google Play Console, see [Google documentation](https://support.google.com/a/answer/2494992?hl=en).

BlackBerry Portal:
:   To publish your private branded Android app to the BlackBerry Portal if you are using BlackBerry mobile application management (MAM), see [KB0813295](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0813295).

Microsoft Intune:
:   To sync your private branded Android app from Google to Microsoft Intune, see [Microsoft documentation](https://learn.microsoft.com/en-us/mem/intune/apps/apps-add-android-for-work).

## 6. Keep your app updated {#testpubnu-andapp-privdist__section_yjg_1db_j2c}

Update your app before you update your ServiceNow® family version, or at least once per year to keep your push notifications working and to leverage the most up to date ServiceNow mobile features. For more information, see [Tested devices and supported versions for ServiceNow mobile apps](https://www.servicenow.com/docs/8xzlmQx~rHrHGUiij8jPXg "Use the following information to verify that your mobile devices and operating systems are ready to use ServiceNow mobile apps.").

*[\>]: and then