Skip to content

Show your working

The feed is an interface for engagement. The match card is an interface for trust. As dating apps come under regulatory and cultural pressure, explanation-first UIs will become normal - and "why" will become as important as "who".

Deep Dive ยท Industry   By 0xBrewEntropy - 01 April 2026 · 7 min read

The problem: a score without a reason

Dating apps make consequential choices about exposure, ranking, and timing. Most users experience those choices as mood: "today is good" or "today is dead". That is not a user experience problem. It is an accountability problem.

When the system is opaque, users cannot tell whether they are being rejected by people or deprioritised by a model. The result is algorithmic anxiety - the kind of self-doubt described in Building a Transparent Algorithm and the ethical case in The Right to an Explanation (in Dating).

๐Ÿ” Thesis: The match card is not a design flourish. It is the UI layer of accountability.

Why the UI layer matters

Many platforms already claim to be transparent: "we use your preferences". That is not transparency. It is a story. Transparency is an interface you can interrogate.

The reason the UI matters is simple: for most users, the UI is the system. If the system cannot be expressed in a card the user can read, the system is not explainable in practice.

What a match card should contain

A useful match card answers four questions in one screen:

Top signalsShared niche interests, values Q&A, mutual constraints
WeightsWhat mattered and why
ConfidenceHigh / Medium / Low with count and recency
ControlsEdit filters, hide signals, revoke integrations

Common failure modes (fake transparency)

Predictions

The likely outcome: the match card becomes normal

As the cultural tolerance for black-box ranking declines, the feed will start to look outdated. The match card will become the default surface for serious dating products: a compact, readable explanation of why someone was suggested, not just a prompt to keep swiping.

In other words: the match card becomes normal, and the new differentiator becomes whether a platform's explanation is honest, auditable, and connected to real user control.


Compatibility you can read

Affinity Atlas is built around the match card: overlap, weights, and confidence - with transparency that works in practice.

Try the demo