# Run the game from one screen; let everyone play from theirs

Connect the [desktop game-show host](../desktop/game-show-host.md), a public room display, and [phone-based participation](../shared-web/party-game.md) into one enjoyable game night. Build it extremely well. The host should pay attention to the people playing while each screen supplies the information and controls appropriate to its role. Follow the [shared launch](../shared/launch.md).

Begin with the game and material the person has already built. Preserve its rules, saved shows, and useful hosting controls. Complete a chosen format across the connected screens, adding missing components where needed.

## Make joining part of the evening

Let players join from their phone browsers through a convenient link or room code. Give them a recognizable identity in the right game, individually or as a team according to the rules.

Help the host see who has arrived and start when the group is ready. Make returning after an accidental refresh or locked phone straightforward. Preserve the player's place and any contribution already accepted.

Set up the television or projector on the person's actual equipment. Let the host rehearse the display arrangement and recognize which view the room will see.

## Give each role the right view

The host needs the current answer, upcoming material, pacing controls, and the group's progress. A player needs the current task, their own answer or choice, and confirmation of what the game received. The room needs the public question, reveal, and standings.

Deliver information to each role according to the game's rules and current phase. A player can inspect their submitted answer while other players' answers remain private until reveal. The host can prepare the next question without exposing it to the room.

Keep all views attached to one ongoing game. A changed question, accepted answer, score correction, or new round should reach the relevant screens coherently. Make a stale or disconnected view recognizable and return it to the current game when it reconnects.

## Preserve the host's control of the room

Let the host pause to explain a question, extend a response period, accept a valid unexpected answer, or correct a score. Give those actions clear consequences for the round and standings.

Choose phone interactions that fit the existing game: typed answers, votes, wagers, or buzzing in. Complete the interactions the format actually uses. If response order matters, make the accepted order and the host's ability to resolve a dispute clear.

Show players whether an answer arrived in time and whether they can still change it. A repeated tap or a late reconnect should leave them with a comprehensible result. Keep the room's reveal enjoyable and give everyone a clear finish to the game.

## Deliver a connected evening

Use the established hosting setup and suitable free services where they fit. Explain current service limits and which components must remain available. Keep participants' access appropriate to a shared game; use any private device connection for the private management work it serves.

Complete a round with a host view, public display, and separate player sessions. Include a private submission, reveal, scoring adjustment, and returning player. Judge readability from across the room, ease of answering on a phone, and whether the host can continue talking to the group while operating the game.

Retain reusable show material and saved results under the shared launch's ownership guidance. Teach the person how connected applications can give different people different experiences of the same event. Later game formats can reuse that relationship while bringing their own rules and atmosphere.