Restaurant Wishlist App: What Makes One Work

Someone asks where you want to eat. You're outside the station, it's twenty past seven, and your mind is completely blank.

Which is odd, because you know there's a list. Not written down anywhere exactly, but you're fairly sure there are ten or twelve places you've been meaning to try. You could probably name three of them tomorrow afternoon at your desk. Standing here, nothing.

So you go to the Italian place again. Everyone's happy. Nothing is wrong with it, except that you've now done this eleven times.

A wishlist isn't a memory aid

That's the misunderstanding underneath the whole thing. We treat a restaurant list as something for remembering, so we optimise the saving — a faster note, a quicker screenshot, a neater folder.

The failure isn't at saving. It's at deciding.

The list has one real job: to be in front of you at twenty past seven outside the station, with enough on it that you can pick in under a minute. Everything else is filing.

Once you look at it that way, the reason your current system doesn't work gets a lot clearer — and each of the usual ones breaks at a different point.

Three systems, three different failures

The notes app fails at retrieval. Capture is genuinely fine. You type "Rondo, Dalston, apparently the lamb" in eight seconds and it's there forever. But the note has no location attached, so it can't reach you. A list that can't tell you it's four minutes from where you're standing isn't a wishlist. It's a diary.

The camera roll fails at everything after the shutter. Screenshotting a restaurant is the fastest save there is, which is why everybody does it. Then it lands in a stream of nine thousand images between a photo of a parking bay and a picture of your friend's dog. Six weeks later you're scrolling by date, trying to work out which week it was. Some of it is searchable now — just not the part you need, which is why it was on your screen in the first place.

A star on Maps fails at meaning. This one is closest, and it's where most people end up. Retrieval is good: it's on a map, it knows where you are, it survives a new phone. What it doesn't do is tell your saves apart. Every star is the same star. The place a colleague raved about for ten minutes, the place you half-noticed walking past, the place you saved for one specific dish, the place that's only good at lunch — same pin, same colour, no note, all flattened into "starred". It also needs the restaurant to already exist in the database, which quietly rules out the pop-up, the market stall and the one that opened last month.

There's a fourth habit worth naming: the message you send to yourself, or the link a friend drops in the group chat. That isn't a save. That's a hope.

What the list actually needs on it

Four things, and it's fewer than people assume:

1. Where it is. Not the address — the ability to see it on a map, and to notice it when you're near. That's the entire retrieval half.
2. Why it's on there. One line. "Priya, the dumplings." "Good for six." "Only worth it at lunch." Without this you open the list and can't tell your own saves apart.
3. When you'd go. A Tuesday-after-work place and a somebody's-birthday place are not interchangeable, and a flat list makes you work that out again every single time.
4. A way to make it smaller. Twelve options is a decision. Sixty is a wall.

Everything else these apps tend to grow — star ratings, price bands, cuisine tags — is optional, and mostly goes unused.

How this works in Blinko

Saving a restaurant makes it a Spot: the photo, the map pin and a note about why it's there, in one card. The note does the heavy lifting later. It costs ten seconds and it's the difference between a list you can read and a list you can only stare at.

The map view is the retrieval half. You can look at what you've saved near where you're actually standing, which is the exact question you have outside the station at twenty past seven.

Collections handle the shrinking. Instead of one long list called "restaurants", keep a few short ones organised by occasion — the weeknight ones, the ones that work for a group, the ones you're saving for when someone visits. When the question comes, you open one of them and you're choosing between four things rather than sixty.

And if the wishlist is really a shared one — you and a partner, or you and the two friends you eat with most — it can live in the conversation as a list you can both add to and tick off, rather than a document one of you owns and the other never opens.

Blinko is free on iOS and Android, on a free forever plan.

The bit everyone skips

Prune it.

A wishlist grows and never shrinks, and after two years it's mostly archaeology: places that closed, places you went to and forgot you'd been to, places you saved during a phase. Every few months, go through and delete anything you can't defend in a sentence.

Fifteen places you'd be genuinely pleased to end up at beats eighty you're slightly afraid to open. The point was never to collect restaurants. It was to stop going to the same one on autopilot.

Start with the next one someone mentions — and write down who mentioned it, because that turns out to be the most useful line on the card. And once five or six of your saves land in the same part of town, you've got the makings of an evening or an actual itinerary rather than a single booking.

Read next: The Best App to Save Places You Discover — everything beyond restaurants, and how the save itself is put together.

See what Blinko Spots does →