The Chrome team continues evaluating how they'll implement support for the Android Photo Picker. Recently they added a flag that controls what Picker is launched:
"It is not entirely clear which way of launching the Media Picker is the right one for Chrome, so we're adding four variations to allow for some experimentation."
H/T LanceAdams on Telegram
1) GET_CONTENT is currently handled by DocumentsUI (the system file picker). Google is experimenting with having the new Android Photo Picker "take over" handling of the GET_CONTENT intent. This briefly rolled out in November but was reverted.
2) ACTION_PICK_IMAGES intent is the standard way to invoke the framework Photo Picker on Android 11+ (though Chrome stills seems to require Android 13?). Through GMS, Photo Picker is also backported to Android 4.4+
3) ACTION_PICK_IMAGES "Plus" is interesting. The MIME type is set to */* (ie. all) which Photo Picker does not handle and instead forwards to DocumentsUI. It seems the Chrome team wants the Photo Picker team to add a way to force the Photo Picker to show the "browse" button...
...in the overflow menu; currently this "browse" button only appears when the Photo Picker is invoked through the GET_CONTENT takeover, and tapping it opens the system file picker/DocumentsUI.
I personally think this would be useful; give users the option to open the more feature-rich DocumentsUI, no matter how the Photo Picker is invoked, while still defaulting to the prettier Photo Picker for image/video selection.
4) Chrome Picker, this just launches the old in-app media picker, which means you have to grant Chrome gallery access permissions.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Google Play has just announced a new data deletion policy that I welcome 🎉
If your Android app allows users to create an account, then Google Play will eventually require you to offer a way for users to initiate account AND data deletion from within the app and from the web.
Google Play will require that the web link for account/data deletion be provided to users through your app's Data Safety section, as shown in the GIF embedded above. This is so users can request deletion WITHOUT reinstalling your app.
When completing the Data Safety form, there'll be new questions related to this data deletion policy. Google's asking developers to submit answers by December 7, 2023. Sometime in early 2024, users will see the new data deletion badge and area in apps' store listings.
Although Google Play currently lets you install Cross-Device Services onto any Android 13 device, the Android-to-Chromebook app streaming feature will NOT work for you unless you the app was already preinstalled in the OS by the OEM.
For example, I could install Cross-Device Services onto my Zenfone 8 running Android 13. It installs fine, but it will never work for one reason: It can't get the permissions it needs!
Problem 1: Priv-app permissions. Cross-Device Services requests several permissions that can only be granted to privileged apps (located in a priv-app directory) through Android's privileged permission allowlisting mechanism. This must be done at build time by the OEM.