Let's Join
  • Friend codes
  • Onboarding
  • First ping

Brunch Friend Code Invites Using a Friend Code

The code is the handshake; the ping is the plan. This is the operational path from characters on a screen to eggs with someone you already know.

Handshake, then plan.

How Let's Join fits

Friend code → ping → meet IRL

  1. Grow the graph with codes

    Share a six-character friend code with someone you already know. Redeem creates instant friendship—no stranger discover in shipping UX.

  2. Ping brunch with audience

    Place plus time, or Let's Decide. All friends, Close friends, or a list—plus FoF on or off for this invite only.

  3. RSVP, lock, meet

    Keep hangout chat thin. Host locks time when ready. Open plans that never settle cancel seven days after create.

Why it matters

What a friend code is—and is not

A friend code is six characters, one per person, no reset theater. Share it with someone you already know offline; redeeming creates instant friendship in the graph.

It is not a dating handle, not public discover, not a capacity ticket. Shipping UX grows known graphs; city-radius stranger feeds stay out of live product even if backend waits phase two.

First friend is mandatory before core feed—brunch inviting assumes at least one node beyond you.

Phone verify—five-minute OTP, one resend—is separate from Cognito email login. Verify before mutating plans if gates apply.

Code redeem is handshake; brunch needs the ping footstep next.

In Marseille, Sora told the group that friend code invites using a friend code only works when the invite matches real life: place pinned, audience named, and an end time that lets bodies breathe. The morning of section 1—"What a friend code is—and is not"—Sora almost bailed until the ping said FoF off and Close friends only. That clarity was the social lubricant.

Todd still talks about the brunch where a dog sat between chairs like a hired mediator. Phones went face-down while rolls cooled. They measured the win in shared minutes, not in stories they would post for strangers. The graph was people they already knew—redeemed by six-character codes, not a discover feed. When coordination stayed thin, the room could hold actual news about friend code invites using a friend code.

Walking back through Marseille, Sora drafted the next ping while cheeks were still warm: same scale, rotated host, honest list. If time stayed open, someone would lock before seven days turned the plan into guilt. Unfriend or list changes would drop people from upcoming pings without a public exit speech—boundaries as mechanics, not theater. That is how friend code invites using a friend code becomes a habit instead of a hope.

Circle brunches stay friendship logistics: no capacity theater, no ticket metaphor. For friend code invites using a friend code, section "What a friend code is—and is not" is where that habit becomes visible: place plus time—or Let's Decide until someone locks—plus audience named on the ping. Friend codes grew this graph; first friend is still the gate before the feed opens.

RSVP on the ping so hosts buy food for humans, not for maybe-reactions. That combination is why friend code invites using a friend code can repeat without turning into guilt theater. Close friends stays undeletable; custom lists slice contexts; all-friends broadcasts stay rare when tenderness matters. The app will not manufacture strangers for your table—six characters, instant friendship, no code reset.

From redeem to first brunch ping

After redeem, send place plus time, or Let's Decide with lock owner named. Audience on ping: all friends, Close friends, custom list, FoF on or off for this invite.

Starter first ping: coffee near redeem friend, sixty minutes, honest end—prove logistics before fantasy brunch.

Hangout chat for buzzer; RSVP on object.

Unset open cancels seven days—fine for tentative first plans.

Host locks when window visible—leadership welcome even among new graph edges.

In Marseille, Sora told the group that friend code invites using a friend code only works when the invite matches real life: place pinned, audience named, and an end time that lets bodies breathe. The morning of section 2—"From redeem to first brunch ping"—Sora almost bailed until the ping said FoF off and Close friends only. That clarity was the social lubricant.

Todd still talks about the brunch where they left before the crowd arrived. Phones went face-down while rolls cooled. They measured the win in shared minutes, not in stories they would post for strangers. The graph was people they already knew—redeemed by six-character codes, not a discover feed. When coordination stayed thin, the room could hold actual news about friend code invites using a friend code.

Walking back through Marseille, Sora drafted the next ping while cheeks were still warm: same scale, rotated host, honest list. If time stayed open, someone would lock before seven days turned the plan into guilt. Unfriend or list changes would drop people from upcoming pings without a public exit speech—boundaries as mechanics, not theater. That is how friend code invites using a friend code becomes a habit instead of a hope.

