FLICKR · 0→1 PRODUCT
Flickr Chat: bringing messaging to mobile
Messaging was Flickr’s most-requested mobile feature for years, and Pros were its biggest users. I designed Flickr Chat, a standalone app that made mobile messaging possible without touching legacy systems.
ROLE
Sole product designer
TEAM
Product, 1 engineer, Trust & Safety team
PLATFORMS
Designed for iOS and Android, light and dark mode
STATUS
Shipped as an early-access beta for Pro members on iOS.



01 — THE PROBLEM
Flickr’s most-wanted feature was stuck on desktop
FlickrMail is a legacy, email-style inbox that only exists on desktop web. Members asked for messaging on mobile more than anything else, but rebuilding FlickrMail meant reworking old code the team didn’t have the resources for.
Legacy and desktop-only
FlickrMail works like email from another era, and there’s no way to message on the apps.
The #1 mobile request
Year after year, members ranked mobile messaging as their top ask in Flickr surveys.
Limited resources
Rebuilding the legacy system wasn’t realistic with the engineering we had.
THE INSIGHT
Messaging was already a Pro behavior.
1st
Pro → Pro
Pros messaging other Pros was the most common use of FlickrMail.
2nd
Free → Pro
Next came free members reaching out to Pros, often to connect or ask about their work.
Even on a dated, desktop-only feature, the people messaging most were paying members. That made Chat more than a feature request: it was a chance to add real value to Pro, which is why we launched it first as early access for Pro members.
02 — THE APPROACH
Start fresh, beside the legacy
01
Test the familiar first
I first designed and tested various messaging vs. inbox layouts to get an idea of how users perceived each. Surprisingly users liked the async style of communicating but wanted more modern, mobile first features. This gave us confidence that a modern conversation layout wouldn’t alienate legacy users.
02
A separate app on new code
To ship with limited engineering, and to test messaging as Pro value, product chose a more experimental path: a standalone Flickr Chat app built in React, with an entry point from FlickrMail to download it. Legacy systems stayed untouched.
03
Mobile-first, both platforms
I designed Chat for iOS and Android from the start, including dark mode, so it could launch alongside the existing Flickr app.
03 — TRUST & SAFETY
Opening up messaging without opening the floodgates
On a photo platform, open messaging invites unsolicited explicit images. Product and Trust & Safety went back and forth on how open Chat should be. I proposed an existing model both teams could move forward with: a request inbox for anyone you don’t have a connection with.
HOW A MESSAGE REACHES YOU
You follow each other
Or one of you follows the other
→
Inbox
Chat right away
No connection
Anyone else on Flickr
→
Requests
Preview with unsafe words and content hidden
→
You decide
View, ignore, or report and block
01
A request inbox for strangers
Messages from people you have no follow connection with land in Requests, not your inbox. Nothing reaches you directly until you choose to view it, ignore it or report it.
02
Previews that protect
Request previews hide unsafe words and content, so you’re never shown something explicit by default, and you can judge a request before opening it.
03
Clear ways out
Reporting and blocking are one tap from any conversation, with plain-language consequences: “They won’t be able to message you or see your stuff.” This helps simplify a complicated feature into a user friendly one.
04
Text first, photos later
Photo sharing, with its own NSFW treatment, moved to V2. That let a safe V1 move forward instead of stalling on the hardest problem.

Requests sit in their own tab, with Ignore and View up front


Block with plain-language consequences, and reporting with clear categories
04 — DETAILS
Designed for real conversations
Swipe with a safety net
Swipe to mark read or delete. A full swipe deletes instantly, with an undo toast to recover from mistakes.
Edit within 15 minutes
Long-press your own message to edit or delete it, so typos don’t live forever.
Badges that mean something
1–9 unread shows a number, 10+ shows 9+, and opening Chat without reading clears the count but keeps a dot.
Built for every language
Labels collapse to icons on small screens or long translations, so the layout holds in every locale.

05 — SCOPE
A smaller V1 that could actually ship
With one engineer and open safety questions, I worked with my product lead to split the work into what Chat needed on day one and what could wait.
V1 · launch
• 1:1 text messaging with people you’re connected to
• Requests, previews, reporting and blocking
• Search across contacts and conversations
• Push notifications and unread badges
• Light and dark mode
V2 · later
• Photo sharing with NSFW treatment
• Threaded replies
• Group chats
• Pro perks, like pinned conversations
• Video and full-resolution attachments
OUTCOME
Flickr Chat shipped as an early-access beta for Pro members on iOS. Feedback was overall positive, and the request-inbox model gave product and safety a shared path to messaging. Flickr later moved resources to other priorities before a wider launch.
06 — WHAT I LEARNED
Safety is a design problem
The hard part wasn’t the chat UI
It was finding a model that let messaging open up without exposing people to abuse. A design proposal unblocked a debate that policy alone couldn’t.
Scope is a design tool
Moving photos and group chats to V2 is what made a safe, buildable V1 possible for a team this small.
NEXT PROJECT