Picture someone on a Tuesday night, thumb moving through faces. A profile passes, another passes, a third gets a half-second pause and then passes too. Nothing about any of them is wrong. There's just no reason to stop, because nothing on the screen explains why this person rather than the one before. That pause, or the absence of it, is the whole problem.
Why a feed of faces is a weak starting point
A swipe feed is a sorting task dressed up as a choice. It asks the user to make a judgement from a photo and a few lines, with no context about compatibility and no signal about why the app surfaced this person at all. The result is a stream of low-confidence decisions: each one cheap to make and easy to regret. People don't stop swiping because they're picky. They stop because the decision never gets any easier, and a feed that never gets easier eventually feels like work.
The deeper issue is trust. When the app offers no explanation, the user assumes the ranking is arbitrary or optimised for something other than their interests. That assumption is hard to undo once it sets in.
The idea that changes the experience
What shifts the dynamic is giving the match a reason to exist. If a platform learns something real about a person first, through structured questions rather than free-text bios, it can explain why two people are being shown to each other. That explanation does more work than the match itself. It converts a guess into a recommendation, and a recommendation is something a user can accept, reject or think about, rather than just flick past.
Curated suggestions, whether from a matchmaker or a careful algorithm, add a second layer: scarcity. A short list of considered matches feels more valuable than an infinite one, and it changes how people behave. They read profiles properly. They write longer messages. The conversation has somewhere to go because the match arrived with a premise.
Safety sits alongside this. Structured onboarding and controlled access to chat give a platform ways to set expectations before contact begins, which matters for anyone who has had a bad experience on a dating app. A guided path isn't a restriction. It's what makes people willing to engage.
What a good result looks like
The signal isn't downloads. It's what happens after a match: whether conversations last, whether people meet, whether they come back. A matching system that explains itself tends to produce fewer matches and better ones, and the metrics that matter move in the right direction without the app chasing volume.
Getting there is mostly a design and research problem before it's an engineering one. The flows have to be clear enough that the quiz doesn't feel like admin, the recommendations have to feel earned, and the interface has to stay calm rather than gamified. Teams that skip that groundwork end up with a technically working app that users abandon at the same rate as everything else.
The full breakdown of how this was built, including the onboarding and quiz flow, matchmaker recommendations, match acceptance and controlled chat access, is in the Second Date case study on Foundry 5.
Top comments (0)