Designing a scoreboard interface that stays readable under pressure
Mickey Scoreboard got better when the interface stopped trying to be a control panel and committed harder to being a scoreboard.
The original direction for Mickey Scoreboard was already opinionated: use the race-to-close Mickey ruleset, treat Darts-Oche as the canonical rules source, and avoid switchable rules variants. That constraint was useful because it kept the product from turning into a generic darts rules engine.
What became clearer after launch was that most of the quality came from subtraction. The release history through v0.2.5 does not show a product getting better by layering on more chrome. It shows a product getting better by removing what interrupted play.
In v0.2.2, the separate score-entry button section was removed so the scoreboard could stay the main interaction surface. That was more than a visual cleanup. It changed the posture of the app. It felt less like operating a dashboard and more like keeping score. Around the same time, the risky inline minus-one correction button gave way to long-press correction on the current-player score cell.
The later releases kept following the same logic. v0.2.3 tightened the header for smaller phone screens. v0.2.4 removed the three turn slots, the "Darts entered this turn" label, the redundant turn heading, and extra controls like Undo Last Dart and Clear Turn. v0.2.5 then fixed turn-history recording for scoreboard taps and added a persistent round label under the table.
That sequence is why the scoreboard-first idea matters. Readability under pressure is not only typography or spacing. It is about reducing choices in the moment when players are moving quickly and attention is already split. Every unnecessary control asks for thought at the wrong time.
The strongest version of this product turned out to be the one that stayed closest to the board itself. That is usually a good sign in interface work. When the main object is clear, the design should stop competing with it.