Why dating apps don't turn into dates
Matching was never the bottleneck. The reason a good conversation never becomes an evening out is structural, and naming the mechanism makes it fixable.
You match. You talk. It is good, actually: there is a rhythm to it, you are both funnier than you expected to be. Then it thins. A day between replies becomes three. Nobody said anything wrong and nobody decided to stop.
That is the part worth sitting with. It happens between people who were genuinely interested in each other. Whatever went wrong, it was not that one of you was not interested enough.
Matching was never the bottleneck
Every dating app is very good at the thing it can count. Matches are countable. Messages are countable. An evening where two people ate dinner and one of them walked the other to the subway is not, so it does not appear on any chart anybody optimises.
This is not a conspiracy, it is just what happens when a product measures one half of a problem. The half that gets measured gets better. You are not short of matches. You are short of Thursdays.
A conversation has no ending that produces a plan
Think about what a good conversation actually does. It establishes that you can talk to each other. That is genuinely useful, and it is also the whole of what it can do.
There is no natural point where a conversation resolves into an appointment. It can continue pleasantly and indefinitely, and every day it does is a day where both of you are getting the small reward of being liked by somebody without either of you having to be anywhere at seven o'clock. Nothing in the format pushes toward a meeting. The format is complete without one.
So the conversation does not fail. It just never converts, which from the inside feels identical.
A conversation can go well forever. That is exactly the problem with relying on one.
"We should grab a drink sometime"
Here is the sentence that ends more of these than any argument does.
It sounds like progress. It is an agreement to agree later. There is no day in it, no place, nothing either person has committed to and nothing either could be held to. Both people get to feel like the thing is moving while neither has taken on any risk at all.
And it is genuinely nice to say. That is the problem. A phrase that produces the feeling of a plan without the substance of one is very hard to stop using, because the feeling is the part you wanted.
Nobody wants to be the one who asks
Proposing something specific costs more than proposing something vague, and the cost is not evenly shared.
If you say "Thursday, this place, seven", you can be turned down on Thursday, on the place, on seven, or on you. Each of those is a small, legible rejection with your name on it. If you say "sometime", you cannot be turned down at all, because you have not asked for anything.
So both people wait, each hoping the other will absorb that. Ambiguity is comfortable for exactly as long as it takes for the conversation to go quiet, and then it is not comfortable for anybody.
And then, if somebody does ask, there is the admin
Say one of you is brave. Now you negotiate.
Which night. Which part of town. That place or the other one. Is eight too late. Two rounds of this and something has drained out of it, because you are doing calendar logistics with somebody you like but do not yet know well enough to want to do calendar logistics with. Plenty of dates die here, after both people already said yes in principle.
What a specific plan does instead
Put a real place and a real time on the table before anybody has to negotiate, and the whole structure changes shape.
There is one decision instead of four, and it is a yes or a no. Nobody has to schedule anything, because the thing is already scheduled. And the risk moves: you are not asking a person out, which is a question about them and you. You are offering an evening that exists, and they are deciding whether to come. Those feel different to send and they feel different to receive.
It also filters honestly. "Dinner at this place on Thursday at seven" is answerable by somebody who wants dinner on Thursday, and not by somebody who wanted to keep texting. That sounds like a narrower funnel and it is a narrower funnel. It is also the only kind that produces evenings.
Which leaves the question of what to propose, and the default answer is worse than it looks. There is a separate piece on first date ideas that aren't drinks and why the obvious option is the one most likely to leave you interviewing each other.
Deciding the place in advance is the safe version too
This is not a footnote to the argument, it is part of it.
Meeting somebody you do not know should happen somewhere public, chosen ahead of time, with somebody else knowing where you are. Every one of those is easier when the place was settled before you arrived instead of improvised on the night. The specificity that makes a plan easy to accept is the same specificity that makes it easy to be careful about.
What we built
Seatt is one mechanic. You post something you are already doing, at a real place, at a set time, with exactly one seat open. People ask for the seat in a line of writing. You read what they wrote with their photos blurred, pick one, and only then does a conversation open.
The order is deliberate. The plan comes first, so there is nothing to negotiate. What somebody wrote comes before how they look, because the thing you are deciding is who to spend an evening with. Plans have to be at a public venue, which the app checks rather than trusts.
It is new, free, and it opens one city at a time. If that sounds like the shape of the problem you have, it is on the App Store and Google Play, and there is more on how we handle safety if that is the part you want to read first.