Google Photos Solved Sharing. It Didn’t Solve Consent.
When group albums become crowdsourced, curation can’t be one-sided.
There was a time when sharing photos from a trip meant chasing people across WhatsApp, email threads, and pen drives.
Then shared albums happened.
Today, for almost every trip or get-together, there’s a simple pattern:
One person creates a Google Photos album.
Everyone uploads their photos.
Everything gets auto-arranged by timestamp.
It just works.
And in many ways, Google Photos solved this problem beautifully.
The problem starts after sharing works
When multiple people contribute to the same album, something predictable happens:
Not all photos are equal.
Some are great
Some are duplicates
Some are blurry
And some… are just not flattering for the people in them
The problem is simple:
The person in the photo has no control over the photo.
Only the uploader does.
The current workaround is broken
In my circles, we’ve created a workaround:
If you want a photo removed, just “like” it.
Which is… completely backwards.
A “like” is supposed to mean this is a good photo
Instead, it becomes please delete this
Even worse:
You can’t delete a photo from within the album
You can only remove it from the album
To actually delete it, you have to go find it in your library
And if there are multiple similar photos?
Good luck picking the right one.
The only slightly better workaround is to archive the photo first — so it moves out of your main library — and then go into the archive to delete it.
Which means:
You’re now using a storage management feature
to solve a social curation problem.
That’s usually a sign something fundamental is missing.
The missing layer: consent-based curation
Shared albums today are optimized for aggregation, not consent.
But once photos include people, this becomes a social system — not just a storage system.
What’s missing is simple:
The ability for subjects of a photo to signal whether they are okay with it being there.
The missing feature
A lightweight layer that sits on top of shared albums:
1. “Flag for Review” (not Delete)
Any person in the album can flag a photo
The flag is private (not publicly visible)
2. Subject-aware signals
If multiple people in the same photo flag it → higher priority
If the uploader flags it themselves → instant action
3. Smart uploader nudges
The uploader gets a clean prompt:
“2 people requested changes on this photo”
With quick actions:
Remove from album
Delete permanently
Ignore
4. Album-level hygiene
Optional filters:
“Show flagged photos”
“Pending review”
Why this matters
This isn’t just about UX.
It’s about social comfort in shared digital spaces.
Right now:
Sharing is frictionless
Control is asymmetric
And that asymmetry creates silent friction:
People hesitate to upload
People feel awkward asking for deletions
People live with photos they don’t like
The shift
Google Photos solved:
“How do we put everyone’s photos in one place?”
The next problem is:
“How do we make everyone comfortable with what’s in that place?”
One small toggle
Sometimes the biggest UX gaps are not about new features.
They’re about missing permissions.
A simple “flag for review” toggle could turn shared albums
from crowdsourced dumping grounds
into socially aware memory spaces
If someone at Google sees this:
Build This Next.
I write about how products can be better — fixing what’s broken and imagining what’s missing.
If this made you notice something broken or missing, you can subscribe to Build This Next to receive future essays directly.
Every subscription is a vote for building better products.
And if this sparked an idea, take a few seconds to share it — it might help someone else build or see products differently.