


Whspr: Crowdsourced urban intelligence platform for women
- Role
- UX Researcher • Product Strategist • Prototyping • Visual & Interaction Designer
- Platform
- Mobile Application
- Timeline
- 4 months | Jan to May 2026
What is Whspr?
My Role
Context
Women already share knowledge about places all the time. Before going somewhere new, they'll text a friend, check a neighborhood subreddit, or read reviews to get a sense of what a place is actually like. But that knowledge is scattered and it disappears fast. It lives in group chats and comment threads, and none of it is anywhere you can actually find when you need it.
There's no interface designed to support collective sensemaking around women's perceived safety in public spaces.
Research
Where the knowledge lives today
Down the side: whether you know a woman is speaking from experience. Across the top: how far what she said can travel.
- Nextdoor
- Yelp
- Citizen
- AWDTSGAre We Dating The Same Guy
- Discord
- TikTok
- iMessage
- Word of mouth
I began by researching why women still resort to the whisper network in the age of apps, then went out and asked them. Three patterns kept coming back.
Before she goes out
Three patterns from the interviews, and the research behind each.
Wonder if any of my friends have been here before? Let me text the chat.
The knowledge exists, and it disappears
Damn, Citizen makes me scared to even leave my home.
Tools amplify fear, or flatten it into a score
Is it safe to go here alone at night?
Safety depends on context: the time, the crowd, who you are
The Insight
I set out to build a safety tool. The research told me I was solving the wrong problem.
Women weren't asking for another app to warn them about danger. They already had that, and it wasn't working. What they wanted was the thing they were already giving each other in group chats: a sense of what a place actually feels like, at a certain time, for a certain kind of person.
So I stopped designing a safety app. Women already notice things, tell each other, and warn each other. What they don't have is somewhere for all of that to live after the group chat moves on.
Design Decisions
Four decisions, each one traced back to the research.
01
No star ratings
Not a 1 to 5 score, like every other review platform
Knowing what to expect is what makes a new place feel okay, and a rating can't tell you that. It squashes everything into one number and loses the stuff you actually want to know: what the crowd was like, how the staff treated you, whether you'd go alone. So you leave a short first-hand account instead, tagged with the time you were there.
No stars anywhere
House of Yes, read through what women said about it, each account tagged with when they went.

02
A day/night toggle
Not one profile per place, averaged across every hour
Somewhere well-lit and full of people at 6pm can feel completely different at 1am. Whspr keeps the two apart and lets you switch between them, so what you read matches the time you'll actually be there.
Same place, different time
Schmuck at 6pm and at 1am. Same bar, different accounts.


03
Verification, without surveillance
Not open posting, or an account tied to a real identity
This only works if the people posting are actually women. But the moment you ask for ID, people get nervous about posting at all. So I kept the two apart. You're verified once, when you sign up. After that your posts are anonymous, and nothing personal gets stored.


04
Friction as a feature
Not an open text box, or a one-tap rating
You answer 5 prompts before you can post: have you been before, when you went, were you alone, what it's about, and then what happened. A few extra seconds from the person posting saves the next woman from guessing.
When I asked one woman whether other people's experiences change where she goes, she said, “It depends what the experience was, if it was a staff member that made the experience bad, or if it was just someone who was there.” That difference is exactly what a star rating throws away, and it's what the prompts are there to capture. The cost is that posting takes longer, so whether people keep doing it at scale is the first thing I'd test next.
The contribution friction model
5 prompts before you post, and what they turn into.
What you answer
- 1Have you been here before?
- 2When were you there?
- 3Were you alone or with people?
- 4What is it about?
- 5What happened? Type it or say it.
What the next woman reads
Schmuck, East Village
“Gets loud after 10pm, but it's easy to get a cab after midnight.”
A star rating would have said 4.2. This says who went, when, and what it was about.
How it fits together
What one woman posts reaches the next one who searches.
Two rules that keep it honest
Old posts fade. After 6 months a post dims, because a bar can change a lot in a year.
Thin places get flagged. Under 4 accounts, a place carries a warning, so 2 people can't define it.
The design system
Whspr runs on a dark, calm interface, built to feel like a quiet resource rather than an alarm. A Midnight base, a single Signal Amber accent, and DM Serif Display paired with DM Sans.
Midnight
#07080A
Surface 1
#1A1A24
Surface 2
#252533
Signal Amber
#FF8830
Amber Dim
#CC6F00
DM Serif Display
DM Sans: body, labels, captions
The Product



