Applicable XR devices This guidance helps you build experiences for these types of XR devices. [Learn about XR device types →](https://developer.android.com/develop/xr/devices) ![](https://developer.android.com/static/images/develop/xr/ai-glasses-icon.svg) Audio \&  
Display Glasses [](https://developer.android.com/develop/xr/devices#audio-display) [Learn about XR device types →](https://developer.android.com/develop/xr/devices)

<br />

Audio glasses and display glasses use the standard Android notification
framework, so you can notify users across different form factors using the same
notification APIs. To promote maximum compatibility and minimize development
overhead, use the Android [`NotificationCompat`](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat) APIs. Android parses
incoming notifications and adapts their presentation based on the capabilities
of the device.

By following the [best practices for notifications](https://developer.android.com/develop/ui/compose/notifications), your existing phone
notifications can be bridged to audio glasses and display glasses with little to
no additional configuration. Read the information in the following sections to
understand how the system adapts notifications for audio glasses and display
glasses.

## How the system determines whether to bridge a notification

Android uses the incoming notification's [`Notification.Style`](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.Style) together with
several other criteria to determine whether or not to bridge the notification to
the user's audio glasses or display glasses.

### Supported notification styles on display glasses

Display glasses support a subset of Android `Notification.Style` classes. The
following notification styles are fully rendered on display glasses:

- [Standard style (`NotificationCompat.Style`)](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.Style)

  ![Standard style notification](https://developer.android.com/static/images/develop/xr/jetpack-xr-sdk/glimmer/standard-notification.png)
- [`MessagingStyle`](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.MessagingStyle)

  ![MessagingStyle notification](https://developer.android.com/static/images/develop/xr/jetpack-xr-sdk/glimmer/messagingstyle-notification.png)
- [`BigPictureStyle`](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.BigPictureStyle)

  ![BigPictureStyle notification](https://developer.android.com/static/images/develop/xr/jetpack-xr-sdk/glimmer/bigpicturestyle-notification.png)
- [`ProgressStyle`](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.ProgressStyle)

- [`MediaStyle`](https://developer.android.com/reference/kotlin/androidx/media/app/NotificationCompat.MediaStyle)

- [`CallStyle`](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.CallStyle) (only when the notification [qualifies as a live
  update](https://developer.android.com/develop/ui/compose/notifications/live-update))

Other notification styles (such as [`InboxStyle`](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.InboxStyle)) aren't fully parsed and
rendered. For these styles, style-specific fields aren't rendered (such as the
[summary text](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.InboxStyle#setSummaryText(java.lang.CharSequence)) for `InboxStyle`). Instead, the system reverts to the
standard style and renders only common fields such as the [content title](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.Builder#setContentTitle(java.lang.CharSequence)).

> [!NOTE]
> **Note:** Custom notifications with `RemoteViews` aren't bridged to glasses.

### Other required criteria for bridging

Besides the notification's style, a notification must also meet the following
criteria to be bridged to the user's audio glasses or display glasses:

1. The notification isn't subject to **any** of the following user-controlled
   settings that would prevent its delivery:

   - **Glasses companion app settings**:

     - App-level toggle: Users can select which app notifications are
       bridged to the glasses. When notifications on the glasses are turned
       on, specific app notifications are turned off by default, except for
       those in the "Suggested" list.

       This default behavior lets a user leave notifications enabled on
       their phone for a certain app, but disable them for that app on
       their glasses. To help a user decide whether to enable notifications
       for your app in the Glasses app, explain how
       notifications would improve their experience with your app.
   - **System-level notification settings on the user's phone**:

     - App-level toggle: If a user disables notifications entirely for an
       app on the phone, no notifications for that app are bridged.

     - Notification channel settings: If a user disables notifications
       for an [app-defined notification channel](https://developer.android.com/develop/ui/compose/notifications/channels), no notifications
       for that channel are bridged.

   - **System-level Do Not Disturb (DND) settings on the user's phone**: AI
     glasses use the phone's DND settings. If the user's phone is in DND
     mode, notifications are also suppressed on the user's glasses.

2. The notification is assigned to a channel with [`IMPORTANCE_HIGH`](https://developer.android.com/reference/kotlin/android/app/NotificationManager#importance_high) or
   [`IMPORTANCE_MAX`](https://developer.android.com/reference/kotlin/android/app/NotificationManager#importance_max).

3. The [notification's title](https://developer.android.com/reference/kotlin/android/app/Notification#extra_title) isn't `null` or empty.

4. The notification isn't marked with [`FLAG_LOCAL_ONLY`](https://developer.android.com/reference/kotlin/android/app/Notification#flag_local_only). If this flag is
   set, the notification is restricted to the primary device.

5. The notification isn't an [ongoing notification](https://developer.android.com/reference/kotlin/android/app/Notification.Builder#setongoing), such as a persistent
   background task, unless it [qualifies as a Live Update notification](https://developer.android.com/develop/ui/compose/notifications/live-update).

## How Live Update notifications are bridged to display glasses

[Live Update notifications](https://developer.android.com/develop/ui/compose/notifications/live-update) are a specialized class of notifications
designed for ongoing, user-initiated activities that require real-time
monitoring, such as rideshare ETAs, turn-by-turn navigation, or active calls.
Unlike regular notifications, live updates remain active to provide a continuous
stream of information that are surfaced prominently across the system UI.

For display glasses, live updates are rendered in two primary locations:

- **Home screen** : Live Update notifications appear on the Home canvas as [cards](https://developer.android.com/design/ui/ai-glasses/guides/components/cards). If multiple live updates are active, the system uses a [stack](https://developer.android.com/design/ui/ai-glasses/guides/components/stack) instead.
- **System bar** : When the user is inside another app or experience, live updates appear as status chips in the [system bar](https://developer.android.com/design/ui/ai-glasses/guides/surfaces/sysui#system-bar). These chips appear briefly whenever a status change occurs. If the display is asleep, a status chip automatically wakes the screen to signal a status change, so the user stays informed without manual interaction.

If a live update notification uses a [supported notification style](https://developer.android.com/develop/xr/jetpack-xr-sdk/glasses/notifications/behavior#notification-styles) for AI
glasses, it is fully parsed and rendered. Live Updates notifications that use
other notification styles (such as [`BigTextStyle`](https://developer.android.com/reference/kotlin/androidx/core/app/NotificationCompat.BigTextStyle)) aren't fully parsed,
and the system adapts them to a standard style notification instead.

## Available notification actions for display glasses

On display glasses, incoming notifications appear as
[heads-up notifications](https://developer.android.com/develop/ui/compose/notifications#Heads-up) (HUNs). For `MessagingStyle` notifications, your
app can use a [direct reply](https://developer.android.com/develop/ui/compose/notifications/create-notification#reply-action) action. Users can tap to expand for more
details and reply. For all other notification styles, the only available option
is the system-provided clear action.

When using direct reply, users can reply with their voice or select from a smart
reply list by scrolling forward. For smart replies, you can use [on-device
AI](https://developers.google.com/ml-kit/language/smart-reply/android) to suggest short, relevant replies.