The Sunday Evening Rescue: Engineering FairDraw's Zero-Friction Lucky Draw Engine for Live Events

1. The Sunday Evening Crisis at VBE 2026

It was Sunday evening at the after-party and gala dinner of the VBE 2026 (Vietnamese Badminton in the EU) tournament. Over one hundred celebratory, hungry, and exhausted athletes from across Europe had gathered in the venue hall. Trophies were resting on the banquet tables, music was playing, and everyone was eagerly anticipating the grand raffle draw.

My friend was in charge of running the lucky draw. Her original plan was the classic, time-honored logistical nightmare: print out sheets of numbering, find two pairs of dull scissors, manually slice a hundred tiny paper slips, fold every single one in half, throw them into a large plastic bowl, and pray that nobody knocked a glass of water or beer across the prize table.

Earlier that weekend, I had looked at that setup and whipped together a clean digital prototype on my laptop. When I showed it to her, she gave me the polite, hesitant nod that every developer knows all too well: with a hundred tournament logistics already on fire, she stuck with paper simply because habit is comfortable and safe.

Then came Sunday evening. The dinner was about to start in exactly fifteen minutes. Volunteers were depleted after two straight days of high-stakes court management. The paper raffle was hopelessly behind schedule: half the tickets were still un-sliced, handwritten names were smudged, and panic was setting in.

My phone buzzed with an urgent text: "Hey... that raffle app you made? Can we actually use it right now?"

2. The 15-Minute SOS from the Badminton Court

Here was the punchline: I was physically stuck on the badminton courts running the final matches. I couldn't walk over to the gala hall, plug in an HDMI cable, or give her a live software walkthrough.

At that point, there wasn't even an automated projector QR code generated. She simply copied the web link and dropped it directly into the tournament participants' WhatsApp and Zalo group chats.

And with zero instructions from me, she ran the entire lucky draw effortlessly.

Within three minutes, all one hundred attendees tapped the link on their phones, typed their names, and received their digital passes. She opened the stage screen on the venue display, tapped spin from her smartphone backstage, the mechanical slot reels rolled with sound effects, and the entire hall erupted into cheers. Every winner was verified instantly. Not a single slip of paper was cut, not a single participant lost their stub, and the draw completed flawlessly.

That electric moment was an undeniable revelation: if an everyday organizer can pull off a 100-person lucky draw in an emergency with zero training while the developer is playing badminton on the court, this experience belongs to the entire world.

3. The 6 Great Nightmares of Live Event Organizers

Taking that raw weekend prototype and evolving it into FairDraw meant systematically solving the six universal friction points that plague event organizers:

1. The Entry Bottleneck: Handing out physical raffle stubs or writing down names creates long, chaotic check-in queues. With FairDraw, guests simply scan the big screen QR code on their phone, enter their display name, and instantly mint their pass in five seconds.
2. Lost Stubs & Illegible Handwriting: Paper tickets get misplaced or crumpled in pockets; handwritten slips lead to awkward mispronunciations. FairDraw stores tickets safely in local phone memory with an 8-character cryptographic recovery key.
3. Absent Winners & Dead Silence: The classic raffle pause where an MC shouts a number four times while the crowd waits in silence because the winner is in the restroom. FairDraw introduces a synchronized Live 45-Second Claim Window with instant mobile verification.
4. Spammers & Duplicate Entries: In public streams or large gatherings, bad actors try submitting multiple times. FairDraw includes a host-level 1-Ticket Anti-Spam Lockdown bound to anonymous session tokens.
5. Tethered to the Stage Laptop: Most spinning wheel tools force the host to stand awkwardly behind a podium clicking a trackpad. FairDraw separates controls completely via a Pocket Remote Controller in the MC's palm.
6. Flashing Projector Banner Ads: Free spinner websites flash intrusive casino popups or weight-loss banners directly across the venue's projector. FairDraw guarantees 100% ad-free Stage and Host screens forever.

4. Dual-Surface Architecture: Stage Screen vs. Pocket Remote

In traditional event software, the biggest architectural failure is combining presentation with administration. If the audience can see your admin mouse clicks, your settings dropdowns, or your reset buttons on the projector, the magic of the presentation evaporates.

FairDraw implements a strict Dual-Surface UI Paradigm powered by real-time Firestore listeners:

• The Stage Display (Projector / TV): Built on a deep obsidian presentation canvas (`#080C14`). It features multi-digit mechanical slot reels with fixed character widths (`tabular-nums`) to prevent jitter during spins. It implements the native Screen Wake Lock API (`navigator.wakeLock`) so venue screens never go dark mid-event. Crucially, it contains zero admin buttons, zero PIN inputs, and zero advertisements.
• The Pocket Remote Controller (Smartphone): Formatted according to Apple Human Interface Guidelines for effortless one-handed backstage operation. The organizer pairs their phone in five seconds by scanning a private 128-bit Admin Key pairing QR code on the setup screen. From their pocket, the host can trigger spins, toggle participant locks, or adjust repeat winner policies.
• Apple Dynamic Island Telemetry: When the organizer taps a toggle backstage, an animated pill capsule floats at the top of the big stage screen, confirming actions (`Registration Locked`, `Repeat Winners Allowed`, `Reels Spinning`) with native spring physics.
• Hardware Clicker Support: For hosts who prefer walking the stage with a standard wireless presentation remote, the Stage screen natively listens for `Spacebar` and `Enter` keystrokes to trigger spins hands-free.

