Articles/Engineering

Engineering Realtime Multiplayer for a Room Full of Strangers

Freedom Bar Games runs live trivia across venue screens, tablets, and phones simultaneously. Here's the architecture that keeps every surface in sync.

July 17, 2026·9 min read·By Impartial AI Tech

Freedom Bar Games runs live trivia and tournaments across three surfaces at once: the venue's big screens, staff tablets, and every player's phone. When a question drops, it drops everywhere in the same instant — because the moment one table sees the answer choices before another, the game isn't fair, and a game that isn't fair in a bar gets loud.

GAME ENGINEauthoritative state · websocketsVENUE SCREENquestions · leaderboardTABLETShost controlsPLAYER PHONESQR join · answersEVERY SURFACE SEES THE SAME MOMENT — OR THE GAME BREAKS
Fig 1 — One game state, three surfaces, sub-second sync

One authoritative state

The architecture rule that makes everything else work: the server owns the game. Phones, tablets, and screens are projections of one authoritative state, never sources of it. Every device connects over websockets and receives the same state transitions; no client ever decides what time it is, what question is live, or whether an answer arrived in time. Client-authoritative multiplayer is how you get cheating and drift; server-authoritative is how you get one shared moment.

The clock problem

Trivia is a timing game, and every phone's clock is slightly wrong. Freedom Bar Games syncs on connection: each client measures its offset from server time and renders countdowns against the corrected clock. Answers are timestamped on arrival at the server — the only clock that counts — so a laggy phone shows a tight countdown but never gains an advantage.

Designing for the worst network in town

Bar wifi is hostile territory: concrete walls, a hundred competing phones, a router installed in 2019. The system assumes disconnection as the normal case. State is resumable — a phone that drops for ten seconds reconnects into the current moment, not a broken session. Payloads stay small, reconnects are aggressive, and the venue screen (wired, stable) never depends on any phone.

Why realtime is the product

The engineering serves a social outcome: a room full of strangers reacting to the same reveal at the same second. That shared gasp is the product — the latency budget, the clock sync, the reconnect logic all exist so the room stays one room. Multiplayer infrastructure, deployed where people actually gather. That's Freedom Bar Games: freedombargames.com.

See Adaptive XI Intelligence in action

Tell us about your project. We will respond within one business day.

Start a Project →