diff --git a/docs/html/images/training/articles/user-data-overview-permissions-flow02.jpg b/docs/html/images/training/articles/user-data-overview-permissions-flow02.jpg deleted file mode 100644 index c2275eb59a905..0000000000000 Binary files a/docs/html/images/training/articles/user-data-overview-permissions-flow02.jpg and /dev/null differ diff --git a/docs/html/images/training/articles/user-data-overview-permissions-flow02.png b/docs/html/images/training/articles/user-data-overview-permissions-flow02.png new file mode 100644 index 0000000000000..08b6060149a94 Binary files /dev/null and b/docs/html/images/training/articles/user-data-overview-permissions-flow02.png differ diff --git a/docs/html/training/articles/user-data-overview.jd b/docs/html/training/articles/user-data-overview.jd index 42322a91789b9..2713080d3e437 100644 --- a/docs/html/training/articles/user-data-overview.jd +++ b/docs/html/training/articles/user-data-overview.jd @@ -97,15 +97,19 @@ page.article=true This also means that when you request access to a particular API call or query a content provider behind a permission, the user will be presented with a request to grant permission for the whole group rather than the specific - API call. For example, if you request the MANAGE_ACOUNTS - permission, the user will be asked to grant access to the Identity - group (in API level 22 and lower), which is composed of the GET_ACCOUNTS, - READ_PROFILE, and WRITE_PROFILE permissions, and + API call. For example, if you request the WRITE_CALL_LOG + permission, the user will be asked to grant access to the PHONE + group (in API level 23 and higher), which is composed of the + READ_PHONE_STATE, CALL_PHONE, + READ_CALL_LOG, WRITE_CALL_LOG, + ADD_VOICEMAIL, USE_SIP, + PROCESS_OUTGOING_CALLS GET_ACCOUNTS, + READ_PROFILE, and WRITE_PROFILE permissions, and all their associated methods.

- +

@@ -142,7 +146,7 @@ TelephonyManager.getVoiceMailNumber()

To use these methods, the READ_PHONE_STATE permission must be declared in the app's manifest, and the associated permission group, - Device ID and Call information, will be surfaced to the user. This + PHONE, will be surfaced to the user. This is important, because it means the user will be asked to grant permission for the relevant group and all its associated permissions and API calls, rather than for the specific API call you're requesting. @@ -166,7 +170,7 @@ please refer to the appropriate version-specific documentation below:

media player when there's a call, and to resume playback when the call is over. The permission seems to scare a lot of people...1

+href="#references" style="color:#777;padding-left:.1em;">1

@@ -182,23 +186,23 @@ href="#references" style="color:#777;padding-left:.1em;">1

One study2, in which users + "color:#777;padding-left:.1em;">2, in which users were shown two unbranded apps with similar ratings that had the same functionality but different sets of permission requests, showed that users were, on average, 3 times more likely to install the app with fewer - permissions requests. And a similar study3 showed that users are 1.7 + "color:#777;padding-left:.1em;">3 showed that users are 1.7 times more likely, on average, to select the application with fewer - permission requests. + permission requests.

- Finally, permissions usage is not evenly distributed across apps within + Finally, permissions usage is not evenly distributed across apps within a similar category of Play apps. For example, 39.3% of arcade game apps in the Play store request no permissions that are surfaced to the user while only 1.5% of arcade games request the Phone permission group (see Figure - 1). + 1).