One phone, the whole auth story: join with an invite code, get your one-time code, verify and you're in — or come back as a returning member with a password. Then sign out properly: this device, or everywhere at once.
Try it: join with any name + email/phone and an invite code like TODD-XXXX → the demo code is 123456 → type a wrong code and watch the error stay on the code screen with resend → sign in, then sign out on this device vs everywhere and watch the session bar clear. Returning member? Flip the toggle and use password sign-in, or “Forgot password?” for the reset link.
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.
What maps to the Android build: SignInScreen.kt is the same flow — stepped Details → Code → Joined, inline field errors, six one-digit code boxes with paste, resend with a 30-second cooldown, wrong-code stays on the code screen, password sign-in with show/hide + forgot-password reset. SignOutScreen.kt is the sign-out screen — this device vs everywhere, with a confirm. SupabaseAuthClient.kt does the real work: OTP via /otp + /verify, password via /token, reset via /recover, sign-out via /logout (this device, with the user's token) and /logout?scope=global (everywhere). The local session is always cleared even if the server call fails.
What this preview does NOT do: no real account is created, nothing syncs, no code is actually sent. The main interactive prototype (previews/index.html) is where events, RSVP, claims, chat and calendar live.