Two live phones, one shared table. The left phone is the Android app (native Kotlin + Compose, the main build). The right phone is the web companion for iPhone friends. They are not two chats — they are the same group, same events, same bring-list, same conversation, syncing live both ways.
Try it: sign in on either phone (demo code 123456) → open Friendsgiving → RSVP Going with 2 adults + 1 kid and watch the headcount jump on both phones → tap “I’ll bring it” on the lemonade → send a chat message from the web phone and watch it land on the Android phone → tap 😀 for the full emoji picker, GIF for an animated GIF, and + on any message to react with any emoji → paste a link and watch it unfurl → check your “✓✓ Seen on Web” receipt → switch the calendar to Week / Day, create an event from a day with Monthly repeat → on Members, add a guest, then remove Sam and watch his turkey claim free up live → try Quiet hours (Members → Notifications): while quiet, cross-phone pings hold and land in one Missed rundown instead.
Todd says it’s time to eat.
Powered by Makryden
Invite-only — no public signup. If the buttons don’t respond, reload the page — the interactive preview needs JavaScript.
Todd says it’s time to eat.
Powered by Makryden
Invite-only — no public signup. If the buttons don’t respond, reload the page — the interactive preview needs JavaScript.
Android and web read and write the same Supabase tables — chat_messages, claims, events, rsvps, bring_items — under the same Portal identity. A message, claim, RSVP or new event lands in the same row whichever client sent it.
Both clients subscribe to postgres_changes on all five tables. When a row changes, Supabase pushes it — the other client re-renders that list on the spot. No refresh, no polling. Publication is turned on in supabase/schema.sql.
This prototype has no backend keys in it, so the “channel” here is one shared JavaScript store feeding both phones — the same shape as the real channel, with a sync log so you can see every event cross from one phone to the other. The production wiring is in web/app.js (subscribeRealtime()) and the Android repo swap in the README.
Admins add guests with an invite code (spent in the Portal) and remove them behind a confirm step. Removal is enforced in remove_member(): access gone at once, RSVPs dropped, claims deleted so the dish opens up again. Past chat stays as history. Try it on Members — remove Sam and watch his turkey free up on both phones.