The problem
Finding and attending events locally still often means scouting the internet, word of mouth, or fragmented organizer pages. Discovery was noisy, ticketing ran through DMs and screenshots, and organizers lacked a real ops home. Beyond discovery, organizers lack the interface to manage invitations, RSVP, event-themed posts, and more customizations. Event Hub aims to solve these two main problems.
My role
I contributed to the web app and admin surfaces as part of a development team, and I handled the mobile app end to end (React Native / Expo).
- Web platform (team) — marketing site plus organizer and admin areas in one Next.js app: discovery, ticketing, invitations, RSVP, scanning, and ops
- Mobile app (end to end) — Expo client: onboarding, auth, discovery feed, event detail, tickets, and preferences (Zustand and related app state)
- Shared platform work — wiring clients to the backend so auth, events, and tickets stay consistent across surfaces
Architecture
Two clients talk to one backend API. The web app is a single Next.js application — marketing, organizer, and admin live in the same codebase, separated cleanly with Better Auth (roles) and a multi-tenant model so each organizer workspace stays isolated. The mobile app is the attendee-facing native client. The diagram stays at that level — no infra internals.
