3 ms·

More background services would be very nice even though it's a bit of a security nightmare. A request was opened almost 5 years ago for background geolocation s

More background services would be very nice even though it's a bit of a security nightmare. A request was opened almost 5 years ago for background geolocation services. Any plans for https://developers.google.com/nearby https://developers.google.com/nearby ? I don't want Google or central authorities to decide which PWAs are "trustworthy" directly to ask for certain permissions but there could be a way or compromise. I don't remember which feature it was but it required yes from Google. I really want the first screen after installing PWAs to be their privacy policy or detailing which permissions/how they use them. It should be mandatory and important or may show a default screen with permissions and few dangerous ways they can be used for.

hutzlibu 7y ago
"I really want the first screen after installing PWAs to be their privacy policy or detailing which permissions/how they use them." Wouldn't it make more sense, to display this info before you install a pwa?
- searchableguy 7y ago
  Oh, yeah before. Though, I think it should also show that screen if a user hasn't used the app for a while.
b1tr0t 7y ago
Background geo, including geofencing is challenging, but there may be a way forward. We're exploring this conceptually, but it's not in the plan for 2020. I'd certainly like to be able to improve the capabilities of web based ride sharing and similar apps that have a need for this. Bluetooth discovery is an especially thorny area from a privacy perspective. What use cases did you have in mind? Asking for permissions upfront has been found to be an anti-pattern in systems UXR. Research has found that users make better decisions and find the experience less interruptive when permissions are requested in context at runtime. For example, in a video chat app, it's better to ask for the camera/mic permission at the start of the first chat session, not when the app first starts. Mac OS, Android etc. and other platforms have all been moving in this direction over the past few years. When the permission is requested, we're investigating ways that we can do more to communicate permission risks to the user. Nothing publicly shareable yet, but do expect experiments to be showing up in dev channels over the next few months while we try new things.

hutzlibu 7y ago

"I really want the first screen after installing PWAs to be their privacy policy or detailing which permissions/how they use them." Wouldn't it make more sense, to display this info before you install a pwa?

searchableguy 7y ago
Oh, yeah before. Though, I think it should also show that screen if a user hasn't used the app for a while.

b1tr0t 7y ago

Background geo, including geofencing is challenging, but there may be a way forward. We're exploring this conceptually, but it's not in the plan for 2020. I'd certainly like to be able to improve the capabilities of web based ride sharing and similar apps that have a need for this. Bluetooth discovery is an especially thorny area from a privacy perspective. What use cases did you have in mind? Asking for permissions upfront has been found to be an anti-pattern in systems UXR. Research has found that users make better decisions and find the experience less interruptive when permissions are requested in context at runtime. For example, in a video chat app, it's better to ask for the camera/mic permission at the start of the first chat session, not when the app first starts. Mac OS, Android etc. and other platforms have all been moving in this direction over the past few years. When the permission is requested, we're investigating ways that we can do more to communicate permission risks to the user. Nothing publicly shareable yet, but do expect experiments to be showing up in dev channels over the next few months while we try new things.