Repair after a miss should fit in one ping, not a group-chat memoir. For friend code invites using a friend code, section "From redeem to first brunch ping" is where that habit becomes visible: place plus time—or Let's Decide until someone locks—plus audience named on the ping. Friend codes grew this graph; first friend is still the gate before the feed opens.

RSVP on the ping so hosts buy food for humans, not for maybe-reactions. That combination is why friend code invites using a friend code can repeat without turning into guilt theater. Close friends stays undeletable; custom lists slice contexts; all-friends broadcasts stay rare when tenderness matters. The app will not manufacture strangers for your table—six characters, instant friendship, no code reset.

Who to code first for brunch culture

Pick someone who already ate with you IRL—code cements digital coordination onto real trust.

Close friends list membership comes after friendship exists; code creates friendship edge first.

Avoid mass-code spraying to acquaintances—graph quality beats count for brunch repeat rate.

Custom lists arrive later when you slice brunch subgroups.

FoF off on first pings—surprise hops confuse new rhythm.

In Marseille, Sora told the group that friend code invites using a friend code only works when the invite matches real life: place pinned, audience named, and an end time that lets bodies breathe. The morning of section 3—"Who to code first for brunch culture"—Sora almost bailed until the ping said FoF off and Close friends only. That clarity was the social lubricant.

Todd still talks about the brunch where the table finally felt like friendship again. Phones went face-down while rolls cooled. They measured the win in shared minutes, not in stories they would post for strangers. The graph was people they already knew—redeemed by six-character codes, not a discover feed. When coordination stayed thin, the room could hold actual news about friend code invites using a friend code.

Walking back through Marseille, Sora drafted the next ping while cheeks were still warm: same scale, rotated host, honest list. If time stayed open, someone would lock before seven days turned the plan into guilt. Unfriend or list changes would drop people from upcoming pings without a public exit speech—boundaries as mechanics, not theater. That is how friend code invites using a friend code becomes a habit instead of a hope.

Rotating who sends the invite teaches the circle that belonging is mutual labor. For friend code invites using a friend code, section "Who to code first for brunch culture" is where that habit becomes visible: place plus time—or Let's Decide until someone locks—plus audience named on the ping. Friend codes grew this graph; first friend is still the gate before the feed opens.

Measure the month in shared minutes with known faces—not in how wide you broadcast. That combination is why friend code invites using a friend code can repeat without turning into guilt theater. Close friends stays undeletable; custom lists slice contexts; all-friends broadcasts stay rare when tenderness matters. The app will not manufacture strangers for your table—six characters, instant friendship, no code reset.

Mechanics the product already enforces

Unfriend silently removes upcoming pings—clean edges when codes were mistakes.

List remove same kick—no public chat exit theater.

Circle pings no capacity field—size via audience.

Notifications follow audience choice on each ping.

Public discover not mounted—codes remain friends-only growth path now.

In Marseille, Sora told the group that friend code invites using a friend code only works when the invite matches real life: place pinned, audience named, and an end time that lets bodies breathe. The morning of section 4—"Mechanics the product already enforces"—Sora almost bailed until the ping said FoF off and Close friends only. That clarity was the social lubricant.

Todd still talks about the brunch where nobody argued about the bill. Phones went face-down while rolls cooled. They measured the win in shared minutes, not in stories they would post for strangers. The graph was people they already knew—redeemed by six-character codes, not a discover feed. When coordination stayed thin, the room could hold actual news about friend code invites using a friend code.

Walking back through Marseille, Sora drafted the next ping while cheeks were still warm: same scale, rotated host, honest list. If time stayed open, someone would lock before seven days turned the plan into guilt. Unfriend or list changes would drop people from upcoming pings without a public exit speech—boundaries as mechanics, not theater. That is how friend code invites using a friend code becomes a habit instead of a hope.

End times on the ping are how tired adults say I love you without overstaying. For friend code invites using a friend code, section "Mechanics the product already enforces" is where that habit becomes visible: place plus time—or Let's Decide until someone locks—plus audience named on the ping. Friend codes grew this graph; first friend is still the gate before the feed opens.