5. Zero-PII Entry & Cryptographic Password Restoration

In an era where every event tool demands a Google sign-in, corporate email address, and marketing consent checkbox, FairDraw adheres strictly to the Client-Side Sovereign Manifesto:

Attendees register with Display Name only. Zero emails, zero phone numbers, zero passwords to create. Upon joining, the client runtime generates an 8-character high-entropy alphanumeric recovery key via `crypto.getRandomValues()`.

To protect attendees from credential scraping on public stage displays, plaintext passwords are never stored in the public participants subcollection. Instead, the SHA-256 hash of the recovery key is indexed in a private `/recovery/{hash}` document. If an attendee accidentally closes their browser tab or switches phones, presenting their recovery key allows an instant $O(1)$ document lookup to restore their exact ticket pass with zero exposure of personal identifiable information.

The Live 45-Second Claim Window Protocol

When a winning ticket is selected, FairDraw triggers a synchronized countdown. On the Stage projector, an emerald progress bar counts down from 45 seconds. On the winner's smartphone, their digital pass transforms, glowing with victory confetti and displaying an interactive button: "Tap to Claim My Prize on Stage!".

Tapping the button immediately updates Firestore, locking out accidental host forfeitures and turning the projector screen into a verified celebration banner. If the winner fails to claim within 45 seconds, the host remote provides a safe Re-Spin / Pass action that returns the unclaimed prize to the active pool without corrupting the draw state.

6. Concurrency & Streamer Scale: Solving the 7 Edge Cases

A naive real-time raffle works fine with 20 friends in a living room. But when a streamer broadcasts to 10,000 live viewers on YouTube or Twitch, naive database architectures collapse into catastrophic read-storms or infinite browser loops. FairDraw was engineered from day one to withstand streamer-scale traffic:

• Avoiding the Birthday Paradox Loop: In a naive 4-digit random number generator, collisions accelerate exponentially as capacity approaches 8,000 entries. Naive `while(true)` loops freeze the browser tab. FairDraw enforces bounded reservation attempts (maximum 5 tries) backed by atomic ticket reservation keys (`/tickets/{code}`). If a room approaches capacity, it expands dynamically to 5 or 6 digits (up to 999,999 entries).
• Eliminating the $O(N^2)$ Read-Storm: If 5,000 attendees query the entire participants subcollection upon registering, Firestore serves 12.5 million reads in minutes ($$$ billing shock!). In FairDraw, attendee devices never query the participants list. Tickets are assigned with a single atomic write batch to `/tickets/{code}` and `/participants/{id}`. Read cost is exactly 1 read + 1 write per entrant.
• Scoped Real-Time Listeners: Attendee smartphones only attach listeners to the single room state document (`/rooms/{roomCode}`) and their personal ticket pass. Only the organizer's Stage screen listens to the full roster, reducing connection overhead by over 99.9%.
• Clock-Skew Immune Security Rules: Different devices often possess slight millisecond clock discrepancies. FairDraw's Cloud Firestore security rules validate updates via positive integer checks (`lastUpdated is int && lastUpdated > 0`) rather than rigid client-timestamp comparisons, preventing network drops or clock shifts from triggering permission rejections.

7. Architectural Benchmark: FairDraw vs. Alternatives

To understand why FairDraw represents a fundamental leap forward for event organizers, examine how it compares to legacy alternatives:

8. The Ephemeral 7-Day Purge & Cookieless Privacy

Every room created in FairDraw includes rolling `lastHostActionAt` and `expireAt` timestamps. Scheduled Cloud Functions automatically perform recursive cascade purges (`db.recursiveDelete()`), completely wiping expired rooms, tickets, hashes, and winner records seven days after an event concludes. There is zero orphaned data, zero marketing tracking, and zero database residue (embodying our client-side sovereign philosophy).

Furthermore, FairDraw operates under strict Google Consent Mode v2 with all storage flags denied (`ad_storage: 'denied'`, `analytics_storage: 'denied'`). Because no persistent profiling cookies or cross-site fingerprinting identifiers are used, the entire platform complies 100% with GDPR and the EU ePrivacy Directive with zero annoying cookie consent banners.

FairDraw exists because when people gather to celebrate, compete, and share joy, software should amplify that excitement, not obstruct it. Zero friction, zero tracking, and pure synchronicity.