Your app. A bigger player pool.
Excellent independent darts apps often struggle to gather enough players for online multiplayer to feel alive. DartXchange is designed so you can keep your app, your users and your scoring technology — and still offer them opponents.
Status: DartXchange is in its foundation phase. Registration is an enquiry only, and the integration described here is a design, not a shipped product. Details may change as we build and test with early partners.
Why join?
Solve the empty-lobby problem
Smaller apps share one pool of opponents instead of each waiting alone.
Keep control
Your branding, accounts, scoring engine, camera system and interface stay yours.
Don’t build it all
Matchmaking, cross-app match coordination and video signalling are shared infrastructure.
Neutral by design
No single app owns the network. Any compatible app may take part.
Flexible scoring
Automatic and manual scoring apps can both participate, with lobby creators choosing what they accept.
Seamless for players
Players stay in the app they already use, with their existing login and username.
How joining is planned to work
1. Registration
You submit your application details (name, website, scoring method, multiplayer status). Applications are reviewed so references and credentials are issued to genuine apps.
2. Application reference
DartXchange issues a unique short reference (for example DF) plus a public application ID and private server-side credentials. The reference becomes the suffix shown with your players’ names.
3. Player identity
Your server tells DartXchange who the player is: their existing username and your reference. DartXchange maps this to a permanent unique player ID and builds the display name, e.g. 180King-DF. Players never choose or type the suffix.
4. Lobby inside your app
Your app fetches lobbies from the DartXchange API and shows them in your own interface, in your own style. Players create or join games without leaving your app.
5. Match coordination
Once two players are matched, DartXchange coordinates the match: format, player order, visits, busts, checkouts, legs and sets, results, and disconnect/reconnect handling.
6. Video connection
Your app provides its own camera feed. DartXchange handles WebRTC signalling so each player can see the other’s board; direct connections first, TURN relay as fallback.
Security principles
- A public application identifier, plus private credentials that live only on your server.
- Private secrets are never placed in browser or mobile client code.
- Application and player identities are validated server-side.
- Match events are idempotent, so duplicates cannot double-count a visit.
- Authentication and rate limiting are required in the eventual backend.
Illustrative identity hand-off
// Proposed / illustrative - not implemented
{
"app_id": "app_pub_example",
"app_ref": "DF",
"player_username": "180King",
"player_app_id": "your-internal-id"
}
// -> permanent DartXchange player ID
// -> display name: 180King-DF
Full proposed API design →Interested in being an early partner?
Tell us about your app. This is an enquiry preview — see the form for exactly what it does and doesn’t do.
