Performance
A competition runs in real time. Every avoidable refresh costs seconds, and enough of them put an event behind schedule. Responsiveness is a scheduling requirement here, not a refinement.
Roadmap
Where This Is Going
Running your competition is the foundation, and it is built. This is what is being added on top of it — the four commitments that come before any of it, what is being built now, and what is under consideration next.
This is a statement of intent, not a delivery schedule. Nothing here carries a date, the order changes when a competition on the floor makes something more urgent, and items in the later band may arrive differently than they are described.
Last reviewed Sep 5, 2026
Standing Priorities
Four commitments that take precedence over every feature on this page. When one of them is at stake, it is addressed before anything below is built.
Security
The system holds personal data and competitive results. Protecting both is a continuous discipline, not a certification obtained once and filed away.
Bug Fixes
On competition day a defect has consequences — a missing entry, an absent mark, a result that does not reflect the floor. Defects take precedence over all planned work.
User Experience
Built to the standard of a well-run competition rather than to “good enough.” Friction is recorded and prioritized like any other defect.
Being Built Now
Decided and designed. These are the next things to arrive, and work on them is already underway.
Designed, committed to, and being built.
Private competitions
Invitation-only events, kept off the public listings. Only the guests an organizer invites can take part.
Start next year from last year
Pick a past competition, choose what carries over — sessions, floors, events — and skip most of the setup.
Letting the Chair of Judges correct a result
Rule checks and unusual cases happen. The Chair of Judges or Scrutineer can correct a result inside the system, with a record of who changed what.
A screen for the DJ
The competition as the DJ needs to see it: what is dancing, what is next, and what music each heat calls for.
Under Consideration
These are wanted, and they are being thought about seriously — but they have not been designed in full. Expect them to change shape.
Intended, not yet designed. Some of this will arrive differently than described here.
Payments and ticket sales
What organizers ask for most — entry fees and spectator tickets in the same place the competition is run. Hard to get right, so it is being designed carefully.
Sign in with Google or Apple
One less password to invent and remember, and safer than another one.
The machinery underneath
A wild card. What the system runs on is enough for today; a much busier future could mean rebuilding a good deal of it.
A public API for dancesport developers
Scraping the public pages is inefficient for you and costly for us. Under consideration: a documented, versioned read API over competitions, entries, and historical results, so community projects can query the data directly.
This List Is Not Fixed
Dancesport.app is built by someone who competes and scrutineers, and it is shaped by the organizers, adjudicators, and dancers who use it. If something here matters to your competition — or something that matters is missing entirely — say so, and it will be weighed against everything else on the list.
Write to [email protected], see what has already shipped in the release notes, or read how the product got here.