"Mother, May I?" Asking for Permissions
summary
Android 6 (Marshmallow) moves dangerous permissions to runtime, groups them into nine permission groups, and requires targetSdk=23 to opt in; legacy apps keep permissions but the system uses app‑ops to disable APIs rather than remove grants. Use Support v4/13 helpers, FileProvider and Storage Access Framework + URI permission grants to avoid broad storage/read contacts/camera permissions. Dev tools: adb shell pm grant/revoke and adb install -g. UX guidance: check before call, show rationale only after a deny, prefer ACTION_DIAL/ACTION_IMAGE_CAPTURE intents over requesting full CALL_PHONE or CAMERA.
AI-written summary · about
chapters (26)
- 0:00Intro
- 2:04Before Permissions
- 4:46Runtime Permissions
- 12:30Antipattern
- 13:51Permission API
- 16:12Requesting Permission
- 18:48Upgrades
- 19:32Support Library API
- 20:56Command Line Tools
- 21:46Device Policy
- 24:41Permission Categories
- 25:26External Storage
- 26:19External Files
- 27:46Storage Access Framework
- 30:19URI Permissions
- 33:11Phone Permissions
- 33:45Dont Use IMEI
- 34:40Action Call vs Action Dial
- 35:48Camera Mic Permission
- 36:11Camera Intents
- 38:02Redirect Contacts
- 38:23ActionPic
- 38:56Contacts
- 39:34Calendar
- 39:48Action Insert
- 40:07Summary
related talks
37mStriptease of The Android Permissions System (en)
13mFoster user trust by adopting privacy-respecting permission workflows
08mBest practices for building privacy-friendly apps
21mDeveloping privacy user-centric apps
26mStriptease of the Android permission system
19mAdapting Your Apps for Android Q Privacy Requirements
22mPlatform #AskAndroid
22mHow to ask permission, the clean way