Quieter notifications permissions
summary
Chrome implements Quiet Notification UI (introduced in Chrome 80) that moves prompts to the omnibox or an infobar, animates a bell, and lowers interruptiveness; sites with the lowest accept-rate percentiles are auto-enrolled and Chrome will adaptively enable quiet mode for users who repeatedly block. Developers can check accept rates in the Chrome User Experience Report, aim for 80% (over 50% is safer), and prepare for Chrome 84’s enforcement that flags abusive or misleading notification prompts.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:23Overview
- 0:53What are web notifications
- 1:19Why notifications are important
- 1:56Getting enrolled in notifications
- 2:16Abused websites
- 2:26Why notifications
- 2:40Web notifications
- 3:36Web notifications UI
- 3:46Notification prompt
- 4:03Notification info bar
- 4:30Notifications UI
- 4:56How users get enrolled
- 6:40What should you do
- 7:29Quiet notification UI mode
- 7:56Chrome User Experience Report
- 8:49Make notifications boring context
- 9:38Whats next
- 10:51Conclusion
related talks
16mLooking beyond Prompts for Permissions in Chrome
41mChrome and the web in 2020
45mWhat’s new in Chrome?
41mhttps://*every site here*
10mUsers' Perceptions of Chrome Compromised Credential Notification
01h 06mBrowser panel
40mWhat’s New with Chrome and the Web
01h 19mEffective Transparency and User Controls: Are We Close to a Breakthrough?