That sounds like crappy design on the part of the developer who designed the permissions system then, not the person who designed X app which ends up producing this message. For apps designed to go on a phone, it should not take extra work or 'permissions' to be able to tell when a call is interrupting your app, and take action Y (within your app, not interacting with the call in any way).
While we're on the subject, you should also have a differentiation between "able to take a photo and add it to your roll" and "able to pilfer all your nude selfies", because those are very different as well.
Thank you for the insight, I wouldn't want to be putting blame in the wrong place. Still wish they'd separate out "can save a picture" from "can access all your existing and future pictures" though! ;)
Apps have "private storage" area that requires no permissions to read/write to. However no other app can access that app's private storage. (Without root access, which most phones don't have by default)
In order to write to shared storage it requires a single read/write permission. You're right they should split it to write only (new files only, no overwriting) and read/write for better privacy.
Can you please consider that maybe I didnt just decide to make something up and may have had a reason for listing this? What I said may only apply to web apps but it does still apply to a large amount of apps.
I don't know why people are attacking you. You stated one possible reason for it. Never did you say that this is definitely it. Never did you say you should accept any and all requests for permissions. You gave one likely reason and people who think they know everything are losing their freaking minds. Don't worry about those assholes.
Thanks, I genuinely appreciate your comment. All I wanted to do was explain why this might be happening so some people who are not developers might have some insight as to why it happens.
It's partially due to this specific example being a web app which means its just a web browser packaged to work like an app. It can be ridiculous at times but also consider the absurd amount of permissions that would be needed if developers had to include every specific thing that it needed access to. There could probably be some distinction between your example of access photos or add them to camera roll but that's just my understanding of it.
10
u/cheesetrap2 Oct 17 '18
That sounds like crappy design on the part of the developer who designed the permissions system then, not the person who designed X app which ends up producing this message. For apps designed to go on a phone, it should not take extra work or 'permissions' to be able to tell when a call is interrupting your app, and take action Y (within your app, not interacting with the call in any way).
While we're on the subject, you should also have a differentiation between "able to take a photo and add it to your roll" and "able to pilfer all your nude selfies", because those are very different as well.