Android 17 Beta 3: photo picker customization and privacy defaults that will show up as UX friction (if you ignore them)

Original post (source): Android Developers Blog - “The Third Beta of Android 17” (March 26, 2026)

• https://android-developers.googleblog.com/2026/03/the-third-beta-of-android-17.html

What’s new (the parts app teams will actually feel)

Android 17 Beta 3 is platform stable (API surface locked), so this is when teams should stop hand-waving “we’ll look later” and start doing compatibility testing.

A few items in the post are especially relevant to app growth teams because they change real UX, not just SDK trivia.

1) Photo picker customization (privacy without the ugly modal)

Android’s privacy-preserving Photo Picker is being pushed harder as the default way to request media without broad storage permissions.

In Android 17, apps can now customize the picker UI using PhotoPickerUiCustomizationParams. The headline example is changing the grid aspect ratio (from 1:1 to 9:16), and it applies to both:

• ACTION_PICK_IMAGES intent
• the embedded photo picker

This matters because permission and media-pick moments are conversion moments (profile setup, listing creation, onboarding), and “it looks foreign” is a real drop-off driver.

2) Certificate Transparency enabled by default

Certificate Transparency (CT) is enabled by default for apps targeting Android 17.

This is mostly “security plumbing”, but the failure mode is not theoretical: if your networking stack or certificate setup is sloppy, you discover it as broken login, broken checkout, and a pile of 1-star reviews.

3) Local network access blocked by default (targeting Android 17)

Android 17 blocks local network access by default for apps targeting 17+. The post nudges teams toward:

• privacy-preserving pickers where possible
• new ACCESS_LOCAL_NETWORK for broad, persistent access

If your app has any “smart home”, “device pairing”, “casting”, or LAN discovery behavior, this will be felt as “setup broke”.

Why this matters for marketers (not just engineers)

Two patterns repeat:

• platform privacy changes show up first as funnel friction
• teams only notice once support tickets, churn, or ratings move

If you want the store listing to convert, the first session still has to work.

Tiny win

Before your next Android 17 targeting push:

1. run your top 3 onboarding flows and identify every media pick moment
2. if you are not on the Photo Picker, make a plan (and decide what “good-looking” means for your UI)
3. QA one real device on a realistic network setup (Wi-Fi, VPN on/off) to catch CT and local-network surprises

Treat this as conversion hygiene, not compliance work.