Adapting Your Apps for Android Q Privacy Requirements
summary
Android Q makes concrete changes: location gains an only-while-in-use permission and foreground services must declare a foreground-service metadata flag to keep accessing location; external storage moves toward scoped storage with the Storage Access Framework and a manifest fallback flag for legacy behavior, while media contributed to MediaStore is readable without permission; background activity launches are limited with narrow exceptions (visible window, activity in back stack, bound service, pending intent — alarm manager excluded); non-resettable IDs like IMEI and build serial restricted to system-only; always check permissions before access to avoid security exceptions.
AI-written summary · about
chapters (7)
- 0:00Introduction to Android Q privacy
- 1:31Key Android Q privacy features
- 3:41Location permission changes
- 8:21External storage access updates
- 12:16Restricting abusive foreground activities
- 15:26Restrictions on hardware IDs
- 17:59Best practices and takeaways
related talks
29mAdapting 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
39mWhat’s “Q” in Android Security
32mWhat’s new in shared storage
08mBest practices for building privacy-friendly apps
21mDeveloping privacy user-centric apps