This is a good thing. There are too many apps that request full disk access despite not needing it.
I counted 44* applications on my mac that ask for FDA. I've only granted it to 8. The other apps work just fine without it. (Some apps that ask for full disk access: Anki, a flashcard app and Soulver, a calculator app – cmon now)
This change is less about bureaucracy and more requiring developers to be more clear why it needs the permissions it does.
I think a lot of apps do it just to avoid all the different prompts. It’s probably easier to get the average person to say yes to that than to have to go through each one over time.
Can I see your documents? Your downloads? Your home folder? Your desktop?
And it’s not like they all happen at once. Every time you go to open a file, it randomly asks you if it’s somewhere they haven’t done it before. Maybe because they’re not using the system open save dialogue, which automatically grants access to that one file.
I like that macOS has these facilities. But the existing dichotomy of all or nothing + 30 prompts just didn’t work well.
> Apps that might ask for Full Disk Access or System & App Protection Override include backup apps, disk cleaners, file indexers, security apps, and others.
This is not what Full Disk Access was designed for. Not a huge fan of Apple misrepresenting what permissions do so they can pretend like their policies are consistent and not a kneejerk reaction to what’s going on in the world.
> > Apps that might ask for Full Disk Access or System & App Protection Override include backup apps, disk cleaners, file indexers, security apps, and others.
> This is not what Full Disk Access was designed for
Can you explain why an app for backups or indexing don’t need access to your files? I’m really confused what you’re trying to say?
I'm saying that Apple is intentionally picking a limited set of uses that they claim the API is for. Obviously the other options are valid use cases (although most backup apps do not use full disk access in this way, because even with that you miss some data that makes it difficult to restore the machine from).
It might be interesting to take a peek at what Apple is using it for, or namely, what exemptions Apple gives themselves. Is Safari a backup app or file indexer? Why does it get to bypass the protections, hmm? (Hint: it has access to your Firefox and Chrome folders.)
The only complaint I’ve seen is that the full disk access dialog is scary.
Well ok? Full disk access is EVERYTHING. Keys to the kingdom. If it’s not encrypted (and some of Apple’s stuff isn’t that should be) then apps that have the permission can anything.
Before that wasn’t the worst thing in the world, most apps didn’t care. But now we have LLMs. And suddenly people are realizing just how creepy full disk access really is.
For me more important would be to exclude specific folders from that full disk access (like ~/.ssh), rather than selecting one directory.
For example I've used Daisy Disk app to visualize directory size. It's best used with full disk access. But I know that my `.ssh` is tiny and I'd prefer for this app not to be able to access it at all.
This is great! I loved when iOS let me expose only a subset of my contacts list to whatsap (and, this is important: banned facebook from retaliating) -- the subset it already knows, and this is another good step in the right direction. I trust precisely 0% of apps with my private data, and apple making it easier to limit exposure is good!
I counted 44* applications on my mac that ask for FDA. I've only granted it to 8. The other apps work just fine without it. (Some apps that ask for full disk access: Anki, a flashcard app and Soulver, a calculator app – cmon now)
This change is less about bureaucracy and more requiring developers to be more clear why it needs the permissions it does.
*edit: originally said 56
Mine are a raspberry pi image flasher, Alfred, my backup software, and ghostty.
(Not saying you're computing wrong, I'm interested in your computer experience, it's just different from mine)
Can I see your documents? Your downloads? Your home folder? Your desktop?
And it’s not like they all happen at once. Every time you go to open a file, it randomly asks you if it’s somewhere they haven’t done it before. Maybe because they’re not using the system open save dialogue, which automatically grants access to that one file.
I like that macOS has these facilities. But the existing dichotomy of all or nothing + 30 prompts just didn’t work well.
This is not what Full Disk Access was designed for. Not a huge fan of Apple misrepresenting what permissions do so they can pretend like their policies are consistent and not a kneejerk reaction to what’s going on in the world.
> This is not what Full Disk Access was designed for
Can you explain why an app for backups or indexing don’t need access to your files? I’m really confused what you’re trying to say?
What apps was it actually designed for, that you say Apple is misrepresenting?
Well ok? Full disk access is EVERYTHING. Keys to the kingdom. If it’s not encrypted (and some of Apple’s stuff isn’t that should be) then apps that have the permission can anything.
Before that wasn’t the worst thing in the world, most apps didn’t care. But now we have LLMs. And suddenly people are realizing just how creepy full disk access really is.
So I agree. This is a great change.
For example I could set my "Top Secret Ideas" folder to "Deny" for "All Apps" but "Read & Write" for Finder and my Markdown editor.
The tricky part would be how to assign IDs or "accounts" for apps and what to do when an app gets updated..
For example I've used Daisy Disk app to visualize directory size. It's best used with full disk access. But I know that my `.ssh` is tiny and I'd prefer for this app not to be able to access it at all.
This looks really well-implemented, considering the complexity of explaining all of this to users.