Does multiplayer mode work over poor internet connections?

Mostly yes — better than screen-sharing. The animation runs locally on each device from a shared seed, so a slow connection delays the spin start but doesn't smear the animation itself. Compare to screen-share, where every frame has to traverse the network and a slow viewer sees a blurry, compressed wheel.

What happens if the host disconnects mid-spin?

The wheel keeps spinning on every viewer's device. The room state already has the seed; the animation completes locally. With screen-share, a host disconnect freezes the entire audience and the draw has to be redone — usually with awkward questions about whether the first spin actually finished.

How many people can join a multiplayer room?

Practically, dozens — the limit is your firestore quota, not the wheel. For livestream giveaways with hundreds of viewers, post the room code in chat and let interested viewers join. Each one becomes an independent witness to the result.

Can viewers see each other's names in the room?

Each viewer picks a display name when joining. The host sees the participant list; viewers see each other as anonymous unless the host explicitly shares names. Useful for transparency without exposing audience identities.

Running a draw with remote viewers: multiplayer mode vs screen-sharing

Published on May 13, 2026· 2 min read

By SpinOfLuck Team

Why a shared multiplayer wheel beats screen-sharing for raffles and giveaways with remote viewers — covering latency, verifiability, and what to do when the host's internet is the bottleneck.

Key Takeaways

Screen-sharing is fine for small low-stakes draws; latency, compression, and verifiability fail at scale.
Multiplayer mode renders the animation locally on each viewer device — crisp, low-latency, and independent witness.
Hybrid pattern: stream your face and audio normally, but have viewers open the multiplayer wheel room separately.
If the host disconnects mid-spin, multiplayer continues on every viewer's device; screen-share freezes everyone.

The default way to run a draw with remote viewers is to share your screen and spin the wheel while everyone watches. It works — most of the time. The remaining 20% of cases is where multiplayer mode (a shared wheel each viewer joins on their own device) earns its place.

What screen-sharing does well

Screen-sharing is the obvious default for good reasons. There's one wheel, one timeline, no synchronization problems. Everyone sees exactly what the host sees. For small groups on a stable call, it's perfectly fine.

It also has minimal setup. The host opens the wheel, hits share-screen, spins. No room codes, no coordination, no extra tabs for viewers to open.

Where screen-sharing breaks down

Three failure modes show up reliably:

Latency: the host's spin animation arrives at each viewer with 200ms–2s of delay, varying per viewer. By the time the slowest connection sees the result, the host has already announced it and the suspense is gone.
Compression artifacts: streamed video at modest bitrates blurs fast-moving wheels. Viewers see a smeared rotation and a stationary final frame. They have to trust the host that the wheel actually spun — they can't see the slowdown.
Verifiability: a recorded screen-share is one stream. A determined skeptic can claim the host pre-edited it. A multiplayer session, by contrast, has the same animation playing simultaneously on multiple independent devices — much harder to fake.

Why multiplayer fixes these

In multiplayer mode each viewer's device renders the wheel locally from a shared room state. The animation is crisp because it's rendered in their browser, not streamed as video. Result reveals happen within a few hundred milliseconds across all devices — the spin start is networked, the animation itself is local.

More importantly: every viewer becomes an independent witness. If five people watching from different cities see the same wheel land on the same name, that's a much stronger fairness claim than 'trust the host's screen-share.' For high-stakes giveaways, this matters.

Host a multiplayer draw

Create a room, share the 6-character code, and let viewers join from any device — independent witness for free.

Open the Multiplayer Wheel →

When to use which

Internal team draw, low stakes, small group: screen-share is fine. Don't over-engineer it.
Public giveaway, anyone-can-watch, prize value over $50: use multiplayer mode. The audit trail is worth the 60 seconds of setup.
Livestream giveaway with chat-based entry: multiplayer mode with the room code in chat description. Viewers join on their phones while watching the main stream — independent witness for free.
Anything you'll record for after-the-fact compliance (charity raffle, regulated draw): multiplayer mode, and pre-share the room code so the timestamp on the recording matches the timestamp viewers had on their devices.

The host-internet failure mode

One nice property of multiplayer mode: if the host's internet drops during the spin, the wheel keeps spinning on every viewer's device. The room state already has the seed; the animation completes locally. Compare to screen-share, where a host disconnect mid-spin freezes the entire audience and the draw has to be redone — usually with awkward questions about whether the first spin actually finished.

It's a small thing until it matters, at which point it matters a lot.

Frequently asked questions

Does multiplayer mode work over poor internet connections?: Mostly yes — better than screen-sharing. The animation runs locally on each device from a shared seed, so a slow connection delays the spin start but doesn't smear the animation itself. Compare to screen-share, where every frame has to traverse the network and a slow viewer sees a blurry, compressed wheel.
What happens if the host disconnects mid-spin?: The wheel keeps spinning on every viewer's device. The room state already has the seed; the animation completes locally. With screen-share, a host disconnect freezes the entire audience and the draw has to be redone — usually with awkward questions about whether the first spin actually finished.
How many people can join a multiplayer room?: Practically, dozens — the limit is your firestore quota, not the wheel. For livestream giveaways with hundreds of viewers, post the room code in chat and let interested viewers join. Each one becomes an independent witness to the result.
Can viewers see each other's names in the room?: Each viewer picks a display name when joining. The host sees the participant list; viewers see each other as anonymous unless the host explicitly shares names. Useful for transparency without exposing audience identities.