For an in-house product build: a party game where the players write the rules, running on a phone with nothing to install. A browser game with no install for players. Party games ship with a fixed rulebook, so the game is the same on the tenth night as the first and the group stops reaching for it.
We built this one for ourselves: an in-house product build. It earns its place here on the same evidence as any client project.
Party games ship with a fixed rulebook, so the game is the same on the tenth night as the first and the group stops reaching for it. The interesting part of any house game is the rules a group invents for itself, and no product was capturing that.
A browser game with no install for players. Each round every player secretly proposes one rule, all proposals reveal at once, then everyone casts one secret ban vote. A single ban vote kills a proposal permanently and a proposal nobody bans becomes a live rule for every round after it, so the game the group is playing on round ten is one they wrote themselves. Secrecy is enforced on the server rather than trusted to the client, because a party game where one person can peek is not a game.
This one is built but not live yet, so there is no result to measure. The day it launches and the numbers come in, they go here, dated.
Build record: 8 tracked changes over 2 days, 3,797 lines of working code, 9 automated test files. Every number here comes straight from the project's build history.