Mobile Publishing use cases

  • Release version: Xanadu
  • Updated August 1, 2024
  • 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 Mobile Publishing Use Cases

    Mobile Publishing enables organizations to create branded mobile applications tailored to their specific needs. It addresses various requirements such as having multiple app types on a single device, enhancing employee trust and adoption, and allowing for customized app distributions outside traditional app stores.

    Show full answer Show less

    Key Features

    • Multiple Mobile Apps: Create custom mobile apps with unique client names if more than two apps are needed on one device.
    • Private Distribution: Distribute apps privately via intranet, email, or EMM vendors.
    • Unlisted Apps: Publish apps that are not listed on the Apple app store.
    • Push Notifications: Utilize push notifications for on-premise customers.
    • Pre-release Access: Gain early access to app versions for testing before general distribution.
    • Custom Licensing and Policies: Implement your own end-user license agreements and app protection policies.
    • Custom App Store Listings: Personalize app descriptions and images in app store listings.
    • Enhanced App Management: Manage additional apps using MAM or MDM solutions.
    • Custom Login Features: Streamline login processes with pre-populated URLs for better user experience.

    Key Outcomes

    Using Mobile Publishing, organizations can effectively manage their mobile application ecosystem, ensuring compliance with internal policies, improving user experience, and enhancing overall employee engagement with their mobile solutions. Licensing for Mobile Publishing is available through various ServiceNow subscription levels or can be purchased from the ServiceNow Store.

    Here are several reasons to use Mobile Publishing to brand the mobile apps of your company.

    Common reasons for using Mobile Publishing

    Use Mobile Publishing if your company needs a branded app for any reason or to satisfy any of the following requirements.
    • Need more than two mobile apps to exist on any one device. Because the ServiceNow Mobile Platform doesn't support two mobile apps of the same type on the same mobile device, end users can only have one Now Mobile and one Mobile Agent app (branded or not) on their devices. If end users need a third mobile app type, you can use Mobile Publishing to create custom-type apps with unique mobile client names.
    • Enable employee trust in the app and increase employee adoption.
    • Distribute your app privately off any app store through your intranet, by email, text link, iTune or Blackberry Enterprise Mobility Management (EMM) vendor, or by other means.
    • Need an "unlisted app" in the Apple app store. For more information, see Distribute Unlisted Apps to Apple Devices on the Apple support website.
    • Use push notifications and you’re an on-prem customer.
    • Need to be insulated from potential issues related to releases of the standard published ServiceNow mobile apps.
    • Want early access to certain app versions before they’re automatically sent to the phones of your employees. Having early access means that you can test and choose whether to distribute apps later when they’re requested and approved.
    • Remove the need for employees to update their apps on a monthly basis when the standard published ServiceNow mobile apps are updated.
    • Must use your own end-user license agreement.
    • Must use your own app protection policy.
    • Want to customize the app store listings descriptions and images.
    • Need to leverage features and flags that are available in the app configuration of EMM vendors.
    • Need an additional mobile app that is managed by a MAM or an MDM when you already have a standard published ServiceNow mobile app that isn't managed by a MAM or an MDM.
    • Customize app behavior to make them more efficient for your end-users to use. For example, you can request a custom branded mobile app and configure an auto-populated URL so your end-users don't need to type the instance URL during login. This can be configured in the Login management section of the Request a new app form. For more information, see the Request, test, and publish a branded mobile app section that contains instructions for requesting custom branded apps for both the iOS and the Android platforms.
    For more information about deciding whether Mobile Publishing is right for the requirements of your company, see the white paper Mobile Publishing: Decision Trees and Guidance.
    Note:
    You must have an account and log in to the ServiceNow University website to access this white paper.

    Licensing

    Mobile Publishing is a paid plugin. It is included in the Pro, Enterprise, and App Engine subscription levels (SKU's) of ServiceNow®. Alternatively, you can purchase the plugin on the ServiceNow Store and add it to your ServiceNow subscription. Navigate to the ServiceNow Store, log in with your credentials, and then search for mobile publishing.