Birding Echoes
Revisiting and sharing past birding experiences
Role
Product Designer
Timeline
6 Months
Client
Merlin Bird ID

TL;DR
What began as my master’s capstone project became a partnership with Merlin, an AI-powered bird ID app. In a small team (me, another designer and a researcher), I started with blind birders and found that Merlin’s recordings were rarely revisited after a session. So I made logging more meaningful, gave people easier ways to look back, and added sharing and reminders. I coded a working prototype with Claude Code for remote accessibility testing. Merlin’s team asked us to keep building these features with them, and they’re on track to ship in spring 2027.
01 · Log
Recordings that hold the moment
Sessions title themselves and keep field notes, friends and photos.

02 · Look back
A home for every session
My Recordings, a page for every bird and a map of every place you’ve birded.

03 · Share
Made to be shared
Shareable stories and bird mixes, built for Instagram and group chats.

On track to launch
in the Merlin app in spring 2027
Reach
Designing for 10M+ Merlin users
Scope
Self-initiated and pitched to Cornell Lab
What is Merlin
Merlin identifies birds by sound, but no one had tested it with people who can’t see
Merlin Bird ID is a free, AI-powered bird identification app from the Cornell Lab of Ornithology. Hold up your phone, and Sound ID listens to the birds around you, naming each one as it sings.

Why blind birders
So I pitched an accessibility project, focused on blind birders and an auditory-first experience
This began as my capstone for the University of Washington’s MHCI+D program, with a team of three: me, a fellow designer, and a researcher. Merlin’s own team is small too, and they hadn’t had the bandwidth for usability testing or generative research. No one had studied how the app works for people who can’t see it. I took that on.
Birding is often thought of as a visual activity, but Merlin is primarily an auditory app. That made me curious about how blind birders were using it.
What we found
People only went back to recordings to share them, so I designed more ways to share
Across 6 interviews, 2 field observations, ~6,000 app reviews, and 2 mixed-visibility co-design sessions, one pattern kept coming up: no one revisited past recordings on their own. They only went back to share them with someone. So we built better ways to get back to past recordings, reminders to revisit them, and dedicated ways to share.
Before

Past recordings hid behind a small gray button
Today, past recordings sit behind a small button in gray text at the bottom of the home page. Many people we talked to had never noticed it.
After

My Recordings gives every session a home
My Recordings gives each past session its own page. “This week” shows a calendar that opens for every session.
Logging a session
Merlin identifies birds by sound, but every session gets saved the same way
Before
A list of bird names
A past recording was just a list of the birds Merlin heard. Every session looked the same, with nothing to tell one morning apart from the next.
After
Make recordings personal
Now you can add field notes, the friends you birded with, photos, and whatever else made the outing stand out. Each recording becomes a memory you log your way.
Going back to a session
No one was going back to their past sessions, so I made them worth going back to
Before
When a recording ends, Merlin saves it with a date, a city, and a bird count. There’s no prompt to add anything, so most sessions are saved as a timestamp and nothing else.
After
When you end a session, Merlin asks if you want to finish logging now or later. The session titles itself and fills in relevant data, and you can add things like field notes to help you reminisce when you look back on the recording.
Sharing your birding experience
there is no dedicated way to share in Merlin
Before
Sharing meant screenshotting the app
With no way to share from inside the app, birders screenshotted Merlin and posted the screenshot to social media. It worked, but it said little about the moment itself.

After
So I built dedicated sharing into the app
We designed sharing artifacts: stuff you could post to an Instagram story if you wanted to be public, or a quick emoji bird summary to drop into a text chat.




How I got here
100 ideas narrowed down to 3

Date, species and place mattered most when trying to go back to past birding memories
We made scrappy designs and put them in front of birders until it was clear that date, species, and location were what mattered most when looking back at birding memories.



Merlin’s team helped pick the biggest change for the least lift
I ran a workshop spanning research, design, and engineering at Merlin to validate and ideate on our designs. We checked each idea against both Merlin’s engineering capabilities and its overall business goals.
The question we kept asking was: What would create the biggest positive change for the least lift?

Then high fidelity, ready for accessibility testing
We then leveled our designs up to high fidelity and ran accessibility tests on them.



Accessibility testing
Screen reader users navigate by headings and search, so three pages became one
Sighted people scan a screen and tap what catches their eye. Screen reader users can’t scan, so they navigate in two ways: they jump from heading to heading to learn what a screen contains, and they search to go straight to what they want.
I built the prototype, and the tools to test it remotely
A clickable mockup doesn’t work with a screen reader, so I coded a working prototype with Claude Code. Testing remotely raised a second problem: I couldn’t see where a participant’s screen reader focus was. So I vibe coded a viewer that showed me their focus on screen, which let me guide people when they got lost without taking over.

We had designed date, species, and location as three separate pages. Watching people move through them with a screen reader, we realized they’d be much easier to navigate as one page with meaningful headings and search. So I combined them into a single My Recordings page.
Before testing · three separate pages



→
After Testing · one page

“[I] like the idea of mindfulness and looking at the history. Now it’s like developing a personal story on birding.”
-Blind birder
“People are gonna be blown away when seeing this. This is really cool.”
-Low-vision birder
“The intentional side and sharing side of things would strengthen the birding community.”
-Low-vision birder
Outcome
On track for spring 2027, and Merlin now designs with blind and novice birders
Merlin’s team saw the value in what we found and asked us to keep working with them on these features after the capstone ended.
A good idea isn’t enough for a small team. Merlin couldn’t take on everything we found, so I ran a workshop with research, design, and engineering to weigh each idea against their goals and what their system could already support. We chose the biggest change for the least lift, which is why this work is on track to ship instead of sitting in a report.
What I learned
Centering underrepresented users doesn’t narrow a design problem. It opens it up.
Before this project, I had never gone birding, run research with blind and low-vision participants, or facilitated co-design with mixed visual abilities in the room. On the design side, that taught me to stop treating accessibility as a checklist at the end. Watching people move through screens with a screen reader changed the structure itself: headings became navigation, search became the main way in, and three pages became one. Designs that worked by ear turned out to be clearer for everyone.

my first time birding with my team

