Dating apps have no way to surface deal-breakers before matching — you discover them on date 1 or 3

social0 views
You are a non-smoker who cannot tolerate cigarette smoke. You match with someone. Great conversation for a week. First date: they step outside to smoke. Date over. You are child-free by choice. Three dates in, they mention wanting kids. Three dates wasted. You keep kosher. They suggest a barbecue restaurant for a first date. These are not preferences — they are hard incompatibilities that make a relationship impossible. But dating apps bury them in optional profile fields that most people skip or lie about. So what? Each discovered deal-breaker costs 2-10 hours of invested time (messaging + dates). A person with 3 firm deal-breakers (smoking, kids, religion) will waste 20-50 hours per year on dates with fundamentally incompatible people. This is not about being picky — these are non-negotiable lifestyle incompatibilities. The time wasted on avoidable mismatches is time not spent meeting compatible people. Why does this persist? Deal-breaker filtering reduces the match pool. If you filter for non-smoking, child-free, same religion, same dietary preferences, your pool might shrink from 1,000 to 50 in a mid-size city. Apps do not want to show you a pool of 50 — it looks empty. They would rather show 1,000 and let you discover incompatibilities on your own time. The 'big pool' illusion keeps users subscribed. OkCupid used to have extensive deal-breaker filtering (1,000+ questions) — it was the most effective matching system ever built — and Match Group gutted it after acquisition to make OkCupid more like Tinder.

Evidence

OkCupid had 4,000+ matching questions before Match Group simplified it post-2017 acquisition. Hinge deal-breaker filters are limited to age, distance, height, ethnicity, religion, and children. Lifestyle factors (smoking, diet, political intensity, alcohol use) are profile fields but not filterable deal-breakers. Match Group 10-K does not mention match quality metrics — only engagement and subscriber metrics.

Comments