Mateus Peruzzo

Brinda

Research · UX/UI · 2026


Overview

Brinda answers one question: what should I drink with this?

You type in what you’re about to eat, and you get three suggestions — the classic one, an original one, and one drawn from wherever the dish comes from. Each comes with a short note explaining why it works, because knowing why is what lets you make the next choice on your own.

The app is built for people who cook out of curiosity. Someone making feijoada on a Sunday who wonders whether there’s something better than the beer already in the fridge. Someone who has read that white goes with fish and red with meat, and suspects that’s not the whole story. You don’t need to know anything about wine to use it, and you won’t be talked down to for not knowing.

Pairing has always been guarded knowledge — passed between sommeliers, printed in books that assume you already speak the language. Brinda is an attempt to hand it over in plain words, one dish at a time.

Where it goes next

The same idea works inside a shop or a restaurant. A supermarket has a wine aisle and no one standing in it to help; a restaurant has a list and a server who may or may not know it well. Brinda could work from an actual inventory — recommending from what’s on the shelf that night, not from an ideal cellar that nobody has.

That’s the longer arc: the app in your hand first, and eventually the same knowledge available at the exact moment someone is standing in front of a shelf, deciding.


User Research

Before designing anything, I wanted to know how people actually decide what to drink with a meal — not what they think they should do, but what happens at the table. Six conversations later, most of what I had assumed turned out to be wrong.


Method

Six conversations, over WhatsApp and in person, before any screen existed. None of the participants work in food or beverage. They were in Brazil and Europe, across a range of ages, and included one person who no longer drinks alcohol.

Some are people I know. That made the conversations franker, and it narrows how far the findings generalise — worth stating either way.

I chose conversations over a survey because I wanted to hear people describe their own reasoning, not pick from options I had written for them. Quotes below are translated from Portuguese except where the participant spoke English.


What they said

They care, and they’ve given up anyway

"It matters a lot, but we set it aside because we don't know how."

"I believe it's very important, even if it's not within my reality."

Participants rated pairing as important and then described doing it only on special occasions. The gap between what they valued and what they did was the widest finding in the research.

They want the mechanism, not the answer

"What's the fundamental difference between a Merlot and a Cabernet Sauvignon? And how does that difference apply to pairing with a meal?"

"Price and knowledge — so I don't have to depend on the opinion of the staff."

All six asked to understand why a pairing works. Not to learn for its own sake: they wanted to be able to choose on their own, in front of a wine list or in a supermarket aisle.

The repertoire stops at two rules

"Knowing what works beyond fish and red meat."

Every participant described the same pair, unprompted: white with fish, red with meat. Several named it themselves as the limit of what they knew.

Non-alcoholic is underserved, not absent

"There aren't enough non-alcoholic options that aren't too sweet."

Five of six wanted non-alcoholic pairings. The complaint was not that they don’t exist — it was that the ones that do are either sugary or dull.


Pain points

  1. 1 — Interest without a route. People value pairing and give up on it anyway, because they don’t know where to start.
  2. 2 — No explanation, no autonomy. Every participant asked to understand why a pairing works — so they could choose without help next time.
  3. 3 — Suggestions they can’t act on. Price and availability decide the final choice. A technically perfect recommendation is useless if the bottle isn’t on the shelf.
  4. 4 — A repertoire stuck at two rules. White with fish, red with meat. Participants named this themselves and asked for a way past it.

What it changed

Where the three categories came from

I asked each participant which they would want: a classic pairing, an original one, or one drawn from the dish’s region. The answers didn’t converge on a category. They converged on context.

"If I'm travelling and getting to know a place, regional. In a well-reviewed restaurant, maybe the original one. At home, classic."

That is why Brinda returns all three at once instead of asking users to pick a mode. The same person wants a different answer depending on where they are — so the app stops asking and simply answers three ways.

