How to Organise a Beach Bonfire That Moves

Mo says he's five minutes away. Mo is not five minutes away. Mo has sent a photograph of a bin, as though a bin is information.

We're on the beach past the second car park, the bit where the sand goes shingly, by the low wall you can lean the bags against. Which is an extremely precise location if you have ever been here, and completely useless if you haven't.

That's the beach problem. No address. Barely a landmark. "Past the second car park" survives about four people before it collapses into blurry photos and increasingly clipped voice notes.

Which is a shame, because the evening itself is easy. What's hard is the bit between deciding to do it and everyone actually standing round the same fire: the plan, the pin, and the people.

And then, obviously, you move

Nobody tells you this bit when they suggest a fire on the beach: you will not stay where you started.

Around nine someone goes for a wander and comes back saying there's a better spot two hundred metres down. More driftwood. Less wind. Further from the family with the speaker. So you shift — bags, blanket, the disposable barbecue nobody has admitted is not working — and every person still walking towards you is now walking towards a patch of sand where you used to be.

The texts start again. Are you still by the wall. I'm at the wall. There is nobody at the wall.

A pin you can move

Not a map link. A map link is one moment frozen in amber; you drop it once and it's wrong the second you shift.

Not a description either. You tried a description. It produced Mo and his bin.

What the night needs is a pin that says here, that changes when here changes, and that anyone coming can just look at without asking you.

That's a Live Beacon. You publish it stood where the fire's going to be, it pins you, and it gets a page and a link. Send the link into the chat once. When you shift down the beach, you open it and tap I've moved — update my pin, and the pin lands where you're stood now.

One tap. No setup, and nothing you have to remember to switch off later.

Be honest about what that is

It's a snapshot. Each tap takes one reading of where you are and puts it on the page. It doesn't draw a line behind you. Nothing is crawling across a map while you carry firewood about.

And for a bonfire that's the right shape, not a watered-down version of a better thing. Nobody at this fire needs a trail of your evening. They need a current answer to where. Those are different questions, and only one of them is anybody's business.

People see how fresh it is in plain words: Live · updated 12 min ago. Two minutes, they walk. Forty minutes, they text you, because you've probably moved and not re-pinned, and forty-minute-old sand isn't where you are.

There's a version of this that streams your position and never goes stale. Easier to build, easier to explain, and it also never stops. The person it's broadcasting about is always the one least likely to be thinking about it at eleven at night on a beach. A pin that goes stale is a problem you fix with a tap. A thing that never stops isn't a problem you can fix at all.

Nobody's phone goes off

People assume the opposite, so it's worth saying: nothing is sent to anyone.

Someone following the Beacon sees the new pin the next time they open the app. That's the entire mechanism. No buzz in a pocket, no alert sliding in mid-conversation.

Slightly less convenient than a broadcast. Much better on a night out, when the last thing anyone needs is their phone doing things at them unprompted. People check when they want to know, and they want to know when they're walking.

Publish it before you leave the house

Small thing, quite useful. The Beacon doesn't have to wait for the night to start, since you can follow one from the moment it's published, not from the moment it kicks off.

So pin the rough spot in the afternoon, send the link, and people can follow it in advance. Then when you get there and the fire ends up thirty metres from where you imagined, you re-pin and it's simply right. Nobody has to be re-invited.

Same for the maybe-person who decides at ten that they will after all. They've already got the link. They open it, they get the current pin, they turn up. Nothing had to be relitigated in the chat.

The actual fire bit

Check the council rules where you are. They vary enormously and some beaches will fine you.

Above the high tide line, well away from dunes and dry grass. Bring water. Actually bring it, a bottle of water is not water. And don't bury it and walk off, because hot sand stays hot for hours and the person who steps in it tomorrow is barefoot and about eight years old.

Driftwood is fine if it's properly dry. Pallets are fine if they're clean and not the treated blue ones. Take the ash out with you in the morning.

None of that is an app problem. It's just the part everyone skips.

Who's bringing what

Somebody has to bring the things.

If it's a small crew and you know exactly who's in, a Plan is the better shape for that half of it: a guest list, a time, RSVPs, and a check-in when people arrive. Beacon for where, Plan for who. Most bonfires are both: a Plan for the six doing the shopping, a Beacon for the wider orbit who'll drift down after the pub. That split is the same one behind inviting people to a gathering without a social platform.

If it becomes a habit rather than a one-off (a summer thing), the people who keep turning up end up in a Group, which is where the next one gets sorted without anyone starting a fresh chat. That's the same front-door-and-back-room arrangement that makes a university society survive past its first meeting.

And if the thing you're doing is the opposite of come-one-come-all, say a gig in someone's basement or a night that would be ruined by forty strangers, the Beacon still works, but what you leave switched off matters more than what you switch on.

What the Plan half looks like from their end

Worth being specific about that half, because people assume it needs everybody on the same app.

It doesn't. You make the plan with a time, a place and the handful of names you're actually catering for, and the share sheet hands you prewritten invites for Messages or WhatsApp. You send them. From your phone, from your number. Nothing goes out from Blinko, and nobody's number gets typed into anything.

Your friend taps the link and it opens in a browser. The what, the when, the where, two buttons. They say yes with a first name. No install, no account, no password, which is the entire difference between eleven replies and six replies plus a round of chasing texts on Friday.

Then the numbers do the counting you'd otherwise do by scrolling. Going, maybe, moving as they land. Sunday afternoon you know you're buying for nine rather than "nine-ish, unless Priya's brother comes". There's an add-to-calendar file as well, and it isn't a snapshot: shift the fire from seven to half eight because of the tide, and the entry sitting in their calendars shifts with it.

Twenty-five is the ceiling on a plan, which is more people than any beach fire ought to have.

So the night runs on two links doing two different jobs. The Plan link goes out nine days early to the six doing the shopping, and answers who and when. The Beacon link goes to the wider orbit, gets re-pinned when you shift down the sand, and answers where. Nobody has to pick between them, and neither of them lives in a chat that's already forty messages deep by Thursday.

Blinko Spots is free. All of it, no tiers.

Mo still won't be five minutes away. But he'll be twenty minutes away from an accurate pin, which is a meaningfully better class of problem.

Capture the spot, plan the night, get everyone there, and keep the one that turns out to be the summer's best. Never lose a moment.

See what Blinko Spots does →