Foundation
A Friday darts problem became the starting point
Board Ready Darts began as a practical answer to a club-night problem: how to quickly turn the players who turned up into a clean schedule that could be written onto the board.
Board Ready Darts
Development Timeline
Major milestones in the growth of Board Ready Darts.
A look at the design journey behind Board Ready Darts, from a simple Friday darts scheduling problem to a focused app for creating clean, board-ready singles and doubles draws.
Core idea
The numbered board became the heart of the app
The app settled around a simple board format: each player or team gets a number, and the schedule shows who each number plays across five games.
Product focus
BRD became a draw planner, not a league platform
The project deliberately moved away from scores, rankings, league tables, and tournament management. Its purpose became clear: select players, generate the draw, check the board, and save the schedule.
Schedule model
Singles and doubles became the two core modes
The app was shaped around real club-night use. Singles uses one player per place in the draw, while doubles builds teams first and then creates the schedule from those team numbers.
Doubles decision
Mixed pairing became the preferred doubles behaviour
Doubles was defined to create mixed pairs where possible, then fall back to same-group pairs only when needed. If there is one player left over, that person remains in the schedule as a single-player team.
Odd-number problem
The one-BYE model became a key breakthrough
Odd player or team counts were one of the biggest scheduling challenges. BRD settled on a board-ready opponent-list model where one side has one BYE, instead of forcing a BYE in every game column.
Template stage
Approved odd schedules gave the first build a stable base
The first version focused on known useful odd schedule templates, alongside generated even-number schedules. This gave the app a reliable foundation without overbuilding the generator too early.
Validation layer
The app started checking the schedule, not just showing it
Schedule validation became an important part of the app. The draw needed to check for repeated opponents, invalid numbers, wrong BYE counts, and missing reciprocal matches.
Player flow
Player selection became part of the real club workflow
The app moved beyond a blank number generator and began supporting saved players, attendance selection, player counts, and named views for games.
Screen structure
The app flow was simplified and locked
The app structure was refined into Home, Create Schedule, Current Schedule, View Games, Add Player to Schedule, Manage Players, History, Saved Schedule Detail, and Settings.
Visual identity
BRD found its dark sports-app direction
The app moved toward a sleek modern sports style: near-black backgrounds, charcoal cards, gold branding, warm white text, subtle green accents, and clean row actions.
Current development
The app is being shaped into a usable club-night tool
Current work is focused on turning the locked structure into a smooth app experience: creating schedules, handling singles and doubles correctly, improving player management, polishing the current schedule view, and keeping the visual design aligned with the BRD identity.
Next focus
The next stage is refinement, testing, and presentation
The next development focus is to keep improving the real organiser workflow: faster player search, clearer team/player display, stronger schedule presentation, better saved history, and final visual assets that match the locked sports-app direction.