The second pain point shaped the card itself. Because every participant asked why, the explanation is not a detail behind a tap: it sits on the card, in the second colour tier, above the origin.


Wireframes

The first structure, built on what the interviews had shown. Each pair shows the original and what replaced it after testing.

Home: o wireframe cinza à esquerda e, à direita, a tela final do Brinda com a busca e o Journal. Resultados: o wireframe com três blocos iguais e, à direita, os três cards — Clássica, Regional e Original — já com o motivo de cada um. Detalhe da harmonização: o wireframe com “add to my list” e, à direita, a tela final com Resumo, Detalhes e Ciência.

Product architecture

Brinda is built around a single action, and everything else supports it. You type a dish, you get three drinks, and the reason each one works.

Four tabs

Home is the search and the result. Almost all the time in the app is spent here.

Saved holds the pairings you wrote yourself, after the meal — the dish, the drink, and your own note on why it worked. No button on a result files one here, and that is deliberate: bookmarking a suggestion keeps you leaning on the app, while writing down what actually happened teaches you to choose. The interviews asked for the second one.

Journal is a feature of one pairing a week, photographed and written by hand, chosen from submissions. It exists because the research showed people wanted to learn, not just be answered.

Profile is the lightest of the four today: the account and its settings. It’s also where the app is headed — a place to register what’s actually in your cellar, so the suggestions come from bottles you already own.

Three answers instead of one question

The obvious design would ask what kind of pairing you want, then give you one. Brinda gives all three at once and doesn’t ask.

That came straight from the interviews. Nobody picked a favourite category — they picked differently depending on where they were. Travelling, they wanted the regional one. In a good restaurant, the original one. At home, the classic. Asking would mean making people predict their own mood; answering three ways lets them recognise it.

Preferences belong to the meal, not to the person

There’s no saved preference profile. Filters — wine, beer, cocktails, tea, juice, no alcohol — live on each search and reset afterwards.

That’s deliberate. You might be cooking for a friend who doesn’t drink, or for a table where one person does and another doesn’t. A profile would assume every meal is yours. Treating the filter as part of the question instead of part of the person keeps the app useful when you’re feeding someone else.

Where the inventory idea leads

A cellar, a supermarket aisle and a restaurant list are the same problem: a real, limited stock, and a person standing in front of it without help. The app starts by suggesting from everything that exists. The version worth building suggests from what’s actually there.

Dish Classic Regional Original Saved optional drink filter You write the note yourself One dish, three pairings, and the reason behind each

Sticker sheet

Fifty-one pieces, built from the tokens on the Colour page and the scale on the Type page. Every caption carries the measured value, not the intention.

Brand and chrome: o logo Brinda, a status bar e os cabeçalhos de Home, seção, Clássica e Minha Adega, com a tab bar nos estados inativo e ativo. Buttons: o botão primário nos estados normal, pressionado e desabilitado, mais os botões de adicionar, fechar, sair da conta e mais opções. Input and selection: campo de busca vazio e preenchido, campo de formulário, slot de foto, checkbox, switch, seletor de álcool e o ícone de filtro limpo e ativo. Chips, labels and tabs: os chips da adega ativo e inativo, o rótulo de categoria, os selos do Journal e da adega, e as abas de salvos e de explicação. Cards: o bloco de resultados normal e pressionado, cards de busca salva, de journal, de autor, de ajustes, da adega, de envio, o card de adicionar tracejado, o cabeçalho de resultados e a caixa de explicação. Loading and error: o card de carregamento, os três pontos âmbar e verde da busca, os pontos inativos do erro e o chip com erro.

Two rules

Pressed always darkens, never lightens. Every pressed state is the default tone one step down in luminance. Lightening reads as fading; darkening reads as pushed in.

Disabled exists only where the action can be unavailable. The primary button has it, because the search field can be empty. Links, chips and tabs do not — they never appear when they cannot be used, and a state that never occurs is one more thing to maintain for nothing.


Read the full interviews