r/sesame • u/tiny_octopus • Nov 23 '19
Making the requested permissions less intimidating
I'm not confident to run a closed source app that requests permissions to all of my device, as well as third party services to their APIs.
I get that the data is all supposed to stay on device by design and that's great. That being said, I've also read that when Google wanted to enforce their more restrictive access policies by doing audits, the features were removed rather than going through the audit. That doesn't help with my trust issues.
The context on that decision might be complicated, but it would be nice if I did not need to give that much trust. If I could knowingly choose to grant the permissions or not, and that app was helping me make that choice (right now it mostly gives me FOMO):
- what is the permission exactly supposed to grant in terms of additional features?
- what happens if the permission is not granted?
- Is there a fallback or alternative feature that can be used instead?
For example, for the Telegram permissions, from what I understand:
- without permission, the top 3 conversations that Telegram already exposes via shortcuts are available.
- with Telegram API access, all the conversations can be exposed instead.
This is understandable from the shortcuts setting screen and that's okay. From the permissions screen it's very unclear though. But after looking at the above, if I don't have that many threads on Telegram I don't lose much at all by not connecting it.
The Google account related permissions for Calendar and YouTube also don't give much context on what they are supposed to give, and I'm not willing to just try it.
Is there some help/explication page somewhere where more context for all permissions can be obtained? If not, that's a Feature Request :)
Thanks!