Skip to content
Material Design 2
Main Navigation
v3
v2
v1

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

English

简体中文
繁體中文
Español
Français
Русский
Português – Brasil
Deutsch
日本語
한국어
Italiano
Polski
Türkçe
čeština
magyar

Appearance

Sidebar Navigation

Material System

Introduction

Material studies

About our Material studies

Basil

Crane

Fortnightly

Owl

Rally

Reply

Shrine

Material Foundation

Environment

Surfaces

Elevation

Light and shadows

Layout

Understanding layout

Pixel density

Responsive layout grid

Spacing methods

Component behavior

Applying density

Navigation

Understanding navigation

Navigation transitions

Search

Color

The color system

Applying color to UI

Color usage

Text legibility

Dark theme

Typography

The type system

Understanding typography

Language support

Sound

About sound

Applying sound to UI

Sound attributes

Sound choreography

Iconography

Product icons

System icons

Animated icons

Shape

About shape

Shape and hierarchy

Shape as expression

Shape and motion

Applying shape to UI

Motion

Understanding motion

The motion system

Speed

Choreography

Customization

Interaction

Gestures

Selection

States

Communication

Confirmation & acknowledgement

Data formats

Data visualization

Empty states

Help & feedback

Imagery

Launch screen

Onboarding

Offline states

Writing

Machine learning

Machine learning patterns

Object detection: live camera

Object detection: static image

Barcode Scanning

Material Guidelines

Material Theming

Overview

Implementing your theme

Usability

Accessibility

Bidirectionality

Platform guidance

Android bars

Android fingerprint

Android haptics

Android icons

Android navigating between apps

Android notifications

Android permissions

Android slices

Android split-screen

Android swipe-to-refresh

Android text selection toolbar

Android widget

Cross-platform adaptation

Components

App bars: bottom

App bars: top

Backdrop

Banners

Bottom navigation

Buttons

Buttons: floating action button

Cards

Checkboxes

Chips

Data tables

Date pickers

Dialogs

Dividers

Image lists

Lists

Menus

Navigation drawer

Navigation rail

Progress indicators

Radio buttons

Sheets: bottom

Sheets: side

Sliders

Snackbars

Switches

Tabs

Text fields

Time pickers

Tooltips

On this page

Android permissions ​

Permission requests should be simple, transparent, and understandable.

Usage ​

Android apps have limited permissions associated with them by default. If your app selected to apply “normal” permissions, the system automatically grants those without user input.

For permissions that extend beyond the scope of normal permissions, the user must explicitly grant those permissions. These are classified according to the following groups.

Permission groups ​


Permissions are divided into nine groups, allowing users to grant all permissions encompassed by a single action by bundling them together as a group.

For example, to provide a user with permission to view, edit, and add Contacts, it’s more efficient to group these permissions into a single permission group (called Contacts) than to request each individually.

Permission GroupDescription
CalendarManaging calendars
CameraTaking photos and recording videos
ContactsManaging contacts
LocationCurrent device location
MicrophoneAudio recording
PhoneDialing and managing phone calls
Body SensorsHeart rate and similar data
SMSSending and viewing messages
StorageAccessing photos, media, and files

Intents and Intent Filters

Intents and Intent Filters

Related link

Demonstrated intent ​

A user may perform an action that demonstrates clear intent, such as:

  • Taking a picture
  • Selecting a contact
  • Starting a call or text message

In these cases, the user’s action clearly demonstrates their intent, and no permission dialog is needed or authorized.

Anatomy ​

Diagram of permission group icon, app name, “Never ask again” check box, indicator for multiple dialogs, action
1. Permission group icon
2. App name
3. “Never ask again” check box (This is displayed if a user denies a permission twice)
4. Indicator for multiple dialogs
5. Action

Request types ​

Your permissions strategy depends on the clarity and importance of the permission type you’re requesting. Each strategy offers a different way of introducing permissions to the user.

Critical permissions should be requested up-front.

Secondary permissions can be requested in context.

Permissions that are less clear should provide education about what the permission involves, whether done up-front or in context.

Determine the clarity and importance level of each permission
Determine the clarity and importance level of each permission.

Request types: educate before asking

Educate before asking

If your app has a “warm welcome,” use it to explain what your app does and why unexpected permissions will be requested.

Request types: ask up-front

Ask up-front

Only ask for critical and obvious permissions on first launch.

Because users expect a messaging app to request SMS permissions, requesting it up-front makes sense.


Request types: ask in context

Ask in context

Wait until a feature is invoked to request permission.

Users are more likely to allow a permission when they want to use the feature it enables.

Request types: educate in context

Educate in context

Explaining a permission in context helps gauge user interest and improve comprehension of the permission.


Request types: provide an immediate benefit

Provide an immediate benefit

Provide instant gratification to make accepting a permission feel justified.

Request types: only ask for relevant permissions

Only ask for relevant permissions

When more than one permission is needed for a feature to work, only ask for those permissions and nothing else.

Runtime permissions ​


Apps may request permission to access information or use device capabilities at any time after installation. When a user needs to perform an action in an app, such as using the device camera, the app may request permission at that moment.

Users may also allow or deny the permissions of any app from Android Settings anytime after installation.

Example of an app requesting permission
Example of an app requesting permission

Denied permissions ​


Provide feedback whenever a permission is denied. Because denying permissions may prevent a feature from working as intended, whenever a permission is denied it should be explained to the user.

Permission denials occur in one of two ways:

  • A permission request is denied by the user
  • A permission is silently denied without warning because a user once selected “Don’t ask again” from a previous permission request

To ensure that features requiring permission always behave as intended, the app should state that permission is needed and provide a way to allow it.

A snackbar displays the need for permission in order to use an audio feature
A snackbar displays the need for permission in order to use an audio feature.

Critical permissions

If the app can no longer run because a critical permission has been denied, explain why that permission must be allowed and offer a button to open Settings so the user can allow it.

A screen explains that a permission is needed for an app to function, with a link to allow that permission in Settings
A screen explains that a permission is needed for an app to function, with a link to allow that permission in Settings.
Pager
Previous pageAndroid notifications
Next pageAndroid slices

Released under the Apache-2.0

Copyright © 2018-Present Google

https://m2.material.io/design/platform-guidance/android-permissions.html

Released under the Apache-2.0

Copyright © 2018-Present Google