Eventsprototype
0 free events left
Frontend only · no backend

Pick a user type

Every screen here runs on mock data held in your browser. Nothing is saved to a server, and there are no API calls — this exists so the flows can be walked through and argued about before any backend is written. Reset data in the top bar puts it back.

Coordinator
Paid after 3 free events
Creates and runs the event. The only role that can.

Sign in → event list → create → plan → invite → run the day

Open the coordinator flow
Celebrant
Free
The person the event is for. Sees and approves; never edits.

Accept invite → see the event → approve or reject

Open the celebrant flow
Guest
Free — no account, ever
Opens a link, says who is coming. No sign-in anywhere on this path.

Open link → name members → questions → confirm → QR

Open the guest flow
Merchant
Paid, no free tier
Sells goods and services. Posts packages and a portfolio.

Sign in → profile → packages → portfolio → inquiries

Open the merchant flow
What to poke at
The decisions that are easiest to get wrong, made visible.
The paywall

You have 3 events created. Creating a 4th hits the gate — and deleting an event does not give the slot back.

The four counts

Allotted / named / confirmed / arrived are never summed. Arrived shows “—”, not 0, until someone is actually checked in.

Partial responses

The Santos family has 3 coming and 1 declining. That badge must not look like a shade of “all coming”.

The seat cap

Tita Nena has 2 seats. Try to name a third on the guest flow — the block has to name the way out, not just refuse.

Approvals

The celebrant can approve or reject, never edit. A rejection needs a note, and the coordinator can still proceed — visibly.

Labels

Nothing says “Guest” literally. Open the corporate event and the same screens say Attendee, Organiser, Agenda, Team.