#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?
Great question! We've ended up with a relatively small number of geofencing requests that aren't implicitly spammy -- there was one for unlocking rental cars that was pretty good, but not many others -- and the concern there is silent tracking...
-
-
We shelved work on geofencing over privacy, but unsatisfying to not have an answer. Took a while to see it from a different perspective, but eventually
@beverloo (and I think@owencm) realised we could flip it around. The result is Notification Triggers:https://github.com/beverloo/notification-triggers … -
Still behind a flag, but my hope is that we'll be able to expand from timed triggers to geolocation triggers at some point soon. Heading to Origin Trial soon, but available behind a flag now.
End of conversation
New conversation -
-
-
The
#indieweb concern is building an equivalent to Google maps' location history that isn't in a silo. The stuff Aaron does with Overland and Compasshttps://aaronparecki.com/gps/ -
I think this is a great question we should tackle in Fugu. I'd like to be more privacy preserving than Native here, and so far we've been very conservative. Usage indicators might suffice? IDK.
End of conversation
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.