Conversation

Replying to
The normal approach is for apps to open the system file manager and have the user choose files/directories. The interface you're showing is for authorizing an app to be a full file manager. Apps can't directly request it through a dialog, but users still want that capability.
2
4
Replying to
The alternative to store policy would be users being outraged about it. Scoped storage is very new and apps barely adopted SAF before being forced so people aren't used to it. Users tend to wrongly think SAF means the app has access to those files but it's a system file manager.
1
1
Replying to and
They could try to have a nuanced policy where you have to implement the functionality without it to the extent possible so that the app works without it. Could trivially stop allowing apps to directly open the Settings activity if they wanted too. It was a decision to export it.
1
1
Replying to and
You can drop .nomedia files into directories to stop stuff getting indexed but that's a power user feature. They do need to improve SAF quite a lot and add some nicer new APIs including more specialized media selection. It's mostly the fault of apps being really invasive / lazy.
1
1
Replying to and
It doesn't only apply to files. Many apps should be using the system camera intent for capturing videos and images, system contact picker, etc. I don't actually understand why any app would want to make their own terrible camera instead of using a good one without a permission.
1
1
Show replies