Overview
Mickey Scorekeeper started as a focused PWA for Mickey darts with a touch-first interface and local-first persistence. The core product goal was clear from the beginning: make scorekeeping fast enough to stay useful during a game, then keep polishing only the pieces that support that speed.
Why this project exists
The project exists because darts scorekeeping is simple right up until the interface gets in the way. The product direction favored one canonical rules source, Darts-Oche, and intentionally avoided switchable rules variants so the app could stay opinionated and clear.
What was built
- A scoreboard-first game flow with tap-to-add marks
- Local persistence, install affordances, and finished-game history
- Touch corrections via long-press instead of cluttering the board with extra chrome
Project scope
The most interesting part of Mickey Scorekeeper has been the steady tightening of the interface. Recent shipped releases through v0.2.5 removed extra turn chrome, simplified active-game controls, improved recent-results history, and fixed turn-history recording so scoreboard taps are stored as real turn entries. That makes the project a good example of feature restraint improving usability over time.