The story
A score tracker, player leaderboard and venue book for a padel group in Lahore.
The scoring problem
Padel scoring is the interesting part. The counter implements the full progression through 15, 30, 40, deuce and advantage, plus the sudden-death golden point the group actually plays, and it does so as state rather than as a display. Undo exists because a mis-tap during a live match is the normal case, not the exception.
The interface
Full-screen and mobile-first, with two tap zones, one colour per team. It is designed to be used at arm's length on a court, not read.
Records
Matches are doubles, best of five sets. Players and venues are full CRUD, and deactivating a player hides them from new match setup while keeping their history intact, which is the difference between deactivation and deletion. Every match keeps a point-by-point log, so history is never reconstructed from a final score. The dashboard reports played, win and loss counts, win percentage, sets won and lost, venue usage and recent activity.
Stack notes
Next.js App Router with Tailwind, Drizzle ORM over Turso.
What made it hard
Scoring as state
Modelling deuce, advantage and a sudden-death golden point as real state transitions rather than as display formatting
Usable at arm's length
An interface operated mid-rally on a phone propped on a bench, where a mis-tap must be recoverable
History that survives edits
Deactivating players and editing matches without losing the point-by-point record already captured
