Test and publish a new branded Android app for public distribution

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    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, set up, approve, customize, publish, and maintain a new branded Android app for public distribution after requesting it via Mobile Publishing. Following these steps ensures your app is properly branded, functional, and ready for end-user deployment through Google Play or enterprise mobility management (EMM) providers.

    Show full answer Show less

    Test the app

    • Access the Request details page in Mobile Branding to download the Android AAB testing file.
    • Upload the AAB file to Google Play’s internal testing tool for thorough validation.
    • Verify branding elements such as app name, icon, splash screen, theming, and correct login instance if pre-fill was selected.
    • Confirm the presence of EULA and privacy policy links in the app’s Settings under Legal, matching your specified policies.

    Set up the app

    • Optionally configure push notifications by adding your Firebase Cloud Messaging OAuth token to the push application record for your app type.
    • Test push notifications using out-of-the-box methods to ensure functionality.
    • Configure deep links by setting up an assetlinks.json file on each instance to support seamless app navigation.

    Approve or reject the app

    • Ensure the app meets your branding and functional requirements.
    • Reject the app if changes are needed; use the Duplicate option to create a new request with existing data for edits.
    • Approve the app build to proceed toward publishing.

    Customize your app's workflows

    Use Mobile App Builder to tailor workflows and enhance your branded app experience before publishing.

    Publish and distribute your app

    • Deploy your finalized AAB to the Google Play Console for public distribution, following Google’s publishing guidelines and ServiceNow’s metadata recommendations.
    • Alternatively, distribute via EMM providers such as BlackBerry Portal or Microsoft Intune, using their respective integration methods.

    Keep your app updated

    • Regularly update your app—at least annually or before upgrading your ServiceNow family version—to maintain push notification functionality and access the latest ServiceNow mobile features.
    • Refer to tested devices and supported versions documentation to ensure compatibility.

    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

    After the build successfully completes and your app is ready for testing:
    1. Navigate to the Request details page by selecting All > Mobile Branding > Manage Mobile Publishing Apps > Your 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:

      Mobile Publishing UI showing the download link

    4. Upload the AAB file directly to Google Play so you can use the Google Play internal testing tool.

      See Google documentation 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.
      • 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.

    2. Set up the app

    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 for detailed instructions.

    2. (Optional) If you set up push notifications, test them using an out-of-the-box push notification.

      See KB0829093 for detailed instructions.

    3. Set up deep links for your app by configuring an assetlinks.json file on each instance.

      See KB1648690 for detailed instructions.

    3. Approve or reject the app

    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.

    4. Customize your app's workflows

    Use Mobile App Builder to customize your app. See Mobile App Builder for detailed information about how you can customize your branded app.

    5. Publish and distribute your app

    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. Also see KB1710255 and KB1157062 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.
    BlackBerry Portal:
    To publish your public branded Android app to the BlackBerry Portal if you are using BlackBerry mobile application management (MAM), see KB0813295
    Microsoft Intune:
    To sync your public branded Android app from Google to Microsoft Intune, see Microsoft documentation.

    6. Keep your app updated

    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.