Attendee journey
- Discover an event through public pages, social links, or organizer profiles.
- Open the event page at
/e/[slugOrId].
- Choose a ticket tier and proceed to checkout.
- Pay through Paystack, Flutterwave, Stripe, or a free-ticket path.
- Receive confirmation, pass downloads, and follow-up engagement options.
- Optionally generate a DP, save the event, or use wallet pass and QR check-in features.
Organizer journey
- Sign in through email OTP, magic link, or social auth.
- Create or join an organization and workspace.
- Create an event from
/organizer/events/create.
- Configure tickets, sessions, speakers, DP templates, policies, and marketing assets.
- Monitor orders, attendees, claimed DPs, incidents, and live operations.
- Use reports, insights, and debrief tools after the event.
Admin journey
- Access the admin console under
/admin.
- Review organizations, users, verifications, feedback, and complaints.
- Adjust platform settings such as email, feature flags, releases, SEO, and event types.
- Moderate risky content, support escalations, and payout or refund flows.
Mobile client journey
- Mobile app stores an API key generated from the admin dashboard or uses the legacy static key.
- Requests go to
/api/mobile/backend/*.
- The Next.js gateway validates the key, filters allowed paths, and proxies to the backend service.
- The mobile client receives proxied responses and health or discovery metadata.
DP campaign journey
- Organizer publishes a DP campaign or template.
- Public users open the campaign page and generate or personalize a DP.
- Funnel events are tracked through the DP campaign layer.
- Exports, shares, and generated assets feed campaign analytics and organizer reporting.
Operational workflow
- Health endpoints expose platform readiness.
- Railway deployment metadata is ingested into release history.
- Admin release tooling can analyze deployment data and help with rollback decisions.