News · New this week
Gully Cricket Scorer, built with Claude in 25 minutes
A cricket scoring app that stores every ball instead of the total, so undo is simple and nobody can argue about the fifty.
In gully cricket nobody writes the score down, so everyone remembers it differently. Day ten was an app to settle that. The limit was one hour. It took twenty-five minutes.
What it does
Gully Cricket Scorer is a phone app. On the ground you tap each ball. Four. Six. Wide. Out. Every run goes next to a name, which is what ends the "I scored fifty" argument. My app said twelve.
If the ball is in your hand, tap the mic and say it. Four. Wide. Undo.
It also works out the chase for you. At one point it said four off eleven, and a boundary finished the game. Friends who couldn't come can follow along too. Tap Go live, send them the link, and they watch every ball as it happens.
When the match is over, one tap turns the scorecard into an image for your group chat. Next time someone says fifty, the group can check.
How it was built
If the point is settling fights, the counting has to be perfect. So I asked Claude to plan the app first, and showed it a real scoring app to copy the look from.
Then Claude Code built the counting part first, with nineteen small checks that it counts right. Four of them failed. Three were written wrong. The fourth caught a real bug. Undo was deleting a ball from the other team's batting. That is exactly how score fights start.
One fix and all nineteen passed. Only after that did I put my own colours on it.
The order is the useful bit. Get the logic right and tested before you touch the styling.
Save the balls, not the total
The app never saves the total. It saves every ball, and adds them up again on every tap.
That makes undo simple. It just removes the last ball, and the total always matches.
Your matches are saved on your phone. That means no login, and scoring works on a ground with no signal.
Try this
If you're building anything that keeps a running count, store the events and work out the total from them. Then write small checks for the counting before you do anything else. Three of mine were written wrong, and the one that wasn't caught a real bug.
