--- sourceDocument: Brazil Mobile Configuration and Navigation sourceDocumentLink: https://www.servicenow.com/docs/r/mobile Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Mobile Configuration and Navigation ft:clusterId : - mobile bundleId : - mobile workflow : - Development, Data and Analytics --- # Configure theming # Configure Next Experience theming for mobile {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Configure Next Experience theming for mobile This guide explains how to enable and configure Next Experience theming for ServiceNow mobile apps, starting with version Utah and later. Next Experience theming allows you to apply consistent, modern visual styles across your mobile interfaces, improving user engagement and brand representation. Show full answer Show less ## Available Themes and Defaults * **Coral:** The default theme for Zurich and later versions with Next Experience enabled. It features brand-neutral illustrations and a fresh look. Existing customers upgrading to Zurich must manually select Coral. * **Polaris:** Default for Utah through Yokohama versions with Next Experience enabled. Customers upgrading to Zurich retain Polaris unless they manually switch to Coral. * **Mobile Legacy:** Used as a fallback theme on instances upgraded to Utah or later but without Next Experience enabled. Each theme is represented as a record in the **UX Themes \[sysuxtheme\]** table and linked to one or more **UX Style \[sysuxstyle\]** records specifying UI appearance, primarily colors. ## Creating and Customizing Themes Default themes and styles are not editable, but you can create copies to customize them. By copying and modifying UX Theme and UX Style records, you can override colors by assigning higher priority values. Note that only color elements affect the mobile UI; other style properties like fonts or shadows do not apply on mobile. ## Assigning Themes to Mobile Apps Use the **Mobile Theme** field in the Mobile App Builder to assign a specific theme to an app. When left empty, the system automatically selects the default theme based on the version and Next Experience status: * Zurich and later with Next Experience enabled: Coral * Utah through Yokohama with Next Experience enabled: Polaris * Next Experience disabled: Mobile Legacy Different mobile apps can use different themes if desired. ## Using Color Variables in Custom Mobile Components To maintain a consistent visual experience, use color variables defined in the UX Styles when building custom mobile components such as UI rules, navigation sections, map pins, icons, view templates, mobile view buttons, and input description fields. Applying these variables ensures your customizations align with the active theme. Learn how to enable Next Experience theming, and create and apply themes for your mobile apps. ## Enable Next Experience {#config-ne-theming__section_adj_vz5_xvb} Important: Use Next Experience theming on Utah and later versions of ServiceNow® instances. To use Next Experience theming, you must have Next Experience enabled on your instance. For activation instructions and more information on Next Experience, see [Exploring themes in Next Experience](https://www.servicenow.com/docs/access?context=next-experience-theming&version=brazil&pubname=brazil-platform-user-interface&ft:locale=en-US). ## Available themes for mobile apps {#config-ne-theming__section_iwr_f1v_xvb} Themes are defined by records in the UX Themes \[sys_ux_theme\] table. Your instance includes three base system themes for use in the mobile UI, they are: Coral, Polaris, and mobile legacy.Figure 1. Comparison of the themes legacy, Polaris and Coral Note: * From Zurich versions and above Coral is the default theme with Next Experience enabled. * For Utah to Yokohama versions, Polaris is the default theme with Next Experience enabled. You can use either one of these options. * Existing customers upgrading to Zurich who use Polaris as their default Next Experience theme will retain Polaris as their mobile theme unless a different theme is selected. {#config-ne-theming__ul_fc2_z15_bgc} Coral : Coral is the default theme for instances with Next Experience enabled for versions Zurich and above. Customers upgrading to the Zurich theme will not automatically have their theme upgraded to Coral. Instead they will manually have to select the theme. For configuration instructions, see [Assign a Next Experience theme in the Mobile App Builder](https://www.servicenow.com/docs/6JcSgjLID7isOlaWSlgAFw "Use the Mobile App Builder to assign your Next Experience themes."). The Coral theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. : A core UX Style \[sys_ux_style\] record called Mobile Colors Default is included with the Coral theme. This record cannot be modified, but, users can create a copy of this record or create a new theme record. Give your new or copied record a higher priority value to override the colors specified in the Mobile Colors Default record. Polaris : Polaris is the default theme for instances with Next Experience enabled for the versions Utah through Yokohama. Note: For customers upgrading to the Zurich theme, Polaris remains your Next Experience theme, unless you manually upgrade to Coral. : A new core UX Style \[sys_ux_style\] record called Mobile Colors Default is included with the Polaris theme. This record cannot be modified, but, user can create a copy of this record or create a new theme record. Give your new or copied record a higher priority value to override the colors specified in the Mobile Colors Default record. Mobile Legacy : Mobile legacy is a fallback theme. Instances with upgraded to Utah or later that do not have Next Experience enabled use this theme. Under the Polaris or Coral theme is a UX Style \[sys_ux_style\] record named Mobile Colors Default. This record defines the color variable names and the colors associated with them. ## Create themes and styles {#config-ne-theming__section_lqb_d1v_xvb} Create Next Experience themes on the UX Theme \[sys_ux_theme\] table on your instance. By default, instances with Next Experience enabled use the Coral theme. (From Utah through Yokohama versions, the default is the Polaris theme). Instances without Next Experience enabled use the Mobile Legacy theme. These themes can't be modified, but you can copy either of them and change that copy. Each UX Theme record is linked one or more UX Style \[sys_ux_style\] records that define the appearance of the UI when you apply a theme to your instance. As with theme records, the default style records aren't editable, but can be copied. Learn more about Next Experience theme configuration at [Configuring Next Experience themes and preferences](https://www.servicenow.com/docs/access?context=config-next-experience-themes-prefs&version=brazil&pubname=brazil-platform-user-interface&ft:locale=en-US). Important: Mobile apps only use the color elements of a UX style. Elements such as font, shadow, opacity, and other non-color elements in a theme do not change the appearance of the mobile UI. ## Assign a theme to your mobile client {#config-ne-theming__section_ibz_3hd_dwb} Set a theme for your mobile apps in the Mobile App Builder using the new Mobile Theme field. If the Mobile Theme field is empty : Your instance checks the state of whether Next Experience is enabled and determines which UX Theme \[sys_ux_theme\] record to use for the mobile app. By default: * For the Zurich version, if Next Experience is enabled, the Coral theme is used. * For Utah through Yokohama, if Next Experience is enabled, the Polaris theme is used. Note: You can use different mobile themes for each mobile app, when using Next Experience. * If Next Experience is disabled, the Mobile Legacy theme is used. {#config-ne-theming__ul_vb3_qlm_ngc} If the Client Theme field is not empty : Your mobile apps always use the theme specified in the field to theme the mobile app. ## Use color variables on your custom mobile components {#config-ne-theming__section_axv_l1v_xvb} Use color variables when designing your mobile components to provide a consistent user experience. The following components take advantage of color variables: * UI rules * Navigation sections * Map pins * Icons * View templates * Mobile view buttons * Input description fields {#config-ne-theming__ul_v55_5qf_zvb} How to use color variables varies depending on the component you're building. For information on how to apply color variables on each of these components, see [Color theme considerations for mobile](https://www.servicenow.com/docs/UTrBC5C4nvtKarxuL0EYCw "Learn how to use color in your mobile applications to improve user experience. Using the right colors for your environment can help guide your users through your app and quickly identify important information.").