---
title: Request a new branded Android app for public distribution
description: Request, test, and publish a custom Android app that has your unique company identity. Then make the app available for public distribution on the Google Play Store.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/mobile/request-public-branded-android-app.html
release: australia
topic_type: task
last_updated: "2026-08-20"
reading_time_minutes: 11
breadcrumb: [Request, test, & publish, Custom branded apps, Configuring the Mobile Platform, Mobile Platform]
---

# Request a new branded Android app for public distribution

Request, test, and publish a custom Android app that has your unique company identity. Then make the app available for public distribution on the Google Play Store.

## Before you begin

Role required: admin

## About this task

Mobile Publishing enables you to request a branded Android app that can be distributed on the public Google Play Store. After you complete the request form, your ServiceNow® instance builds the app and provides a link from where you can download an Android App Bundle file \(`.aab`\). Then you download the AAB file and test it. When testing completes successfully, you approve the build and can deploy your branded Android app with the public Google Play Store. For information about AAB files, see the [Google documentation](https://developer.android.com/guide/app-bundle).

If you provided a developer verification snippet, a signed Android Package file \(`.apk`\) containing the snippet is also made available for download alongside the AAB file.

**Note:** Publicly distributed Android app builds take one week from submission to be ready for testing. ServiceNow can't expedite this timeline because it's determined by Google.

Ensure that the images or text in the icons are at least 550 pixels from the edge. This distance accounts for the rounded corners in Android icons.

\[Omitted image "logo-padding.png"\] Alt text: Ensure logos are 550 pixels from the edge of the image to avoid a cut off appearance.

Images that do not follow this guideline may appear cut off, as shown in this example.

\[Omitted image "cut-off-icon.png"\] Alt text: Example icon with cut off logo and text.

## Procedure

1.  Navigate to **All** > **Mobile Branding** > **Manage Mobile Publishing Apps**.

2.  Select **Request a new app**.

3.  On the Add basic info form, fill in the fields.

<table id="table_gw4_d1t_lrb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Your contact info

</td><td>

Enter the name and email address for the requester of the branded mobile app. The email address is used to send notifications about the build status of your request.

</td></tr><tr><td colspan="2">

**Your app's info**

</td></tr><tr><td>

App type

</td><td>

Select either **Now Mobile app** or **Mobile Agent**.

 For more information about these mobile apps, see [Now Mobile app](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/now-mobile-app.md) or [Mobile Agent app](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/mobile-experience.md) documentation.

 In the Washington DC release and later, select customers can use custom app types. For more information, see [Create custom-type mobile apps with Mobile Publishing](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/mob-pub-about-custom-apps.md).

</td></tr><tr><td>

Distribution type

</td><td>

Type of distribution. Select **Public**, and then select **Accept** in the Public distribution terms and conditions dialog box.

</td></tr><tr><td>

Operating System \(OS\)

</td><td>

Mobile operating system for your mobile app. Select **Android only**.

 If you need to brand mobile apps for both operating systems, select **iOS and Android**.

</td></tr></tbody>
</table>4.  Select **Next**.

5.  On the Add app details form, fill in the fields.

<table id="table_rlm_2gs_d1c"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Short name

</td><td>

Name of the app icon. The name can't exceed 13 characters. This name displays below the app icon on mobile devices.

</td></tr><tr><td>

Package name

</td><td>

Based on what you entered for the app name and app type, this field auto-populates with the package name.

 You can select the copy icon \(\[Omitted image "mob-pub-copy-icon.png"\] Alt text: Copy icon\) to copy this name to your system clipboard.

</td></tr><tr><td>

Mobile Application Management \(MAM\)

</td><td>

Whether you want to use a MAM vendor with your apps. For more information, see [Mobile application management \(MAM\) integration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/sg-mam.md).

 To enable a MAM vendor, select the **Use Mobile Application Management** toggle.

</td></tr><tr><td>

Mobile Application Management vendor

</td><td>

Select the **Intune** MAM vendor form the list:

 This field is only visible if you select the **Mobile Application Management \(MAM\)** toggle.

</td></tr><tr><td>

End-user license agreement

 \(EULA\) and privacy policy

</td><td>

EULA and privacy policy options.

 Select the toggle **Use ServiceNow's EULA and privacy policy** to turn on the default EULA and privacy policy.

</td></tr><tr><td>

EULA

</td><td>

URL where app users can view your custom end user license agreement from the mobile app settings. This option only displays when you do not select to use the default ServiceNow EULA.

</td></tr><tr><td>

Privacy policy

</td><td>

URL where app users can view your custom privacy policy from the mobile app settings. This option only displays when you do not select to use the default ServiceNow privacy policy.

</td></tr><tr><td>

Instances used for deep links**Note:** If you selected **iOS and Android** for your **Operating System** in the **Add basic info** form, this configuration section is named **Deep links and Universal links**. For more information about universal links, see [Universal linking for mobile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/universal-links-mobile.md).

</td><td>

This table shows all ServiceNow instances used for your organization. Select the instance URLs that you want to be built into your app as a deep link.

 If you need to configure a deep link to a URL that isn't listed in the table, select **Add custom URL**, enter the URL, and then it's added to the table for selection.

 **Note:** Deep links can only be edited when you submit a new branded app request or when you update a branded app.

 To learn more about mobile deep links, see [Deep linking for mobile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/deep-link-mobile.md).

</td></tr><tr><td colspan="2">

**Login management**

</td></tr><tr><td>

Pre-populate instance

</td><td>

Turn on this toggle to build an instance URL into your branded app so end-users don't need to type the instance URL during login. Instead they only need to provide their login credentials. Enter a default app instance URL that is secure and uses Hypertext Transfer Protocol Secure \(https://\).

 **Note:**

-   This instance URL can only be added when you submit a new branded app request or when you update a branded app.
-   Do not select this option if you are using AppConfig to pre-configure a default instance URL through an EMM suite or an embedded MAM SDK app. For more information, see [AppConfig for Mobile Apps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/appconfig.md).


</td></tr><tr><td>

Default app instance

</td><td>

Enter the secure default app instance URL.

 This field is only visible if you select the **Pre-populate instance** toggle.

</td></tr><tr><td>

Nickname

</td><td>

\(Optional\) Enter a nickname for the **Default app instance** URL that displays on the mobile app for your end-users.

 This field is only visible if you select the **Pre-populate instance** toggle.

</td></tr></tbody>
</table>6.  Select **Next**.

7.  If you selected **iOS and Android** in the **Operating System** field on the **Add basic info** form in Step 3 above, see Step 7 in [Request a new branded iOS app for public distribution](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/request-public-branded-ios-app.md) for information about filling out the **Set up for iOS** form.

    After you complete the optional iOS configuration, return to Step 8 in this topic to complete your request for a public branded Android app.

8.  On the Set up for Android form, fill in the fields.

<table id="table_gmt_5hs_d1c"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td colspan="2">

**Google account**

</td></tr><tr><td>

Firebase app ID

</td><td>

App ID of the Android app in your Google Firebase project. The ID is the unique identifier for the Firebase app across all Firebase projects. App IDs always contain the string `name :android:` within the ID.

 **Note:**

-   Each Firebase app ID is unique to the branded app request. If you request multiple apps, each app must have its own unique Firebase app ID.
-   The package name of the branded app defaults to `com.servicenow.b2b.<*app\_name\_long\_no\_spaces*>.<*client\_type*>`.
 For more information, see the [Google Firebase documentation](https://firebase.google.com).

</td></tr><tr><td>

Firebase API key

</td><td>

API key of the Android app in your Google Firebase project. This key is a string that is used when calling Firebase APIs. For more information, see the [Google Firebase documentation](https://firebase.google.com).

</td></tr><tr><td>

Firebase project ID

</td><td>

ID of the Google Firebase project. This is a user-assigned unique identifier for your Firebase project. For more information, see the [Google Firebase documentation](https://firebase.google.com).

</td></tr><tr><td>

Opt-in to trust user-added certificate authorities

</td><td>

Option that enables you to opt in your app to the trusted user-added certificate authority \(CA\). By default, apps that target API level 24 don't honor user supplied CAs.

 Select the toggle to reduce the application attack surface and to encourage consistent handling of network and file-based application data.

</td></tr><tr><td colspan="2">

**Android developer verification**

</td></tr><tr><td>

Provide developer snippet

</td><td>

Option that enables you to embed a verification snippet from the Android Developer Console or Google Play Console into your signed app. Use this option to complete Google's Developer Verification requirement for existing Android apps. This toggle is off by default.

 **Note:** This section is available only when the system property \(**glide.sn\_mobile\_whitelab.show\_developer\_verification\_snippet\_for\_public\_distribution**\) is configured on your instance.

 When you turn on the toggle, a required **Developer verification snippet** field appears below.

 **Note:** If you select **Next** without turning on this toggle, an alert titled Developer Verification may apply to your app explains the requirement and asks you to go back and turn on the toggle if it applies to you. Select **Continue** to proceed without a snippet, or dismiss the alert to return to the form and turn on the toggle.

</td></tr><tr><td>

Developer verification snippet

</td><td>

Verification snippet from the Android Developer Console or Google Play Console. This field appears only when you turn on the **Provide developer snippet** toggle, and only for Android apps.

 The value can contain only letters and numbers. If the field is empty or contains other characters when you select **Next**, you must correct the value before you can proceed.

</td></tr><tr><td colspan="2">

**Android icons and splash screen**

</td></tr><tr><td>

Use ServiceNow's icons and splash screens

</td><td>

Option that enables you to use the default ServiceNow branding and splash screens.

 If you turn on the toggle to select this option, the customization options are not available.

</td></tr><tr><td>

Adaptive icon foreground

</td><td>

Foreground launcher icon for your app. Select **Upload** to browse for the image file you want to use. The image file must meet the following requirements:

 -   File must be in the PNG format.
-   Image size must be 2048 px by 2048 px.
-   Image must be an icon of a company logo with no text. The icon must take up most of the image.
-   Image must be on a transparent background.


</td></tr><tr><td>

Adaptive icon background

</td><td>

Background launcher icon for your app. Select **Upload** to browse for the image file you want to use. The image file must meet the following requirements:

 -   File must be in the PNG format.
-   Image size must be 2048 px by 2048 px.
-   Image must have no logo or text.
-   Image must have no graphics.
-   Image must not have rounded corners.


</td></tr><tr><td>

Notification icon

</td><td>

Notification icon for your app. This icon is used as the push notification icon on the notification screen. Select **Upload** to browse for the image file you want to use. The image file must meet the following requirements:

 -   File must be in the PNG format.
-   Image size must be 2048 px by 2048 px.
-   Image must contain the company logo with no text on a transparent background.
-   Image must not have rounded corners.


</td></tr><tr><td>

Splash screen logo

</td><td>

Splash screen for your app. Select **Upload** to browse for the image file you want to use. The image file must meet the following requirements:

 -   File must be in the PNG format.
-   Image size must be 2048 px by 2048 px.
-   Image must contain the brand logo or graphic on a transparent background.


</td></tr><tr><td>

Splash screen background color

</td><td>

Colored box where you select a color for the splash screen background color for your app. Select the square and then select a color on the color picker. The associated hex color code is populated in the text box.

</td></tr></tbody>
</table>9.  Select **Next**.

10. In the Review and submit form, review the selections you made in Steps 1-8.

11. If all the selections are what you want, select **Submit** to submit your branded app build request.


## Result

After you complete the request form and submit it, your ServiceNow instance builds the app.

To view the status of the build:

1.  Navigate to **All** &gt; **Mobile Branding** &gt; **Manage Mobile Publishing Apps**.
2.  In **Your recent app requests** section, select the card for your branded app request to view its status on the **Request details** page.

When it completes, you receive an email notification about the status of the build. A link is provided from where you can download an Android App Bundle file \(`.aab`\). If you provided a developer verification snippet, a signed Android Package file \(`.apk`\) containing the snippet is also made available for download alongside the AAB file.

**Note:**

-   You can only submit one build at a time. You can't submit another build until the current build is canceled, failed, or completed.
-   It usually takes about a week or less to build the Android branded application. Sometimes it might take only a few hours. However ServiceNow can't expedite the timeline because it's determined by Google.

## What to do next

After the build successfully completes and your app is ready for testing, see [Test and publish a new branded Android app for public distribution](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/testpubnu-andapp-pubdist.md).