Chrome 152 gives installed web apps a clearer identity

Google Chrome announced on July 16, 2026, that Chrome 152 will give Progressive Web Apps installed on macOS their own native notification identity. Notifications will display the PWA's name and icon instead of appearing under Google Chrome, creating a more recognizable experience while introducing new permission, badging, and API requirements for developers.

{getToc} $title={Table of Contents}

Chrome 152 gives installed web apps a clearer identity

Notifications sent by installed PWAs previously appeared under Google Chrome at the operating system level and used the browser's icon. This made it harder for users to identify which web app produced an alert and separated notification management from the controls used for native applications.

With native attribution, each installed PWA appears as an individual application in macOS Notification Center and banners. Users can manage its alert style, lock screen behavior, icon badges, and other settings from macOS System Settings. Individual PWAs can also be allowed or silenced through Focus profiles.

{getCard} $type={post} $title={More useful reading}

The notification permission flow now includes macOS

When an installed PWA requests notification permission for the first time, Chrome will skip its browser-level prompt and open the macOS system permission dialog directly. If permission was requested before the site was installed, the user may first see the regular Chrome prompt and later receive the operating system prompt when the installed app attempts to send its first notification.

Existing users are also affected. Permission previously granted to the website inside Chrome does not automatically grant permission to the installed PWA at the operating system level. The first notification attempt will trigger the macOS prompt, while a dismissed request can produce an in-app indicator directing the user to System Settings.

Persistent alerts become a user-controlled setting

Chrome will no longer respect requireInteraction: true on macOS when native attribution is active. The operating system lets each user decide whether an app's alerts are temporary or remain visible until dismissed, so a website cannot guarantee persistence through the Notification API.

Web apps should therefore treat notifications as potentially temporary and avoid making a persistent alert essential to a critical workflow. When longer visibility is useful, the interface can guide users toward the PWA's alert style settings in macOS.

Dock badges and managed devices require extra permission

The App Badging API now depends on operating system notification permission for installed PWAs on macOS. If permission is denied or the user disables Badge app icon, calls to navigator.setAppBadge() can still succeed without an error, but no badge will appear on the Dock icon.

Enterprise administrators need controls at both levels to pre-authorize notifications. The PWA's origin must remain allowed through Chrome's NotificationsAllowedForUrls policy, and a macOS configuration profile must grant notification permission to the PWA's App Shim bundle identifier. Without both settings, users will still receive the system prompt.

IMPORTANT: These changes apply to PWAs installed on macOS from Chrome 152. Test first-time and existing-user permission flows, and do not rely on persistent notifications or Dock badges for essential information.{alertWarning}

Daisuki's Take: What This Means for Web Designers

Native attribution closes an important visual gap between a Progressive Web App and a conventional macOS application. A recognizable name and icon make notifications feel connected to the product instead of looking like generic messages from the browser.

The design work now extends beyond the notification itself. Permission explanations, disabled states, settings guidance, and alternatives for missed alerts should be considered part of the PWA experience, especially when users may deny access or choose temporary banners.

For web app and template creators, the practical step is to test the complete installed experience rather than checking only the browser permission. Strong branding improves recognition, but reliable communication still requires an in-app place where users can find important updates after a notification disappears.

{getCard} $type={custom} $title={What's New?} $info={Find more AI Web design news} $icon={}

Sources and Recommended Links

• Native Notification Attribution for Web Apps on macOS | Chrome for Developers Official Blog