Measure the month in shared minutes with known faces—not in how wide you broadcast. That combination is why friend code invites using a friend code can repeat without turning into guilt theater. Close friends stays undeletable; custom lists slice contexts; all-friends broadcasts stay rare when tenderness matters. The app will not manufacture strangers for your table—six characters, instant friendship, no code reset.

Teaching friends the vocabulary

Explain ping, RSVP, lock, Let's Decide in one message when sharing code—shared words lower second-brunch friction.

Show hangout chat vs group DM distinction—logistics thin post-redeem.

Rotate who sends second ping—codes symmetric; hosting should be too.

Phone-light twenty minutes models culture early.

Thank redeemer for showing—positive loop for code-era friendships.

In Marseille, Sora told the group that friend code invites using a friend code only works when the invite matches real life: place pinned, audience named, and an end time that lets bodies breathe. The morning of section 5—"Teaching friends the vocabulary"—Sora almost bailed until the ping said FoF off and Close friends only. That clarity was the social lubricant.

Todd still talks about the brunch where someone admitted they almost stayed home. Phones went face-down while rolls cooled. They measured the win in shared minutes, not in stories they would post for strangers. The graph was people they already knew—redeemed by six-character codes, not a discover feed. When coordination stayed thin, the room could hold actual news about friend code invites using a friend code.

Walking back through Marseille, Sora drafted the next ping while cheeks were still warm: same scale, rotated host, honest list. If time stayed open, someone would lock before seven days turned the plan into guilt. Unfriend or list changes would drop people from upcoming pings without a public exit speech—boundaries as mechanics, not theater. That is how friend code invites using a friend code becomes a habit instead of a hope.

Hosts who treat the invite like a short letter—not a campaign—see fewer last-minute bailouts. For friend code invites using a friend code, section "Teaching friends the vocabulary" is where that habit becomes visible: place plus time—or Let's Decide until someone locks—plus audience named on the ping. Friend codes grew this graph; first friend is still the gate before the feed opens.

Lock time when two real yeses appear; open pings that never land cancel seven days after create. That combination is why friend code invites using a friend code can repeat without turning into guilt theater. Close friends stays undeletable; custom lists slice contexts; all-friends broadcasts stay rare when tenderness matters. The app will not manufacture strangers for your table—six characters, instant friendship, no code reset.

Mistakes new code hosts make

Oversized first ping—twelve seats before trust rhythm exists.

FoF on by accident—wider notify than intended.

No end time—open-ended anxiety for new edges.

Let's Decide without lock owner—seven-day cancel feels like ghosting.

Group-chat parallel plan—splits attention before first sit-down.

In Marseille, Sora told the group that friend code invites using a friend code only works when the invite matches real life: place pinned, audience named, and an end time that lets bodies breathe. The morning of section 6—"Mistakes new code hosts make"—Sora almost bailed until the ping said FoF off and Close friends only. That clarity was the social lubricant.

Todd still talks about the brunch where a kid waved through the bakery window. Phones went face-down while rolls cooled. They measured the win in shared minutes, not in stories they would post for strangers. The graph was people they already knew—redeemed by six-character codes, not a discover feed. When coordination stayed thin, the room could hold actual news about friend code invites using a friend code.

Walking back through Marseille, Sora drafted the next ping while cheeks were still warm: same scale, rotated host, honest list. If time stayed open, someone would lock before seven days turned the plan into guilt. Unfriend or list changes would drop people from upcoming pings without a public exit speech—boundaries as mechanics, not theater. That is how friend code invites using a friend code becomes a habit instead of a hope.

The friendship graph you built with codes is the same graph deserving readable brunch plans. For friend code invites using a friend code, section "Mistakes new code hosts make" is where that habit becomes visible: place plus time—or Let's Decide until someone locks—plus audience named on the ping. Friend codes grew this graph; first friend is still the gate before the feed opens.

Lock time when two real yeses appear; open pings that never land cancel seven days after create. That combination is why friend code invites using a friend code can repeat without turning into guilt theater. Close friends stays undeletable; custom lists slice contexts; all-friends broadcasts stay rare when tenderness matters. The app will not manufacture strangers for your table—six characters, instant friendship, no code reset.

When code friends live far or busy

Let's Decide across time zones for video egg toast—still place-time semantics if meeting IRL later.

Near-term IRL ping pinned between redeemers' neighborhoods.

