Meetzy

There is no shortage of things to do. There is a shortage of someone to do them with. People scroll past a concert, a match, a table at a café, and decide against it — not because the event was wrong, but because going alone was.

So Meetzy is not built around events. It is built around the person you would be sitting next to. Everything in the interface exists to answer one question earlier: would I want to spend an evening with whoever is behind this.

Discovery starts from mood rather than category. You say what kind of evening you are after — something quiet, something social, something active — and the app narrows from there. It is a smaller question than "what do you want to do", and people answer it faster.

From there, distance does the rest of the filtering. Events are listed by how far away they actually are, down to metres, and the same set is available on a map. Nothing is more than a couple of taps from the point where you decide.

You do not simply appear at someone's table. Every event has a host, and joining is a request that the host accepts — which is the difference between an open listing and a social product people are willing to use.

That single decision pulled a lot of the system behind it: requests and their states, notifications on both sides, the profile that has to be good enough to say yes to.

A profile here is not a photo and a bio. It is structured: how someone communicates, how they live, what they do at weekends, what they are into. Enough to make a judgement, laid out so the judgement takes seconds.

The screens in this case study have their users' names and faces removed. That is not a design flourish — real people are in there, and none of them agreed to appear in a portfolio.