The Kismet blog
Field notes on deciding less.
Ideas worth putting in the pool, how-tos for owners and guests, and the engineering that keeps the draw honest.
Posts
One text, no spam: how guest SMS works
Guests can get exactly one text — the result — and only after verifying their number. The design constraints behind…
Hidden means hidden: engineering invisible picks
Keeping submissions secret isn't a UI choice — it's an API contract, a websocket rule, an admin-panel policy, and a…
How the draw stays fair (and why the owner can’t peek)
The whole product rests on one promise: the draw is honest. Here's the architecture behind it — server-side randomness, persisted…
The trip pool: destinations your squad will actually accept
Group trips die in planning. A well-built destination pool — matched to budget, drive time, and the squad's real energy…
Date night roulette: two-person fates
Kismet isn't just for big crews — two hidden picks and one draw fixes the couple's eternal "I don't know,…
12 group nights that survive a random draw
The golden rule of a fate-picked night: every option in the pool should be one you'd actually do. Twelve submissions…
Crews 101: set up your ride-or-dies once
Crews turn a five-minute invite chore into one tap. How to build them, when to split them, and why your…
Locks and draws: timing your activity like a pro
The lock seals the picks; the draw picks the winner. The gap between them is where the fun lives —…
The perfect movie night, decided in 90 seconds
A lock time, a draw time, five posters, one fate: the exact recipe for a movie night that starts on…