A large-audience phone light show needs more than a target attendance figure. Concurrent devices, audience network access, browser behavior, command timing, and operator control all affect the experience.
This guide describes capacity and synchronization planning. It is not a measured performance report or a promise that any audience size will work on any deployment. Confirm the event's requirements with the platform team and rehearse in realistic conditions.
Define Concurrent Participation
Ticket count and concurrent device count are different. A QR announcement may produce a burst of joining activity. Reconnecting devices and the operator's session also form part of the event's connection pattern.
Collect these details before planning the live session:
- Expected concurrent audience devices
- When the QR code will be shown and announced
- Available audience Wi-Fi and cellular access
- Areas with weak coverage
- The account's participant limit
- The proposed server and network setup
A headline capacity number is not enough to approve a production. The proposed configuration and actual audience access need evaluation.
How Scheduled Commands Work
Applying a command as soon as it arrives makes differences in network delivery visible. A scheduled command instead includes a future start time.
The participant page estimates the difference between the server clock and the device's local clock. It uses that estimate to schedule the light steps locally. Receiving the message and starting the effect are therefore separate actions.
This approach does not eliminate every source of variation. Late messages, browser background behavior, device power management, and unstable access may still affect timing. Avoid presenting a single latency result as a guarantee for every phone in a venue.
What Happens During a Connection Loss?
When a participant disconnects, leaves, or the live session ends, lights and pending commands are cleared. That helps prevent an old scheduled effect from running after the participant has lost the current session.
A reconnecting device receives the current session state. Do not assume the show will continue uninterrupted offline. Rehearse the visible response in weak-coverage areas and keep audience instructions understandable.
Plan Capacity and Load Validation
A useful load test reflects the proposed deployment and joining pattern. Simulated connections can reveal server behavior, but they do not replace real-device checks for browser permissions, screen visibility, and torch access.
| Check | What to evaluate |
|---|---|
| Joining burst | Connection growth after the QR announcement |
| Command delivery | Timely delivery and rejection of stale-session commands |
| Reconnection | Return to the current live session |
| Session limits | Account capacity and one live event per account |
| Live control | Pending effects after Stop and End event |
| Operator refresh | Session visibility without automatic playback restart |
Record the deployment setup, network conditions, devices, and date alongside test results. Without that context, performance figures are not a useful basis for comparison.
Rehearse in the Actual Venue
A stable production connection does not prove that attendees can connect. Test from different seating sections or audience areas, using both cellular access and the intended venue network where applicable.
Include iPhone and Android devices, different browsers, screen-light fallback, and supported flash behavior. Test permission denial, reconnecting, returning to the browser, and scanning from real viewing distances.
Instructions should tell an attendee what to do next. They do not need device identifiers or command details to take part in the show.
Agree on the Operator Workflow
Preview runs on the operator's device. Go live opens the session; Play starts the selected item or event flow. Stop cancels playback while keeping the session open. End event closes the live session.
Only one event can be live for an account at a time. A second event can be prepared, but the current live session must end before another goes live. The operator and stage team should rehearse these transitions together.
Prepare the Next Decision
Review stadium QR placement, how phone flashes are synchronized, and the operational differences between wristbands and phone shows. Request a demo to discuss the audience flow and infrastructure checks for your event.
