Heuristic to allow certain URLs to trigger high priority notification |
|||
Issue descriptionBrainstorming an idea: For URLs that we can reasonably say are "high quality" based on a to-be-determined heuristic (e.g. user has added to home screen, over X% of users have clicked on URL from PW notifications, user explicitly ASKS to be buzzed by this notification), we can trigger a vibrating notification instead of a non-vibrating one. Inspiration: company that makes a "water drinking reminder" web application wants to be able to trigger a notification that alerts you to drink water whenever you walk by their beacon.
,
May 24 2016
For some of these use cases, I think the solution is to get user to accept notifications from the website itself after initial discovery via PW. This becomes even more powerful if there was a "WebBeacons" api. I don't think PW should be used for "app triggers" as in the water cooler example. That way, the website can make specific, detailed, high priority notifications, in response to the right combination of signals and conditions (do you want notification every time you are near the water cooler, even if you just drank some already? What if you haven't been by the water cooler all day?). This will also greatly simplify attribution (e.g. what happens when the user wants to disable). It's possible we want High priority notifications under some conditions for PW discovery, but the use cases should be framed accordingly.
,
May 24 2016
Makes sense -- maybe the real solution then is to include beacon proximity as another "trigger" for whether or not to fire a web push notification.
,
May 24 2016
,
Jan 9 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by cco3@chromium.org
, May 23 2016