The answer ball: designing a reveal worth waiting for

A random draw takes the server about a millisecond. We spend considerably longer telling you about it — on purpose. The reveal is the whole show, and the answer ball is its star.

Not a crystal ball. An answer ball.

Kismet’s ball is a warm-black orb with an ember heart. It doesn’t predict anything; it knows something — one true answer, sealed until the moment it matters. The distinction drives the design: no fog, no fortune-teller theater. Precision, warmth, and one great secret.

The choreography

Every reveal plays the same three-act beat, everywhere:

• Wake. The dormant ball stirs; the halo breathes. Your crew’s picks are in there, and the room knows it.
• Ignite. The core lights — ember flooding the glass. This is the draw itself, dressed for the occasion.
• Answer. The winning pick surfaces — restaurant card, movie poster, destination — with the confetti it deserves, and the pact line beneath it: It is decided. No take-backs.

Same moment, every screen

iOS renders it in SwiftUI, Android in Compose, and the guest web in the browser — but the beats, timing, and copy are deliberately identical, and the moment is synchronized live. A crew watching on three platforms sees one event. Whoever arrives late gets the full sequence on entry; nobody gets a spoiler, and nobody gets a lesser reveal for choosing the browser.

Details we obsessed over

• The winner unseals; the losers never do. Sealed forever reads on screen as a quiet vault, not an error.
• The first witness triggers the moment; everyone else joins it in progress or replays it whole.
• Reduced-motion users get the full information with none of the vertigo — the answer, not the acrobatics.

The best compliment we’ve gotten: a tester turned the phone around so the table could watch it land. That’s the whole design goal — a decision worth gathering around. See it in person.