Player A6
Player B4
Public events on CUE PLAY
Know what is happening before, during, and after match day.
One public event home can carry the schedule, field, live matches, bracket, player search, and final results without forcing spectators into the app.
Public pages stay open in the browser
Live eventIllustrative view
Pattaya · Thailand
Day 3 / 5Tournament hub
ScheduleBracketPlayersResults
Player C—
Player D—
UpcomingDecide whether to join.
LiveFollow what is happening now.
CompletedReturn to results that last.
One durable event home
The page changes purpose as the tournament moves.
Most event pages become outdated the moment play begins. A connected event page should become more useful under live pressure.
Make the decision clear
Venue, date, discipline, format, field, schedule, fees, and registration information belong together.
Information · field · registrationShow the room moving
Live matches, table assignments, bracket progression, player search, and results should update from the event operation.
Schedule · bracket · live scoresPreserve the outcome
Placements and completed matches remain useful for players, organizers, future participants, and the venue.
Results · records · case studyDesigned around the room
Different people need different answers from the same event data.
Players, spectators, and venue staff should not have to interpret an organizer dashboard to understand what matters to them.
When and where do I play?
My match, table, opponent, race, schedule, result, and progress.
What is happening now?
Live matches, notable players, bracket movement, and final outcomes.
What needs attention next?
Table pressure, waiting matches, blocked matches, scoring, and intervention.
What did this event create?
A professional public record, recurring activity, and evidence for the next event.
Open web + player app
Public access first. Personal participation when it adds value.
The public event page answers shared questions without requiring installation. The app connects a player’s identity, active matches, notifications, history, and performance.
Verified event proof
160 players. 479 matches. Five days live.
See what Pattaya proved, what failed under pressure, and what changed afterward.
Explore the Pattaya case studyFind or create the next event