[smartician]

Full disclosure: I'm a Google employee, but not in the areas mentioned in the article. This is my personal opinion.

Regarding the Nest thing: I don't think those devices stop working completely if you don't enable location sharing for the "home and away" feature. It might be bad UI that made the user think that this is the case?

Regarding photo sharing: I think that permission is necessary to show a "photo picker" inside the app that allows the user to pick and choose which photos to upload. I'm not quite sure what the alternative would look like: "he can identify specific pictures in his library and grant access to just those" --> How exactly would that work without the app having access to the pictures? Also, does the author believe the app would then secretly analyze all pictures and send content back to the mothership without the user's consent? Again, this might be a communication/UX issue...

[skywhopper]

Bad UI is an intentional decision by the app developers to shepherd folks into thinking they have no choice.

As for how to make photo library access selective, iOS does this just fine. The app thinks it’s seeing everything, but it can only see what you selected. Plus Apple has made it easy to edit those choices. And if you do grant an app unlimited access, it checks in every once in a while to be sure you still want it (particularly if you don’t use the feature very often).

[KTibow]

> How exactly would that work without the app having access to the pictures?

Android recently added an option that lets apps pop up a picker and only get access to the picked pictures. They probably just didn't realize that some users might want to only share some photos with Google Photos or didn't think the slice was big enough to justify implementing.

[snibsnib]

GrapheneOS has Storage Scopes that does exactly this. (https://grapheneos.org/features#storage-scopes)

[Almondsetat]

>How exactly would that work without the app having access to the pictures?

Extremely simple: the photo picker is part of the OS and not the app, so the app can open it and wait for return file handles without knowing a thing about what the file browser will display

[rlue]

Selective access to a set of user-specified photos is a native feature of iOS. Any time an app prompts you to choose some photos from your photo reel, you are first given the option to explicitly choose which photos the app even has access to.

[kentonv]

On a desktop browser, if a web site wants me to upload photos, I click the "upload" button, and then the browser displays a file picker. The web site only ever sees the files I choose.

The web has this because it has to. Obviously you can't just give a web site permission to see your whole hard drive just to open one file.

But this kind of "privileged picker" approach does not seem to be the norm for mobile apps. I'm actually not even sure if iOS and Android even offer such a UI, or if apps simply have no choice but to request full access and implement their own picker.

If they do offer a picker, I would guess the reason the Google Photos app doesn't use it is not because Google's trying to invade your privacy, but rather because a product manager did not like the fact that they couldn't control the look and feel of the UI. It probably is significantly uglier and clunkier than what the Photos app itself can provide. And unfortunately, most users don't care about granting permissions. So the sleeker UX wins out. (I hate this.)

[sssilver]

I don’t know about Android but iOS does offer a picker. The user can grant permission for the app to access all photos, only selected photos, or none.