Skip to main content
Prakhar Jain
Home Work About Contact Resume Let’s talk
Contact Resume Let’s Talk

Social decision game

SamePage: Five HYPE to turn group indecision into a decision

A live multiplayer decision game where everyone gets five HYPE, spends all of it, and reveals only the group result after everyone commits.

Role
Product Designer · Builder
Platform
Responsive web
Year
2026
Status
LIVE

30 Second Summary

Product

A live multiplayer decision game where everyone gets five HYPE and the group result stays hidden until everyone commits.

Design Move

Replace four independent reactions with one scarce five HYPE rule so every choice becomes a visible tradeoff.

Integrity

Keep individual allocations private, let ties remain ties, and resolve the final result from shared server state.

State

A live shipped product, with engineering verification kept separate from product traction claims.

The first interaction model worked. That was the problem.

Four reactions made the experience behave like a survey. The product became clearer when the interaction model was replaced instead of polished.

Five points changed the interaction from rating to tradeoff.

Every participant gets exactly five HYPE and must spend all of it.

Private before the result, private after it too.

Friends decide without anchoring on each other, then SamePage reveals only group totals.

A Reveal that does not spoil itself.

The board stays neutral until the shared result is ready.

Let a tie be a tie.

Equal displayed shares remain equal standing instead of being broken silently.

SamePage tie result showing equal group standing.

A result should not be a dead end.

Run it back preserves the decision context for another round while Ask something new clears it.

Building for actual use.

Multiplayer state, refresh behavior, duplicate commits, duplicate names, Realtime fallback, and narrow mobile layouts were hardened as product reliability issues.

Shipping changed the problem again.

A production sharing defect was fixed by moving copied room links to the canonical public origin. Engineering verification includes 188 automated assertions, 76 canonical sharing assertions, and 30 applied Supabase migrations. These are engineering verification numbers, not product traction.

Reflection

The strongest improvement came from replacing the rule, then carrying that decision through privacy, Reveal, ties, rematches, reliability, and launch.

Live product

Open live SamePage

Next Project

View Lilly Health

© 2026 Prakhar Jain · Product Designer
PrivacyTerms
Regional time · Open to relocation