The Best Way to Save and Share Places With Friends

Group recommendations have a delivery problem

Somebody in the group chat finds a place. They share it. Everybody says "ooh". Nobody can find it again eight days later, when there is finally a free evening. The recommendation was made, received, and lost — and the loss happened in the gap between "this looks good" and "here is a date".

The failure is not enthusiasm. It is that the thing being shared does not survive the chat scrolling.

Three ways people share a place, and where each one leaks

A screenshot

Fast to send, impossible to act on. A screenshot carries pixels: no address, no tappable link, nothing searchable. It also lands in everyone's camera roll instead of anywhere they would look for a plan, which means the recipient has to re-find the place from scratch using whatever text was visible in the image.

A pasted map link

Better — it is at least tappable and it has real coordinates behind it. But it is a one-shot: it opens a map, and then it is gone. There is no shared state, so five people each end up with their own copy of the same intention and no way to see that four of them are free on Thursday.

"I'll send it to you later"

The most common option and the only one with a zero success rate. It is worth naming, because a lot of sharing systems fail simply by asking for a second action later, and later never arrives.

What sharing a place should actually carry

A share that works carries four things, and most methods carry one or two:

• The place itself — a real location the recipient can navigate to, not a name they have to search.
• Why it was shared — one line of context. "For the birthday thing" is the difference between a saved place and a saved place with a purpose.
• Somewhere shared to put it. If the place lands only in the sender's list and the recipient's chat history, there is no shared object and therefore nothing to act on together.
• A path to a date. A recommendation with no route to a calendar stays a recommendation.

How this works on Blinko

Every place you save on Blinko is an object, not a message. That is the important difference. It has a location, it can carry a note and photos, and it can be shared with a link that opens the actual place rather than a screenshot of it — so the person receiving it can save it into their own collection in one tap.

From there the same object can become a plan: pick a time, invite the people, and everybody sees the same thing instead of five copies of it. Guests who do not have the app can still RSVP straight from a browser, which matters more than it sounds — the person most likely to fall out of a group plan is the one who was asked to install something first.

For families and other groups who do this constantly, a private circle keeps the sharing in one place: dinner decisions, spots worth keeping, errands split between people. It is the same mechanism, scoped to the people you actually plan with.

A shared list beats a forwarded link

The upgrade that changes group behaviour is not a better share button. It is having one list that more than one person can add to. A shared list accumulates: everybody's finds land in the same place, the good ones surface by being mentioned twice, and nobody has to remember who sent what. A forwarded link has to be re-sent every time it is needed.

If you want somewhere to start browsing together, Places is organised by city, Food & Drink gathers the restaurants and cafes, and Entertainment covers venues and things to do. Any page you land on can be saved, shared, and turned into a plan from the same object.

Start with the next one

The next time somebody in the chat finds a place, save it as a place rather than replying to it. It takes the same three seconds as typing "ooh" and it is the one version of the recommendation that will still exist next week.