Shareable Restaurant List: Send Friends the Real One
Somebody is going to Lisbon and asks where to eat. You send eight names in a message, they lose it in the thread, and three weeks later they ask again. A shareable restaurant list is the fix, and the version most apps ship is not quite it.
This is what makes one actually useful, who should be able to see it, and the honest limit of the approach we take.
Why a shareable restaurant list beats a list of names
The problem with eight names in a message is that it strips out everything that made them worth sending. Your friend gets the where and not the what: not which dish, not whether you would go back, not that one of the eight is only good at lunch.
So they arrive, look at a menu with no idea what you ordered, and pick wrong at a place you loved. The recommendation technically arrived and none of the useful part survived the trip.
A list built from reviews carries all of it: the dish, the rating, the note you wrote at the table. That is the difference between sending a list of restaurants and sending an actual recommendation.
How collections work
In Crumble a collection is a named set of your own reviews, with an emoji and a description if you want them. "Honeymoon 2026", "Lisbon", "cheap lunch near the office". It can span any number of cities and countries, so a collection is not tied to one place the way a city page is.
You add reviews you have already written, which is the constraint that makes it worth reading: everything in a collection is somewhere you actually went and rated. There is no way to pad it with places you have only heard of.
Removing a review from a collection removes it from the collection only. Your review, and the visit it records, stay exactly where they are.
Who can see it
Three settings, and they do different jobs:
| Visibility | Who sees it | Use it for |
|---|---|---|
| Friends | Anyone you are friends with, from your profile | The default. Your Lisbon list, findable by the people most likely to want it |
| Private | You, in the app | A shortlist you are still building, or a list that is nobody else's business |
| Specific friends | Only the friends you explicitly grant | The list for the four people on the trip, not the whole friend list |
One thing to be clear about, because it is the sort of thing people assume wrongly: a share link works regardless of the visibility setting. Marking a collection private stops it appearing on your profile, and it does not retroactively kill a link you already sent. If you want a link to stop working, deal with the link rather than the visibility.
What we do not do: collaborative lists
Being straight about this, because it is the main thing people want from the phrase and we do not do it. A Crumble collection is yours. Friends cannot add to it.
Several apps do exactly that. Spotlist describes inviting friends to collaborate on a list and add spots side by side. Nomblr describes inviting friends to build a shared list together. Resy ships shareable lists you send by text or email. If co-editing is the feature you are looking for, one of those is the right tool and this is not.
The reason we went the other way: a collaborative wishlist fills up with places nobody in the group has been to. That is useful for planning and it is a different object from a record of what was good. Our collections trade the co-editing for the guarantee that every entry is a first-hand rated visit, which is what makes the list worth acting on rather than worth discussing.
If what you want is a shared pile of places to try, that is what a wishlist is for, and our guide on restaurant lists for couples covers the two-person version of the same problem.
Collections against the alternatives
| Notes app or chat | Collaborative list app | A collection | |
|---|---|---|---|
| Says what to order | Rarely | Sometimes | Yes, per dish |
| Everything is first-hand | No | No | Yes, by construction |
| Friends can add | Yes | Yes | No |
| Survives the thread | No | Yes | Yes |
| Per-friend access | No | Varies | Yes |
The honest read of that table: a collaborative app wins on planning, a collection wins on recommending. Most people who eat out a lot end up wanting both, and they do not conflict.
Lists worth actually making
- One per trip. "Lisbon 2026" is the single most requested thing you own and the easiest to send twice.
- The near-work list. Boring, and it is the one you use most.
- The when-someone-visits list. Four places, ranked, ready. It saves you rewriting the same message every time.
- The occasion list. Places worth a birthday. Short by definition, and the one you cannot reconstruct under pressure.
- Not: a list of everywhere you have been. That is your map, and it already exists.
Where it fits
A collection is the curated layer. Underneath it your food passport is the automatic one, filling with countries and cities as you eat, and at the end of the year the whole thing turns into a recap. The passport records what happened, the collection is what you chose to say about it.
Frequently asked questions
How do you share a restaurant list with friends?
In Crumble you make a collection, a named set of your own reviews with an optional emoji and description, and either leave it visible to friends, keep it private, or grant access to specific friends. You can also send an explicit share link. Because it is built from reviews, whoever opens it sees the dish and the rating rather than just a name.
Can friends add restaurants to my list?
No. A Crumble collection holds your own reviews and is shared read-only, which is what guarantees every entry is somewhere you actually went and rated. If co-editing is what you want, apps like Spotlist and Nomblr are built around inviting friends to add to a shared list, and they are the better tool for that job.
What is the difference between a collection and a wishlist?
A collection is places you have been and rated, curated to send to someone. A wishlist is places you have not been yet, and it clears itself when you finally go and log the visit. One is a recommendation, the other is an intention.
Can I share a list with only some of my friends?
Yes. Alongside friends-visible and private, a collection can be set to specific friends, where only the people you explicitly grant can see it. That is the setting for the list that belongs to the four people on the trip rather than to everyone you know.
Does making a collection private disable a link I already shared?
No, and it is worth knowing. Visibility controls whether a collection shows up on your profile for friends. An explicit share link works regardless of that setting, so if you want a link to stop working you have to deal with the link itself rather than changing the visibility.
What should I put in a shareable restaurant list?
One per trip is the highest-value list, since it is the thing people ask you for repeatedly. After that: the places near work, a short ranked list for when someone visits, and the small set worth a birthday. A list of everywhere you have ever been is not a list, it is your map.