Permissions
8 post(s)
-
Android 17 Beta 4: the ‘boring’ changes that become support tickets
Android 17 Beta 4 is the last scheduled beta, and the headline for app teams is not one feature, it is a bundle of default-tightening changes: local network access blocked by default (new ACCESS_LOCAL_NETWORK permission), background audio hardening, certificate transparency on by default, plus new memory limits and profiling triggers for anomalies.
-
Android Developers: Play is pushing contact picker, location button, and a real account transfer flow
Google’s Android Developers blog frames the April 2026 Play policy changes as ‘clearer choice’ plus business protection. The practical bits: move invites/sharing off READ_CONTACTS and onto Contact Picker/Sharesheet, use the location button for one-off precise location, and plan for an official account ownership transfer workflow with a cooldown.
-
Google Play policy update (Apr 15, 2026): contacts access, account transfers, location, health data
Google Play’s April 15 policy announcement adds a new Contacts Permissions policy, formalises developer account transfers, and tightens expectations around location and sensitive health data. Here’s what changes, what’s just clarified, and what to sanity-check this week.
-
Play policies are turning into product work (contacts picker, location button, and account transfers)
A credited summary of the Android Developers Blog post on updated Play policies, focused on the concrete implementation changes that reduce review risk and user friction.
-
Location SDK panic is usually a configuration story, not a magic data leak
OneSignal clarifies how location works in its mobile SDK: it is off by default, requires explicit developer enablement, and still depends on OS-level user permission. Useful framing for privacy reviews and stakeholder questions.
-
Android 17 is making location permissions more ‘in-the-moment’ (and harder to over-collect by accident)
Android 17 introduces a new ‘location button’ for one-time precise location, stronger transparency indicators, improved coarse location in low-density areas, and a redesigned runtime permission dialog. This is privacy work, but it also reduces friction in the moments where users actually want location to work.
-
Android 17 Beta 3: photo picker customization and privacy defaults that will show up as UX friction (if you ignore them)
Android 17 reaches platform stability in Beta 3. Buried in the release is a practical UX change: you can now customize the photo picker’s layout to match your app, while keeping the privacy-preserving picker model. At the same time, defaults like certificate transparency and local network protections keep tightening.
-
Android 17’s Contact Picker: a privacy-first replacement for broad contacts permission
Android’s new Contact Picker lets apps request only the specific contact fields a user selects, helping teams avoid READ_CONTACTS for common invite/share flows.