diff --git a/docs/html/preview/features/runtime-permissions.jd b/docs/html/preview/features/runtime-permissions.jd index 2ee44efae38a8..99941200ba492 100644 --- a/docs/html/preview/features/runtime-permissions.jd +++ b/docs/html/preview/features/runtime-permissions.jd @@ -1,4 +1,4 @@ -page.title=Runtime Permissions +page.title=Permissions page.tags=previewresources, androidm page.keywords=permissions, runtime, preview @jd:body diff --git a/docs/html/preview/preview_toc.cs b/docs/html/preview/preview_toc.cs index 0a141bb5d9123..07afcddce520a 100644 --- a/docs/html/preview/preview_toc.cs +++ b/docs/html/preview/preview_toc.cs @@ -29,7 +29,7 @@ API Overview
- The Runtime Permissions feature + The new Permissions model changes the way that permissions are allocated to your app by the user. Instead of granting all permissions during the install procedure, your app must ask the user for individual permissions at runtime. For users this behavior provides more granular control over each app’s activities, as @@ -89,7 +89,7 @@ page.image=images/cards/card-set-up_16-9_2x.png
- The Runtime Permissions change affects the structure and design of your app, as well as + The permissions change affects the structure and design of your app, as well as the user experience and flows you provide to users. You should assess your app’s current permissions use and start planning for the new flows you want to offer. The official release of the platform provides compatibility behavior, but you should plan on updating your app and not @@ -112,8 +112,8 @@ page.image=images/cards/card-set-up_16-9_2x.png
- For more information on the behavior of Runtime Permissions, testing, and best practices, see the - Runtime Permissions developer + For more information on the behavior of runtime permissions, testing, and best practices, see the + Permissions developer preview page.