android 11 |
Major Privacy features
Top privacy changes
This table summarizes the key changes related to privacy that are taking effect in Android 11.
Privacy change Apps affected Mitigation strategy Scoped storage enforcement
Apps that target Android 11 or higher are always subject to scoped storage behaviors Apps that target Android 11 or higher, as well as apps that target Android 10 and haven't set requestLegacyExternalStorage
to true
to opt out of scoped storage Update your app to work with scoped storage
One-time permissions
Users can grant temporary access to location, microphone, and camera using one-time permissions Apps that run on Android 11 or higher and request location, microphone, or camera permissions Check that your app has a permission before attempting to access data that's guarded by that permission
Permissions auto-reset
If users haven't interacted with an app for a few months on Android 11 or higher, the system auto-resets the app's sensitive permissions Apps that target Android 11 or higher and perform most of their work in the background Ask the user to prevent the system from resetting your app's permissions
Background location access
Android 11 changes how users can grant the background location permission to apps Apps that target Android 11 or higher and need access to background location Request foreground (coarse or fine) and background location permissions incrementally in separate calls to the permission request method. When necessary, explain the benefits that users receive for granting that permission
Package visibility
Android 11 changes how apps query and interact with other installed apps on the same device Apps that target Android 11 or higher and interact with other installed apps on a device Add the <queries>
element to your app's manifest
Foreground services
Android 11 changes how foreground services can access location, camera, and microphone data Apps that run on Android 11 or higher and access location, the camera, or the microphone in a foreground service Declare the camera
and microphone
foreground service types for the foreground services that require access to the camera and microphone, respectively. Be aware, however, that foreground services that start while the app is in the background usually cannot access location, camera, or microphone.
This table summarizes the key changes related to privacy that are taking effect in Android 11.
Privacy change | Apps affected | Mitigation strategy | |
---|---|---|---|
Scoped storage enforcement Apps that target Android 11 or higher are always subject to scoped storage behaviors | Apps that target Android 11 or higher, as well as apps that target Android 10 and haven't set requestLegacyExternalStorage to true to opt out of scoped storage | Update your app to work with scoped storage | |
One-time permissions Users can grant temporary access to location, microphone, and camera using one-time permissions | Apps that run on Android 11 or higher and request location, microphone, or camera permissions | Check that your app has a permission before attempting to access data that's guarded by that permission | |
Permissions auto-reset If users haven't interacted with an app for a few months on Android 11 or higher, the system auto-resets the app's sensitive permissions | Apps that target Android 11 or higher and perform most of their work in the background | Ask the user to prevent the system from resetting your app's permissions | |
Background location access Android 11 changes how users can grant the background location permission to apps | Apps that target Android 11 or higher and need access to background location | Request foreground (coarse or fine) and background location permissions incrementally in separate calls to the permission request method. When necessary, explain the benefits that users receive for granting that permission | |
Package visibility Android 11 changes how apps query and interact with other installed apps on the same device | Apps that target Android 11 or higher and interact with other installed apps on a device | Add the <queries> element to your app's manifest | |
Foreground services Android 11 changes how foreground services can access location, camera, and microphone data | Apps that run on Android 11 or higher and access location, the camera, or the microphone in a foreground service | Declare the camera and microphone foreground service types for the foreground services that require access to the camera and microphone, respectively. Be aware, however, that foreground services that start while the app is in the background usually cannot access location, camera, or microphone. |
Top New features & APIs
Overview
Android 11 introduces great new features and APIs for developers. The sections below help you learn about features for your apps and get started with the related APIs.
Media Controls
Android 11 updates how media controls are displayed. Media controls appear near quick settings. Sessions from multiple apps are arranged in a swipeable carousel which includes streams playing locally on the phone, remote streams, such as those detected on external devices or cast sessions, and previous, resumable sessions in the order they were last played.
Users can restart previous sessions from the carousel without having to start the app. When playback begins, the user interacts with the media controls in the usual way.
Conversation imrovements
Android 11 makes a number of improvements to the way conversations are handled. Conversations are real-time, bidirectional communications between two or more people. These conversations are given special prominence, and users have several new options in how to interact with them.
Cht Chat Bubbles
Bubbles are now available to developers to help surface conversations across the system. Bubbles was an experimental feature in Android 10 that was enabled through a developer option; in Android 11, this is no longer necessary.
If an app targets Android 11 (API level 30) or higher, its notifications are not presented as bubbles unless they fulfill the new conversation requirements. Specifically, the notification must be associated with a shortcut.
Prior to Android 11, if you wanted a notification to be bubbled, you needed to explicitly specify that the notification was set to always launch in document UI mode. Beginning with Android 11, you no longer need to explicitly make that setting; if the notification is bubbled, the platform automatically sets the notification to always launch in document UI mode.
0 Comments