Designing Games for One Shared Phone: 7 UX Patterns From 30+ Pass-and-Play Games

Most multiplayer advice assumes every player has their own screen. Pass-and-play games break that assumption: one phone sits on the table, and it moves from hand to hand. That changes almost every UX decision, from how a turn starts to what "undo" is allowed to mean.

I run Pass and Play Games, a free collection of 30+ browser games built for exactly this: chess, Ludo, dice games, and party games for up to 12 people, all on one device. These are the seven UX patterns that show up across the whole collection.

1. Hide, then pass

The core problem: some information belongs to one player only. Your dice in Liar's Dice. Your role in Mafia. The secret word in Imposter.

The fix is a pass screen between turns. The current player hides their information, hands the phone over, and the next player taps to reveal their own. In our Imposter game the phone first shows a "Pass to Riya" screen that tells everyone else to look away. Then Riya's word sits behind a "Hold to reveal" panel: she holds it to read the word, and the moment she lets go, it hides again. In Liar's Dice, a pass screen covers the dice before every turn.

In Imposter, the word only shows while Riya holds the panel. Let go and it hides.

The rule of thumb: never show private information on the same screen that hands control to the next person.

2. Make every secret turn look the same

A pass screen isn't enough if the turns look different from across the room. In Mafia, if only the mafia spend ten seconds tapping at night, everyone else can guess who they are.

So in our Mafia game, the phone visits every living player at night. The mafia choose a target, the Doctor protects someone, the Detective checks someone, and townspeople answer a harmless question. Everyone taps for a similar amount of time, so watching the person holding the phone tells you nothing.

3. Decide what actually needs to be secret

The opposite mistake is hiding everything. Not every game needs a pass screen, and extra taps slow a party down.

In our Truth or Dare, the phone stays on the table and nothing is hidden: it picks the next player, they choose, and everyone hears the card. In Charades, the secret is hidden from the guesser instead: in Forehead mode, the guesser holds the phone to their forehead while everyone else sees the word.

A useful exercise before building any game: list every piece of information and ask who is allowed to see it, and when.

4. Make turn order impossible to argue about

With one device, "whose turn is it?" causes more arguments than the rules do. Two things help:

• Names in seating order. Players type their names in the order they're sitting, and turns rotate in that order. The phone always moves around the table in one direction.
• Fair randomness. In Truth or Dare, "Spin" mode picks the next player randomly, but everyone has a turn before anyone gets a second one. Random enough to be fun, fair enough that nobody gets picked three times in a row.

In Truth or Dare nothing is hidden: the phone stays on the table, shows whose turn it is, and everyone can see the choice.

5. Secret votes that protect people

Group votes on one phone are awkward. If the phone shows who voted for whom, you've built a friendship-ending machine.

Two approaches that work:

• Show the result, never the voters. In our Most Likely To, a secret vote shows the counts only, never who voted for whom.
• Reveal only when everyone has voted. In Would You Rather's secret mode, the phone is passed round, each person taps alone, and nobody sees the split until the last vote is in.

Offering both "vote together" (show of hands, fast) and "secret vote" (slower, safer) lets each group pick.

6. Undo that can't be abused

Mis-taps are easy to make when a phone is being passed around, so undo matters. But in a game with dice, a careless undo is a cheat button.

The rule across our games: undo can reverse a decision, but never luck.

• In Yacht Dice, undo returns your dice, but it never gives you a new roll.
• In Hot Dice, you can take back a bank, but never a roll.
• In Liar's Dice, you can undo your own bid, but not after someone has called "Liar!".
• In Ludo, you can undo moving the wrong token without getting a re-roll.

In Yacht Dice, Undo stays greyed out after a roll. It can take back a scoring choice, but it never gives you a new roll.

7. Never lose the game

A shared phone gets locked, pocketed, or used to check a message mid-game. If that resets the game, the group won't come back.

So saving as you go matters. Liar's Dice saves after every bid, Ludo and Snakes and Ladders auto-save, and in Draw and Guess the drawing itself is saved, so a reload restores the turn. On top of that, every game keeps working offline after the first visit, which matters on road trips, camping weekends and flights.

Bonus: let the computer fill empty seats

"We only have three people" shouldn't stop a four-player game. In most of our board and dice games, any seat can be a computer player, so the game fits whatever group is actually in the room.

What I'd tell anyone building for one shared screen

Design the handover, not just the screen. A lot can go wrong in the two seconds when the phone changes hands: someone sees what they shouldn't, the wrong person taps, or the game loses track of whose turn it is.

If you want to see these patterns in action, the party games collection is a good place to start. And if you've built anything for one shared device, I'd love to hear which handover problem bit you hardest.

I wrote this with help from an AI assistant and checked every game detail against the live game pages.