This post has been republished via RSS; it originally appeared at: Windows Blog.Users tell us that they find notification requests bothersome and distracting – except when they don’t. We want sites to engage with users without annoying them, but we also don’t want our users to miss reminders that may be important for them. With new changes that we’re rolling out, we are hoping to solve both problems at the same time.
What we learned from quiet notification requestsOur users told us that they were dissatisfied with how often they saw notification requests distract them from their current task. To help resolve this issue, we shipped quiet notification requests in Microsoft Edge 84, which reduced the prominence of notification requests while keeping them at a noticeable location in the UI. This experience was enabled by default on all sites to address user feedback about unwanted notifications.
Balance the full prompt and quiet requests : the wisdom of the crowdSome sites offer valuable notifications, and have a high rate of user acceptance when they ask permission for notifications. Other sites offer less valuable (or even spam) notifications, and have a much lower rate of user acceptance when they ask permission to send notifications. We want to maximize the value of notifications and minimize their annoyance by quieting notification requests in the latter case, without penalizing sites offering valuable notifications. To build a good balance, we have developed a new approach we’re calling adaptive notification requests, and have started experimenting with it in Microsoft Edge 88. With this new approach, we provide either the full prompt or quiet requests based on the data accrued from actual user choices – we’re crowdsourcing! We suggest site owners provide permission requests with consideration to the user’s context and timing, after users have engaged with sites. Sites that follow good practices and earn a high user acceptance rate will begin to show the full prompt without being “quieted.”
How it worksTo achieve balance presenting the full prompt and quiet requests, we introduced a score system. Here's an example of the full prompt to understand how we use each user choice when a full prompt is provided.
|Allow||Click on "Allow" button|
|Block||Click on "Block" button|
|Ignore||Navigate away without interaction on the full prompt or close tab itself|
|Dismiss||Close the full prompt by clicking on 'x'|
Configuring quiet notificationsWith this feature rollout, users will see a new "Quiet notification requests" setting in the Microsoft Edge settings page (Settings → Cookies and site permissions → Notifications), which is disabled by default.
A better notification experienceFollowing positive results from our experiment in Canary, Dev, and Beta channels, we have rolled out this new experience to all users in Microsoft Edge 88 Stable. We are keen to continue to monitor the feedback and improve the experience as needed. With this balanced approach, we want to see users be more satisfied with their notification experience on the web. Check out the best practices section in our previous blog to see how you can improve your notification acceptance rate. As sites follow best practices, we hope to see the overall user acceptance rates improve so that over time only known spammer sites will get quiet requests and sites can continue to benefit from user engagement through notifications. We are excited to see what change this experiment is going to bring!
Other notification improvementsIn addition to the notification request experience, we’re also improving notifications in general. Here are a few improvements we have shipped:
- Enabled background push when the browser is not open: Beginning with Microsoft Edge 85, users can now receive push notifications even when Microsoft Edge is closed. With this change, users will never miss notifications from their favorite sites. This feature requires Windows 10 version 20H1 or above.
- Addressed user feedback where Windows toasts would permanently remain on the screen: we found that many users were frustrated by “high priority” toast notifications set with the requireInteraction member, as these notifications never disappear without user interaction. Starting with Microsoft Edge 85, these notifications auto-dismiss in Windows Action Center after 25 seconds.
- Improved Chromium’s integration with the Windows Action Center by fixing unresponsive notification click bugs. Starting with Microsoft Edge 85, we fixed three bugs where clicking on notifications in Action Center failed to trigger onclickevent handlers. We fixed this issue upstream, so both Chrome and Microsoft Edge 85 and above work correctly with the notifications dismissed to Windows Action Center.