Tracking gets messy during the game
Re-buys happen mid-conversation, chips move fast, and paper notes drift out of date.
A mobile-first poker session tracker for casual home games.
Track buy-ins, settle the math and share the result with the group. A live product I designed and built solo.
Used by 50+ people · self-reported

Tracking, payouts, and group sharing usually happen across notes, calculators, and WhatsApp.
Re-buys happen mid-conversation, chips move fast, and paper notes drift out of date.
Hosts are left turning cash-outs into balances while everyone is ready to leave.
Final numbers usually end up as screenshots, partial notes, or a long chat explanation.
One host sets up the night. Everyone else follows along from a link.
Four calls about trust, money and where the group already talks.
The product earns trust when it turns noisy table activity into clear balances.
The intended experience: one host-set PIN for editing, a read-only view for everyone else. Light trust at the table without a sign-up wall, not a security guarantee.
Real tables rarely balance exactly. The host corrects counts or reviews a proposed adjustment. The reviewed version refuses invalid values and adjustments that would need negative counts.
The final artifact is built for the chat where the group already coordinates.
Proposed, not outcomes. No results are claimed here.
Shows whether hosts can start a game without friction.
Shows whether users reach the main payoff moment.
Shows whether hosts come back for future games.
The MVP stays focused on solving one workflow well.
Reduced setup friction for casual games, with identity deferred until there is repeat value.
Cash games were the clearest wedge because settlement pain is immediate and frequent.
Kept attention on the table workflow instead of adding another place to maintain presence.
The latest reliability pass was implemented with Claude Code and independently reviewed.
A money-related edit should show what it did before it is applied.
Invalid values and impossible adjustments are blocked, not quietly patched.
When something goes wrong at the table, the host can see it and fix it.
A reviewed reliability update is on a separate branch; database rollout and deployment are pending confirmation.