If the site isn’t visited often enough to be on my new tab page then the answer is going to be “no”. I wonder if any of my followers or perhaps @__apf__ feel like it’s time to revisit when websites are allowed to ask? @jaffathecake?https://twitter.com/geekylonglegs/status/1111806913069674496 …
-
-
Replying to @slightlylate @erikcorry and
BTW, we know how to do this right-ish: PWA install prompts started conservative to avoid spamminess, but notification request API was legacy and Mozilla and Apple have very much not helped matters by making progress on the permissions API difficult.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @erikcorry and
My current starting place is to make push notifications a feature of super high engagement score; basically of it isn't installed as a PWA, you won't get the ability to ask.
6 replies 1 retweet 21 likes -
Replying to @slightlylate @erikcorry and
I worry that complex heuristics become a hair-tearing problem for legitimate authors, while malicious ones thrive in it. PWA-only is simple enough to be ok, as long as all browsers do the same thing.
1 reply 0 retweets 0 likes -
Replying to @espadrine @slightlylate and
I also feel like the only notifications that are useful to me are those I seeked out first. Maybe we could forbid asking, and users could find the button in the URL bar?
2 replies 0 retweets 3 likes
I'm afraid "all browsers doing the same thing" is going to be hard. FF is implementing a (fraught) user-activation heuristic instead of working with us to improve the permissions API.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.