I’m Your Host

Case study

The problemTrivia hosts spend the night collecting slips and updating scores.

Your room.
Your show.

Phone buzzers. A shared screen.
You run the night.

I’m Your Host shared question display
Player phone with a large buzzer
ONE ROOM. EVERYBODY IN.

I love hosting trivia. I built one app to coordinate the host, players and shared screen so I could spend more of the night with the room.

01

The problem

Trivia night comes with too much paperwork.

Trivia hosts told me about printing slips, preparing grading sheets and tracking scores. I wanted one app to handle those logistics for regular hosts, bars and breweries, and friends playing at home.

My decision

The phone becomes part of the group activity: a buzzer or answer sheet for the same game.

Answer slips, question sheets and a handwritten score grid spread across a trivia host’s table
Generated problem illustration
↓Next The solution02
02

The solution

Connect the host, phones and shared screen.

The host opens the desktop app. Players scan a QR code and join in their phone browser on the same Wi-Fi. A separate display gives the room a shared view.

My decision

I separated the host, player and display views. They need different information from the same game.

Actual host lobby: join QR code, shared Wi-Fi instructions and game settings
The way in · actual app, sample game
↓Next Question control03
03

Question control

Preview privately, then reveal the question.

The host checks the question and answer before showing anything to the room. Revealing the question is a separate action from opening buzzers or starting the written-answer countdown.

My decision

A private preview must never leak to phones or the shared screen.

Private host preview of a question and its reference answer before revealing it to players
Host only · question and reference answer
↓Next Timing04
04

Timing

Collect answers against one server deadline.

Written answers go to the host for review. The local server closes submissions at the deadline. Buzzes are ordered by arrival at that server; a close call can still be affected by Wi-Fi latency.

My decision

Holding the room freezes the countdown and locks responses. The game resumes from that held state.

Host countdown with one submitted answer and one team still thinking
Host view · incoming answers
Player phone showing the same countdown and a submitted written answer
Player view · answer from a phone
↓Next The result05
05

The result

Grade privately, then publish the scores.

The host decides which answers count, reveals the answers and then publishes written-round scores. Draft grading stays private. Saved scores and player identity support reconnects in the same phone browser.

My decision

Marking an answer should not immediately publish its points. The host sets the pace.

Private host grading: accepted answer with points pending publication
01 · Review marks privately

Publish scores

Shared leaderboard showing ten published points for the accepted answer
02 · The room sees the result

Behind the build

My part in I’m Your Host.

I specified the room experience, then the actions needed to move everyone through it. AI was my main implementation tool. The hardest work was getting the phones, host and shared display to agree on timing while keeping previews and unfinished grades private.

Evidence & what’s next

Screens show the actual game with simulated players. The desktop edition hosts multiplayer on a shared local network. The public browser round is a one-device sample; a real-phone game night is the next useful acceptance check.

This is trusted-LAN multiplayer, not an internet-hosted room. Wi-Fi latency can affect close buzzes. The host computer must remain awake. The browser sample is solo; the desktop edition has platform-specific installation prompts.

Run a complete game with real phones. Record join failures, reconnect success, unexpected reveals, host corrections and time spent on scoring.

Have a workflow in mind?

Discuss a workflow ↗