Serendipity is a terrible thing to try to design for. By definition, it's unplanned. It's the unexpected thing that turns out to be exactly what you needed. The moment you start engineering it, you risk destroying it.
And yet — that's essentially what we've been trying to do with Meetley from day one. We've been trying to build a product that creates the conditions for serendipitous connection without turning it into a performance or an algorithm. Here's what we've learned.
The trap of the perfect match
The obvious approach to a social app is to build a matching engine. Input your interests, age, location, preferences — and get served people who are statistically likely to be compatible with you. Dating apps do this. Most networking apps do this. LinkedIn's "People You May Know" does this.
The problem is that the people most worth knowing are rarely the ones an algorithm would have predicted. Your best friend probably doesn't share every interest you do. The mentor who changed your career probably came from a completely different field. Serendipity, by nature, defies prediction.
"We didn't want to build a better filter. We wanted to build a better room."
So we made a deliberate choice early on: Meetley would not try to match individuals to individuals. Instead, it would match individuals to moments — events, trips, gatherings — and let the people find each other inside those moments.
The five design principles we worked from
Proximity over preference
The map is the primary discovery surface, not a feed sorted by relevance score. What's near you is what you see first. This biases toward people who share your physical context — your neighbourhood, your city — which is the most reliable foundation for a real-world relationship.
Show who's going, not who you'd like
When you view an event, you see the attendee list before you RSVP. Not a "people like you are going" recommendation — the actual humans who signed up. This creates a pull dynamic: you go because of the people, not in spite of not knowing them.
Friction at the right moments
We deliberately made some things slightly slower. Sending a connection request requires a short note. Joining a trip group requires reading the host's description. These micro-moments of intentionality filter for people who actually want to be there.
Notifications that pull, not push
We send far fewer notifications than most apps our size. When we do, it's for things that genuinely warrant interruption: someone you connected with is going to an event near you, or a trip you expressed interest in just got a new spot. We never send engagement bait.
The app disappears after the moment
We don't try to own the relationship after the event. The group chat persists, connections transfer to your contacts — and then Meetley gets out of the way. The app is a launchpad, not a destination.
What we're still figuring out
None of this is fully solved. We're still learning how to surface the right events to people who are new to a city. We're still thinking about how to make the first message in a new connection feel natural rather than forced. We're still watching to see whether the people who met on Meetley a year ago are still in each other's lives.
But the early data is encouraging. Connections made through shared Meetley events have a meaningfully higher rate of continued contact than cold connection requests. People who go to events together come back to the app more — not because they're addicted to scrolling, but because they've found a reason to show up again.
Serendipity can't be designed. But the conditions for it can. That's the whole project.