Close friends audience for first soft meet after code.

Decline paths clean—new friendships fragile to guilt.

Repair tiny if first brunch fails—forty minutes, same people.

In Marseille, Sora told the group that friend code invites using a friend code only works when the invite matches real life: place pinned, audience named, and an end time that lets bodies breathe. The morning of section 7—"When code friends live far or busy"—Sora almost bailed until the ping said FoF off and Close friends only. That clarity was the social lubricant.

Todd still talks about the brunch where the route turned left toward the river without a vote. Phones went face-down while rolls cooled. They measured the win in shared minutes, not in stories they would post for strangers. The graph was people they already knew—redeemed by six-character codes, not a discover feed. When coordination stayed thin, the room could hold actual news about friend code invites using a friend code.

Walking back through Marseille, Sora drafted the next ping while cheeks were still warm: same scale, rotated host, honest list. If time stayed open, someone would lock before seven days turned the plan into guilt. Unfriend or list changes would drop people from upcoming pings without a public exit speech—boundaries as mechanics, not theater. That is how friend code invites using a friend code becomes a habit instead of a hope.

When everyone knows who is notified, the table stops feeling like an audition. For friend code invites using a friend code, section "When code friends live far or busy" is where that habit becomes visible: place plus time—or Let's Decide until someone locks—plus audience named on the ping. Friend codes grew this graph; first friend is still the gate before the feed opens.

Hangout chat holds buzzer codes and allergies—the friendship talk stays at the table. That combination is why friend code invites using a friend code can repeat without turning into guilt theater. Close friends stays undeletable; custom lists slice contexts; all-friends broadcasts stay rare when tenderness matters. The app will not manufacture strangers for your table—six characters, instant friendship, no code reset.

Code plus ping equals table

Six characters open graph door; readable ping walks through.

Win: redeem Monday, ping Wednesday, eggs Saturday—with known human.

Tools encode product rules you already respect socially.

Teach circle to repeat—codes are not one-time novelty.

Friendship logistics: redeem, audience, RSVP, meet.

In Marseille, Sora told the group that friend code invites using a friend code only works when the invite matches real life: place pinned, audience named, and an end time that lets bodies breathe. The morning of section 8—"Code plus ping equals table"—Sora almost bailed until the ping said FoF off and Close friends only. That clarity was the social lubricant.

Todd still talks about the brunch where steam on glasses made everyone laugh. Phones went face-down while rolls cooled. They measured the win in shared minutes, not in stories they would post for strangers. The graph was people they already knew—redeemed by six-character codes, not a discover feed. When coordination stayed thin, the room could hold actual news about friend code invites using a friend code.

Walking back through Marseille, Sora drafted the next ping while cheeks were still warm: same scale, rotated host, honest list. If time stayed open, someone would lock before seven days turned the plan into guilt. Unfriend or list changes would drop people from upcoming pings without a public exit speech—boundaries as mechanics, not theater. That is how friend code invites using a friend code becomes a habit instead of a hope.

Low friction is not laziness; it is respect for calendars that already hurt. For friend code invites using a friend code, section "Code plus ping equals table" is where that habit becomes visible: place plus time—or Let's Decide until someone locks—plus audience named on the ping. Friend codes grew this graph; first friend is still the gate before the feed opens.

Hangout chat holds buzzer codes and allergies—the friendship talk stays at the table. That combination is why friend code invites using a friend code can repeat without turning into guilt theater. Close friends stays undeletable; custom lists slice contexts; all-friends broadcasts stay rare when tenderness matters. The app will not manufacture strangers for your table—six characters, instant friendship, no code reset.

Try this week

Concrete hangouts with people you know

  • 60-minute first

    Coffee after redeem.

  • Code QR

    Show in person; redeem same day.

  • Vocabulary DM

    One paragraph on ping rules.

  • FoF off

    First three invites tight.

  • Lock named

    Pick who decides 10 vs 11.

  • Repair tiny

    Retry without shame.

Keep in mind

Soft truths about friendship

  • 6

    Chars

    Instant friendship redeem.

  • 1st

    Ping

    Starter size wins.

  • 7d

    Open

    Unset cancel window.

Good to know

Questions friends actually ask

No reset theater—one code per person.

brunch-friend-code-invites-using-a-friend-code