--- sourceDocument: Australia Mobile Configuration and Navigation sourceDocumentLink: https://www.servicenow.com/docs/r/australia/mobile Release : - australia ft:locale : - en-US ft:publication_title : - Australia Mobile Configuration and Navigation ft:clusterId : - mobile bundleId : - mobile workflow : - Development, Data and Analytics --- # Test and publish a new branded Android app for public distribution # Test and publish a new branded Android app for public distribution {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](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 public distribution This guide outlines the essential steps for ServiceNow customers to test, configure, approve, customize, and publish a new branded Android app for public distribution using Mobile Publishing. It helps ensure your app meets your branding and functional requirements before deployment on Google Play or enterprise mobility platforms. Show full answer Show less ## Test the app * After the app build completes, access the Request details page via **All \> Mobile Branding \> Manage Mobile Publishing Apps** and select your app request. * Download the Android AAB file for local testing or upload directly to Google Play for internal testing. * Verify key elements including app name, icon, splash screen, branding, theming (using Theme Builder), login instance pre-fill, and legal policies (EULA and privacy policy) appear correctly. ## Set up the app * Optionally configure push notifications by adding your Google Firebase Cloud Messaging HTTPv1 OAuth token to the push application record. Test push notifications using provided ServiceNow guides. * Configure deep links by setting up the `assetlinks.json` file on each instance to enable app linking. ## Approve or reject the app * Review your app's branding and functionality. * Reject if changes are needed---use the Duplicate option to create a new app request with copied details. * Approve the app to proceed with publishing. ## Customize your app's workflows Use the Mobile App Builder tool to tailor your branded app's workflows and user experience to meet your organizational needs. ## Publish and distribute your app * Deploy your tested and approved AAB file to the Google Play Console for public distribution, following Google's publishing requirements and ServiceNow's guidance for metadata setup. * Alternatively, distribute via enterprise mobility management (EMM) providers such as Microsoft Intune, syncing from Google Play as needed. ## Keep your app updated Regularly update your app at least annually or before updating your ServiceNow family version to maintain push notification functionality and access the latest ServiceNow mobile features. Learn the next steps to test and publish a new branded Android app for public distribution after you request it in Mobile Publishing. ## 1. Test the app {#testpubnu-andapp-pubdist__section_hj2_kqb_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 AAB file is downloaded to your local system for testing: 4. Upload the AAB file directly to Google Play so you can use the Google Play internal testing tool. See [Google documentation](https://play.google.com/console/about/internal-testing/) for information about internal testing on Google Play. 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=australia&pubname=australia-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-pubdist__ul_irq_mrb_j2c} {#testpubnu-andapp-pubdist__ol_yth_mqb_j2c} ## 2. Set up the app {#testpubnu-andapp-pubdist__section_hlb_rrb_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. (Optional) If you set up push notifications, test them 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-pubdist__ol_vrf_5rb_j2c} ## 3. Approve or reject the app {#testpubnu-andapp-pubdist__section_lmk_psb_j2c} 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-pubdist__ol_knf_tsb_j2c} ## 4. Customize your app's workflows {#testpubnu-andapp-pubdist__section_ktp_zsb_j2c} Use Mobile App Builder to customize your app. See [Mobile App Builder](https://www.servicenow.com/docs/D7JsRshhaXqbaFuveRefbA "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-pubdist__section_ozq_2tb_j2c} After you have tested your app, set it up, and customized its workflows, you are ready to publish your branded Android for public distribution. Deploy your AAB file to the Google Play console, or your enterprise mobility management (EMM) provider: Upload your app to the Google Play Console: : To upload your public branded Android app to the Google Play Console, see [Google documentation](https://developer.android.com/studio/publish/upload-bundle). Also see [KB1710255](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1710255) and [KB1157062](https://support.servicenow.com/kb?id=kb_article_view&sys_kb_id=a2a066bedb5155d0d0dc3feb68961951) for information about required actions to publish a public Android app on the Google Play Store and for ServiceNow® guidance on creating your Google Play console listing metadata. Microsoft Intune: : To sync your public 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-pubdist__section_gmm_t5b_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/KbgnLcYnaX_y4UQuL6sEyA "Use the following information to verify that your mobile devices and operating systems are ready to use ServiceNow mobile apps."). *[\>]: and then