What makes a pass-the-phone app feel fair when 5 people share one screen?
Designing for one shared phone is a different problem from designing for one person. Everyone in the room is watching the same screen, so a single confusing moment is seen by five people at once, and the phone changes hands every 20 seconds.
A few things we have learned so far: every turn must be understandable in about two seconds with zero reading, the handoff moment needs a clear signal of whose turn it is, and any result shown on screen has to be something the whole table can react to together, not just the person holding the phone. Small things like tap targets and what happens when someone accidentally taps twice matter more than we expected, because nobody wants to stop the fun to fix a mistake.
The open question for us: what makes a shared-screen experience feel fair? Is it equal turn length, hiding the answer until everyone is ready, or something else? If you have built or played something that passes one device around a table, what did it get right or wrong?
p/slotify-2
p/runevr
p/producthunt
p/google-cloud-platform
p/airuncode
p/aperture-7
p/ai-context-flow
p/kodlo
p/raycast
p/lasso-11
p/kuc-kuc
p/offiai
p/dino-kids
p/supabase
p/jev
p/many-displays
p/murror
p/reso
p/dex-by-exmergo
p/htmldrag
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.