This is the working prototype, so go ahead and use it. Search a place, read what other women said about it, or post something yourself.
“The interface had to do two things at once: let someone post what a place was like, and let someone else read it to decide whether to go. The whole design keeps those two jobs working together without letting either one flatten the other.”
You search a place and see what other women experienced there, tagged with when they went and what kind of visit it was. There's no score and no crime feed, only people who were actually there.
Where it landed
Washington Square Park, after dark
Testing the prototype in the kind of place these decisions actually get made. 10 women, 7 conversations, mostly on park benches.
To test the concept I took it out around Washington Square Park and the West Village. I talked to 10 women across 7 short conversations, plus 2 long-form interviews. Each street conversation followed the same order, suggested by Professor Bloom: validate the problem first, show the prototype second, ask about use last. That way people named the problem in their own words before they ever saw my solution.
What came back
Ten women across seven street conversations, plus two long-form interviews.
6/7
Word of mouth decided whether they went
“If someone I know has an opinion about it, that's the number one thing.”
7/7
No pushback on the women-only framing
2/10
Wouldn't use it without a clear reason to choose it over reviews
“It's nice if there's something that makes it more specific.”
1/10
Wasn't sure she'd stop to post while out
“I don't know how often I'm going to post.”
Both
Long-form interviews named time of day, unprompted
“Even just knowing what time of day a place is really, really busy.”
Every
Platform named was described as untrustworthy, not empty
“I question the trustworthiness of Reddit users as well.”
Outlined cards are the findings that argued against the concept.
The premise held up. Women already share this stuff, so I didn't need to invent a new behavior, just give it somewhere to go. And the problem was never a lack of information. People just didn't trust where it came from.
The two who said no were right about something. One asked straight out why she'd use this over reviews. The other doesn't own a smartphone, but while ruling herself out she described exactly who Whspr is for: someone new to the city, without a list of places she already trusts. Between them they scoped the product better than I had. Whspr is for people going somewhere they don't know yet.
“If you've never been in an environment like that, how do you trust your instinct?”
Interview participant
What I'd do next
From places to routes. Nobody was asked what else Whspr should do. Getting home came up anyway, from more people than any feature I actually designed. For one woman, the trip home mattered more than anything about the venue. A Whspr layer over the map, where women could leave and read feedback along a route, is the most-requested thing I didn't build.
What they asked for, unprompted
Nobody was shown these or asked about them. People brought them up on their own, across 10 street conversations and 2 long-form interviews.
Getting home safely (the route, not the venue)
one called it her biggest factor
2 people
Age policy: 18+ vs 21+, and filtering by it
2 people
Queer-friendliness
one long back-and-forth, one agreement
2 people
Events, like karaoke night or a poetry slam
2 people
Cost and cover charge
1 person
Whether the venue confiscates pepper spray
1 person
“Will people here look out for me”
1 person
These are small numbers, and the chart doesn't pretend otherwise. The point is that more people brought up getting home than any feature I actually designed.
Verification and inclusion. The verification I designed confirms identity but raises real questions I didn't resolve. Selfie and pose-based checks shut out low-vision users, and gender verification gets complicated fast for trans women, who Whspr is meant to include. I'd want to talk to both groups before building any of it.
Trust at scale. A platform built on contributions is only as trustworthy as the people contributing. Guarding against coordinated manipulation and astroturfing is something I'd need to design for before this could be real.
What I took away
Women already know this stuff. The apps around them just don't treat it as real. Whspr made me notice how much the default choices, like a star rating or a crime map, decide whose experience counts. Saying no to those defaults was the part of this project I cared about most.
