How to Keep Track of Restaurants You Want to Try

It is a list problem, not a memory problem

Most people who say they are bad at remembering restaurant recommendations are not bad at remembering. They are keeping four half-lists. There are three names in a phone's Notes app, two screenshots buried in a camera roll, one place starred in a maps app eighteen months ago, and a text thread where somebody said "you have to go here" with a link nobody opened.

None of those four is wrong. The problem is that there are four. A wishlist only works if there is exactly one of it, and if adding to it is faster than deciding whether to add to it.

The four jobs a restaurant list has to do

Before choosing a tool, it is worth being precise about what you are asking it for. A wishlist that works does four things:

• Capture in seconds. The recommendation arrives mid-conversation. If saving it takes longer than the sentence that produced it, you will not do it.
• Hold context, not just a name. "Rosa's" is useless in six months. The neighbourhood, roughly what kind of food, and who recommended it are what make the entry findable later.
• Answer a location question. The moment you actually need the list is when you are standing somewhere with an hour free. The useful query is not "show me my list", it is "show me what I saved near here".
• Separate want-to-try from already-loved. These are two different lists doing two different jobs, and merging them is what turns a wishlist into an archive nobody reads.

Capture at the moment of recommendation

The single highest-leverage habit is saving while the other person is still talking. Not after dinner, not "when I get home" — during. This sounds small and it is the whole thing: a recommendation captured in the moment has a name attached to it, and a recommendation captured later usually has nothing attached to it, because the details went first.

Save first, organise never

Resist the urge to categorise on the way in. Tagging, rating and sorting are jobs for the moment you are choosing where to eat, not the moment you are hearing about a place. Every extra decision at capture time is a reason to skip capturing. Save the place, keep talking, sort it out when it matters.

Make the list answer the question you actually ask

A flat text list fails at exactly the moment you need it, because the question you ask on a Thursday evening is geographic. "What did I save near here" is not something a Notes file can answer, and it is the only question that reliably converts a wishlist into a meal.

This is the practical reason to keep the list somewhere that knows where places are. Once each entry carries a real location, the list stops being a memory aid and becomes a decision aid — and browsing it is genuinely pleasant instead of a chore.

Two lists, not one

Keep "want to try" and "loved it" apart. The want-to-try list is a queue: things go in, things come out, and it should feel like it is moving. The loved-it list is a reference — the places you send other people to, the reliable Tuesday dinner, the one you book for birthdays. Mixed together, the queue never empties and the reference never gets used.

A simple rule works: the first time you go somewhere, move it out of the queue. Whether it lands in the reference list or nowhere at all is the review.

How this works on Blinko

Blinko Spots is built around the first job — the three-second save. A place goes in with one tap, geotagged, and it shows up on a map without you doing anything else to it. Because saving is that cheap, the habit survives contact with real conversations, which is the part every other system loses.

Everything else follows from having one honest list. The map view answers the location question. Plans and shared lists turn "we should go" into a date. And when you want ideas rather than a memory, the browse surfaces are the front door: Food & Drink gathers the restaurants, cafes, bakeries and bars with pages on Blinko, Dishes is the same corpus organised by what people actually ate, and Places groups everything by city so you can start from a town rather than from a category.

Start with one list, today

You do not need to migrate the four half-lists. Start the single list with the next recommendation you hear, and let the old ones decay. Within a month the new list is the real one, because it is the one with recent things in it — and recent things are what you actually want to eat.