Android 4.4 (API level 19) introduces the Storage Access Framework (SAF). The SAF makes it simple for users to browse and open documents, images, and other files across all of their preferred document storage providers. A standard, easy-to-use UI lets users browse files and access recents in a consistent way across apps and providers.
Cloud or local storage services can participate in this ecosystem by implementing a
DocumentsProvider that encapsulates their services. Client
apps that need access to a provider's documents can integrate with the SAF with just a few
lines of code.
The SAF includes the following:
- Document provider—A content provider that allows a
storage service (such as Google Drive) to reveal the files it manages. A document provider is
implemented as a subclass of the
DocumentsProviderclass. The document-provider schema is based on a traditional file hierarchy, though how your document provider physically stores data is up to you. The Android platform includes several built-in document providers, such as Downloads, Images, and Videos.
- Client app—A custom app that invokes the
ACTION_OPEN_DOCUMENT_TREEintent actions and receives the files returned by document providers.
- Picker—A system UI that lets users access documents from all document providers that satisfy the client app's search criteria.
Some of the features offered by the SAF are as follows:
- Lets users browse content from all document providers, not just a single app.
- Makes it possible for your app to have long term, persistent access to documents owned by a document provider. Through this access users can add, edit, save, and delete files on the provider.
- Supports multiple user accounts and transient roots such as USB storage providers, which only appear if the drive is plugged in.
The SAF centers around a content provider that is a
subclass of the
DocumentsProvider class. Within a document provider, data is
structured as a traditional file hierarchy:
Note the following:
- Each document provider reports one or more
'roots', which are starting points into exploring a tree of documents.
Each root has a unique
COLUMN_ROOT_ID, and it points to a document (a directory) representing the contents under that root. Roots are dynamic by design to support use cases like multiple accounts, transient USB storage devices, or user login/logout.
- Under each root is a single document. That document points to 1 to N documents, each of which in turn can point to 1 to N documents.
- Each storage backend surfaces
individual files and directories by referencing them with a unique
COLUMN_DOCUMENT_ID. Document IDs must be unique and not change once issued, since they are used for persistent URI grants across device reboots.
- Documents can be either an openable file (with a specific MIME type), or a
directory containing additional documents (with the
- Each document can have different capabilities, as described by
COLUMN_FLAGS. For example,
FLAG_SUPPORTS_THUMBNAIL. The same
COLUMN_DOCUMENT_IDcan be included in multiple directories.
As stated above, the document provider data model is based on a traditional
file hierarchy. However, you can physically store your data however you like, as
long as you can access it by using
API. For example, you could use tag-based cloud storage for your data.
Figure 2 shows how a photo app might use the SAF to access stored data:
Note the following:
- In the SAF, providers and clients don't interact directly. A client requests permission to interact with files (that is, to read, edit, create, or delete files).
- The interaction starts when an application (in this example, a photo app) fires the intent
ACTION_CREATE_DOCUMENT. The intent can include filters to further refine the criteria—for example, "give me all openable files that have the 'image' MIME type."
- Once the intent fires, the system picker goes to each registered provider and shows the user the matching content roots.
- The picker gives users a standard interface for accessing documents, even though the underlying document providers may be very different. For example, figure 2 shows a Google Drive provider, a USB provider, and a cloud provider.
Figure 3 shows a picker in which a user searching for images has selected the Downloads folder. It also shows all of the roots available to the client app.
After the user selects the Downloads folder, the images are displayed. Figure 4 shows the result of this process. The user can now interact with these images in the ways that the provider and client app support.
Writing a client app
On Android 4.3 and lower, if you want your app to retrieve a file from another
app, it must invoke an intent such as
ACTION_GET_CONTENT. The user must then select
a single app from which to pick a file and the selected app must provide a user
interface for the user to browse and pick from the available files.
On Android 4.4 (API level 19) and higher, you have the additional option of using the
which displays a system-controlled picker UI controlled that allows the user to
browse all files that other apps have made available. From this single UI, the
user can pick a file from any of the supported apps.
On Android 5.0 (API level 21) and higher, you can also use the
intent, which allows the user to choose a directory for a client app to
ACTION_GET_CONTENTif you want your app to simply read or import data. With this approach, the app imports a copy of the data, such as an image file.
ACTION_OPEN_DOCUMENTif you want your app to have long term, persistent access to documents owned by a document provider. An example would be a photo-editing app that lets users edit images stored in a document provider.
For more information on how to support browsing for files and directories using the system picker UI, see the guide on how to access documents and other files.
For more information about document providers, take advantage of the following resources: