If you are building for venues, the problem is not just "count people." It is state management at scale.
A solid system needs:
- Identity:RFID / BLE / QR / badge linked to a ticket or role
- Events: Entry, exit, zone transition — with timestamps
- Rules:Who can enter which zone, when, and how many times
- Live aggregates:* Occupancy per zone, updated in seconds, not minutes
- Resilience: Offline check-in at gates, then sync when network returns
- Audit:Immutable logs for compliance and post-event analysis
The hard parts are not the sensors. They are deduplication, offline sync, clock drift, and keeping the dashboard fast when 10,000 people enter in 30 minutes.
General
Source:https://dev.to/isadora_gift/building-event-venue-people-tracking-what-the-system-actually-needs-to-do-2hb
Building Event & Venue People Tracking: What the System Actually Needs to Do
dev.to0 views
PreviousMy Voice Agent Portal Keeps the Calls. The Vendor Keeps the Agent.NextWhat are the best SaladCloud alternatives for GPU workloads?
Related posts
Amtrak booking system experiencing major issues amid nationwide FAA ground stop
0Hacker News
FAA issues national ground stop
0Hacker News

2026.46: The End of Jensen
0Stratechery
Away from the keyboard: Kisumu Market Day
0dev.to Watercooler
Структурований Scorecard найму
0dev.to Programming
Show HN: NETWAR – hacker MMO with 15-second card duels on a shared hex map
0Hacker News Show