Conversation

Google: We're killing all file managers in Android Q. Apple: iPad's file manager gets SMB, unzip, and USB support! When did I enter an alternate dimension?

154

672

Replying to

wait, what? why kill file managers ?

Replying to

and

File managers still work. Apps are forced to use the Storage Access Framework for accessing shared storage, which means that users can choose the scope for their access. The app can provide a suggestion, but the API is designed to avoid apps from forcing all or nothing access.

Replying to

and

The built-in file manager will also still be there, and that's the interface used for selecting file and directories when apps use the Storage Access Framework. It finally gives users control rather than apps requesting full shared storage access and refusing to work otherwise.

Replying to

and

SAF is just Google's file manager. That doesn't count. Ground up implementations of feature rich file managers are being crippled, right? Maybe in R?

Replying to

and

That's not an accurate portrayal of SAF. You're misunderstanding what it implements and how it works. An app can request persistent access to a directory tree, which uses the system UI to ask the user to determine access scope. It's entirely usable for implementing file managers.

Replying to

and

SAF is a generic file access API. Apps can use as both a client (like a word processor or a file manager) and as a provider (like an app providing access to cloud storage or a network file system). It's not a file manager. It uses the system file manager UI for choosing scope.

7:20 PM · Jun 3, 2019Twitter Web Client

Replying to

and

So, for example, a file manager will request persistent access to a directory tree. The user can select the root of the volume in the SAF system UI to grant full access to the volume. The file manager now has full, persistent access to that storage volume but it's up to the user.

Replying to

and

It's covered in the official documentation on Scoped Storage: developer.android.com/preview/privac ACTION_OPEN_DOCUMENT_TREE has been supported since Android 5.0. File managers already had to use it to access external drives, since Android 4.4 removed access that wasn't via the SAF API.

Show replies