#AskChrome We learned this week from Firefox that 99% of users don't accept notification requests, yet I'm still hearing "the Web has to compete with Native". How will you ensure the 103 features on the Fugu roadmap don't end up in the same position as Push Notifications?
We thought hard about that case in the design of both SWs and Notifications. If you do a silent update more than once or twice, we eventually show a notification on your behalf to let the user know work happened and allow them to revoke the permission.
-
-
One question we haven't resolved is: if the system app model allows work to happen in the background in this way w/o UI, should the web? We can throttle it, and we can restrict to only happen from networks/IPs users has talked to specific servers from before...haven't built it.
-
There's a related one there with geolocation and geo fencing - could you have a permission so the sw can get notified by the location api (with the same kind of granularity that latest android has for foreground/background)
- 3 more replies
New conversation -
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.