Adapting Your Apps for Android Q Privacy Requirements
summary
Android 10 enforces concrete privacy changes: location gains allow only while app is in use (foreground services count), apps request incremental background permission rather than asking both up front, and foreground services must declare foregroundServiceType=location to receive updates on Q. Storage moves to scoped access — getExternalFilesDir still works, media contributions use MediaStore with an is_pending flag and Storage Access Framework for downloads, edits use recoverable security exceptions. IMEI/serial access is blocked for third‑party apps (use Android ID, per‑app UUID or advertising ID), background activity starts are restricted, and Wi‑Fi/Bluetooth scans require location permission.
AI-written summary · about
chapters (9)
- 0:00Introduction to Android Q
- 1:38User control over data access
- 3:05Location permission changes
- 9:51External storage updates
- 18:55Background activity restrictions
- 21:45Permanent IDs and alternatives
- 24:23Wi-Fi and location access
- 25:26Privacy-first app design
- 29:06Best practices summary
related talks
19mAdapting Your Apps for Android Q Privacy Requirements
45mWhat's new in Android: Android Q and Privcy
18mOverview of privacy changes in Android Q
36mUpdating your apps for location permission changes in Android Q
08mBest practices for building privacy-friendly apps
39mWhat’s “Q” in Android Security
21mDeveloping privacy user-centric apps
32mWhat’s new in shared storage
