Comment by miki123211
7 hours ago
This is basically required for clueless (and even not so clueless) users.
If there's a chat app I installed 3 years ago, with no intention of giving it camera access, and I suddenly need to use that app for a video call, I don't want to be stuck debugging broken camera issues for two hours. I'd much rather have the app tell me that it doesn't have camera access.
This is fair for permissions. But for notifications, the app shouldn't need to know. It can just send them into the void for all the app cares. If the notification doesn't work then it should never break critical app functionality and apps should be built with the assumption that users will never see/interact with notifications.
> This is basically required for clueless (and even not so clueless) users.
I can actually confess that this hit me. Almost nothing on my phone has permission to use my camera, including my web browser (why???). I assume this was done in a fit of pique upon discovering that the setting even existed.
Roll on (god knows how many years later) and I cannot get into the gym with the link I was emailed to have my browser read a QR because my browser is just a grey screen. It was only when the member of staff suggested permissions that I realised what was going on.
I'm the problem, it's me
The OS could tell you instead. If it is a camera app, the OS could tell you on install, that you can't start the app without given camera access, because that's what the app is.