STORY
Engineering story
How the platform was scoped, built, and refined.
A real-time domain system that continuously determines who plays next, how groups remain together, which players fit available courts, how winners rotate, and how those decisions remain synchronized between administrators and participants.
Pickleball events require more coordination than simply allowing players to register. Organizers need to manage participants with different skill levels, maintain a fair player queue, assign players to available courts, communicate changes in real time, and manage membership access without forcing staff to manually coordinate every transition during an active event.
We built Ghost Mammoth as a production membership and event-management platform centered around the live event workflow. Players can join events, provide their skill level, enter the playing queue, and receive court assignments and updates as an event progresses. Administrators can create and manage events, configure courts, oversee player rotation, generate matchups, and end sessions while membership access is handled through subscription billing.
Architecture
The application uses Next.js and TypeScript for the application layer with Supabase providing PostgreSQL persistence, authentication, and realtime infrastructure. Supabase Realtime synchronizes event and court state between participants and administrators, while Stripe handles subscription checkout and membership billing. Row Level Security provides database-level access controls alongside application authorization.
The core challenge was coordinating state that changes continuously during a live event. Queue position, court availability, player assignments, event state, and administrative actions can affect multiple users simultaneously. The system therefore had to keep participant and administrator views synchronized while maintaining predictable queue and assignment behavior.
Real-time applications require thinking differently about state than conventional request-and-response CRUD systems. Changes made by one participant or administrator can immediately affect several other users, making synchronization, authorization, failure handling, and clearly defined ownership of business logic especially important. The project also reinforced the value of dividing complex domain logic into reusable modules and shared contracts as the system grows.
Continued development can expand group registration workflows, improve captain and team-management capabilities, refine event rotation and matchmaking behavior, strengthen administrative analytics, and continue improving the participant experience during live events.
Features
What the product or platform delivers.
- Event creation and management
- Player event registration
- Skill-level management
- Real-time player queue
- Court assignments
- Player notifications
- Court-count configuration
- Player rotation
- Automatic matchup workflows
- Session management
- Group registration
- Membership subscriptions
- Stripe Checkout
- Subscription access control
- Realtime synchronization
- Administrative event controls
- Row Level Security
- Responsive participant experience
Responsibilities
What I personally designed, built, or owned.
- Full-stack development
- Collaborative architecture
- Database integration
- Frontend development
- Backend development
- Realtime integration
- Authentication
- Authorization
- Stripe integration
- Subscription workflows
- Event-management workflows
- Administrative UX
- Testing and debugging
- Production refinement