At a sold-out show at the O2 Arena, every person in the building has a smartphone. That smartphone can access any URL in the world within seconds. This has always been true, but the live event industry has been slow to take it seriously as an infrastructure assumption. Hardware vendors, dedicated apps, and proprietary systems have dominated because they offered control. Browser-based alternatives are now offering the same control without the hardware overhead, and event operators are paying attention.
The app download barrier was never trivial
Event apps have existed for over a decade. Adoption has consistently lagged expectations. The reasons are well understood in the industry: fans don't want to download an app for a two-hour experience they may only have once. Storage is a real constraint on older devices. App store approval processes create production headaches. Battery and permission warnings trigger anxiety at exactly the wrong moment.
Browser-based alternatives sidestep all of these. A URL is frictionless. No download, no account creation, no permission request beyond what the specific feature needs. For a crowd display feature that needs screen color and flashlight control, the browser requests those permissions at the moment they're needed, not during a multi-step app setup flow.
Modern browsers are dramatically more capable than five years ago
The limitation argument against browser-based live event technology used to be credible. WebSockets were inconsistent, JavaScript performance on mid-range devices was genuinely poor, and hardware API access through browsers was limited. That gap has closed substantially.
Current browser capabilities relevant to live event technology include:
- WebSocket connections: stable, low-latency, and well-supported across all major mobile browsers
- Screen brightness control: full-screen color display at maximum brightness available via standard web APIs
- Torch/flashlight access: rear camera LED controllable through the MediaDevices API on iOS Safari and Android Chrome
- Background audio: relevant for synchronized sound-based effects
- Web Push notifications: for event-day prompts without an installed app
The sub-100ms update latency now achievable through WebSocket connections to cloud-scale infrastructure means browser-based coordination is fast enough for real-time synchronization across thousands of concurrent devices. The technical case against browser-based crowd interaction has largely expired.
Infrastructure costs are dropping in parallel
Cloud computing economics have changed the infrastructure calculus for browser-based event technology. Running a WebSocket server that handles 50,000 concurrent connections used to require significant dedicated hardware investment. GCP Cloud Run and similar serverless container platforms allow systems to scale elastically: small events pay for small capacity, large events scale automatically, without over-provisioning for peak load.
This economics shift matters for the event industry because it removes the minimum viable deployment size. A technology that previously required a substantial licensing fee to justify the infrastructure cost can now be viable at event sizes that weren't economically interesting before.
Ticketing set the precedent, crowd interaction is following
Digital ticketing migrated from dedicated apps to browser-based wallet passes and web views faster than most of the industry expected. The trigger was Apple Wallet and Google Wallet integration, which made the browser-accessible approach more reliable than the app-based alternative for many users. Venue access control now largely treats a browser-rendered QR code as equivalent to an app-rendered one.
Crowd interaction is following the same arc. The early browser-based crowd display systems were curiosities: impressive demos with operational rough edges. The current generation is production-validated: tested at 2,000+ concurrent connections, configurable per venue, manageable by internal entertainment teams rather than specialist technical crews.
What operators need to evaluate
For stadium entertainment managers and event producers evaluating browser-based crowd technology, the key operational questions are different from those for hardware systems:
- What's the Wi-Fi capacity in the venue, and is it sufficient for the expected concurrent connection count?
- What's the briefing and onboarding strategy that gets fans to the URL within the available connection window?
- How does the system handle fans who can't participate: older devices, no data, no interest?
The hardware question, which used to dominate procurement conversations, has become less central. The operational question is now about fan behaviour and venue connectivity, not equipment specification. That represents a meaningful shift in how event operators think about crowd technology procurement.
Ready to turn your crowd into the canvas?
Seatwave turns every fan's phone into a synchronized pixel, controlled live from a single dashboard.