The app that runs dragon-boat racing

A native iOS and Android app for dragon-boat racing clubs — membership, teams and seat-by-seat race-crew line-ups — engineered and evolved over three-plus years.

The Dragon King app on a phone showing a dragon-boat crew line-up — paddlers arranged in ten numbered seat pairs down the boat with a drummer at the front, and Save and Balance controls.
Client
Dragon King
Platforms
iOS + Android
Engagement
3+ years
Sport
Dragon-boat racing

Getting a dragon-boat crew onto the water is a logistics problem before it’s a race: the right paddlers, in the right seats, in the right boat, for the right event. Dragon King is the mobile app that runs it — and Toobler engineered it, on iOS and Android, and evolved it with the sport for more than three years.

Customer and context

Dragon King is a mobile app for dragon-boat racing — the paddle sport where crews race long, narrow boats. It is built for the people who organize the sport: club directors, team captains and paddlers. A director registers a club, members join with a club code, and the club’s teams, crews and races are all run from a phone. Toobler was the engineering partner that designed and built the product across iOS and Android, and kept developing it from 2015 through 2018.

The challenge

A dragon-boat club is a moving-parts problem that generic team apps don’t solve:

  • Crews are seat-by-seat line-ups, not just rosters. A boat isn’t a list of names — it’s a configuration: paddlers assigned to seats, balanced across the hull, sized to the boat. The app had to model the boat, not just the team.
  • Clubs, teams and members are a hierarchy. A director creates a club; members join by code; teams are built from members; crews are drawn for each race. Roles and permissions run through all of it.
  • It had to work on the water, on any phone. iOS and Android, portrait and landscape, for volunteers and paddlers — not office staff at a desk.
  • It had to keep evolving. Across three years and multiple releases, with new features and fixes as clubs actually used it.

The solution

A club-to-crew model, built for the sport. Toobler built the domain properly:

  • Club registration — a director signs up, a club is created, members join with a generated club and user code.
  • Roles, members and teams — who belongs to what, and who can change it.
  • Race-crew line-ups, the heart of it — create a race, draw a crew, and arrange paddlers into a boat’s seats, filtered by boat size, category and favourites, with teams you can copy and reuse.

Native on both platforms. The app was built native for iOS and Android, with every screen designed for portrait and landscape — usable on the dock, not just the desk.

A backend to match. A Node.js backend with token-based sessions, push notifications and image handling on AWS served both apps from one source of truth for clubs, members, teams and races.

Built and evolved as a partnership. From the first Android build through the iOS release and successive versions, Toobler developed Dragon King over more than three years — shipping features, fixing what real clubs hit, and growing the product with the sport.

Engineering worth naming

  • Modeling the boat, not just the team. The seat-by-seat crew line-up — sized to the hull, filterable, reusable — is the thing off-the-shelf team apps can’t do. It’s the product.
  • A proper club hierarchy. Director → club → members → teams → race crews, with roles and code-based joining, built end to end.
  • Native iOS + Android from one backend. Two native apps, one Node source of truth.
  • A multi-year build. Engineered and evolved across three years and multiple releases.

Results

  • A dragon-boat club runs from a phone — registration, membership, teams and race-day crew line-ups, on iOS and Android.
  • The boat is modeled, not approximated — paddlers placed seat by seat, sized to the hull, reused across races.
  • A product that grew with the sport — built, released and evolved over three-plus years as a long-term engineering partnership.

What this means for sports software

Sports software lives or dies on whether it models the actual sport — a dragon-boat crew is a seat-by-seat line-up in a specific hull, not a roster; a season is fixtures and results, not a calendar. Dragon King is that principle in practice: a custom mobile product engineered on the real rules and workflow of the sport, native on iOS and Android, built and evolved by a long-term partner. If you run a club, league or federation and need software built around how your sport actually works — not bought off a shelf — talk to Toobler’s engineering team.

Let's talk about your project.

Start with one measurable use case.

A Readiness Sprint is a fixed-scope engagement that maps your integration and AI readiness and produces a production-oriented plan — before anything is built.