The directory
People on the event home (or the search icon in the header) opens everyone attending the current event. It is the event's participant list, so a speaker at one event and an attendee at another are two entries, not one.
Filter chips across the top show counts by type: All, Speaker, Sponsor, Exhibitor, VIP, Attendee, Volunteer, Press. The type is set by the organizer.
Search filters by name. The list loads fifty at a time and fetches more as you scroll.
Each card shows the person's photo, name, title and company, their type badge, and one of three relationship badges once the app has cross-checked your lists:
| Badge | Meaning |
|---|---|
| Connected | You are connections — accepted both ways |
| Pending | You sent a request they have not answered |
| Following | You follow them |
Connect, Follow, Message
They are three different things, and the difference matters.
Connect sends a request. Nothing happens until they accept. Connections are mutual, global across events, and the basis for meetings and messaging. You cannot connect with yourself, cannot send a second request while one is pending, and cannot connect with someone who has blocked you.
Follow is one-way and needs no acceptance. It is for keeping up with what someone posts — a speaker, a sponsor — without asking them for anything.
Message opens a direct chat. It works with anyone who has not blocked you, connection or not.
Connections are keyed on email address in both directions. If someone is registered under two addresses, a request to one of them will not show against the other.
The profile page
Tapping a card opens their profile:
- Avatar, name, role badge (Speaker, Sponsor…) and whichever relationship badge applies
- Headline: job title and company, with their email
- Bio
- Topics — what they said they can talk about
- Social — LinkedIn, X, website, GitHub, where they filled them in
- Sessions — the sessions they are part of, by title; tap through to the session
Actions along the bottom: Connect (or Pending once sent), Follow / Unfollow, Message, and Meet.
The page loads in two passes. It opens instantly with what the card already knew, then fills in the event-specific details and the relationship state a moment later. If a badge appears after a beat, that is why.
Booking a meeting
Meet on a profile opens a short form: a title, a date and start time, a duration, and where — in person with a place, virtual with a link, or by phone — plus an optional note. Sending creates a meeting request.
Meetings have a state you should understand before you rely on one:
| State | Meaning |
|---|---|
| Proposed | Created; every participant is pending |
| Confirmed | Every participant accepted |
| Cancelled | Either side cancelled |
| Completed / No-show | Set afterwards |
The meeting becomes confirmed only when everyone has accepted. A single decline keeps it proposed. If the organizer of the meeting reschedules it, every acceptance is reset and it drops back to proposed — people have to accept the new time.
Your meetings live under Meetings in the drawer, with Upcoming (confirmed ones ahead of now) and All. Respond, cancel, or open the other person's profile from there.
A meeting request goes to anyone you can open a profile for. Connecting first still helps: an accepted connection is far more likely to accept a time.