Skip to content
← All workSport & leisure · One day, plus a morning
1day from a stalled project to an app ready to submit
Epic Life Watersports, a paddling club and watersports centre logo

Epic Life Watersports, a paddling club and watersports centre

The Epic Paddle Challenges feed, each paddle showing its GPS route
The feed. Every paddle draws its own route.
The record screen, with paddleboard, kayak and other activity types
Record. Live GPS, or log it by hand.
A paddle in detail, with its full route and comments
A paddle in full, with its route and comments.
A speed challenge leaderboard ranked by fastest time
Speed challenge. Ranked by fastest single effort.
A paddler profile with running totals
Profile. Running totals, every paddle.

What capped them

An app on TestFlight that nobody could change, built on a no-code platform and seven months adrift from its own source

What we built

A custom iOS app rebuilt from nothing: database, live GPS tracking, design system, brand mark and App Store submission

How long

One day, plus a morning

What was capping them

Epic Life Watersports run paddling out of Sussex. They already had an app on TestFlight and real paddlers using it: sessions logged, club challenges running, everyone able to see where they stood.

The problem was not the app. The problem was that they could not change it.

It had been built on a no-code platform, and the only source anybody could recover was an export from seven months earlier. Features had shipped in that gap that existed nowhere in the code. The data model was whatever the builder had produced rather than one anybody had designed. Every change they wanted next ran into the same wall, and so did every developer they might have handed it to.

What we built

A custom iOS app, written from nothing, with the app they already had as the specification.

Underneath it, a relational database designed around how a paddling club actually works, so challenge standings are worked out from the paddles themselves rather than cached in a number that can drift out of step. On top of it, the things a no-code builder was never going to give them:

Then a look of its own: a deep blue-green ground because English water reads green rather than navy, one bright accent carrying every active state, and a paddle blade over its own wake as the app icon.

The signature element is the paddle's route, drawn as a single line on every post and live on the record screen as you go. It is built from real GPS, so a paddle with no track draws nothing rather than inventing a shape.

The wake: a real route, drawn one stroke at a time.

How long it took

The first commit was at half past five in the evening. By eleven that night the app was building for submission, and the next morning finished the App Store screenshots and confirmed the final change against the live backend.

That speed is not corner-cutting, it is the order of the work. The database was designed and tested before a single screen existed, and the GPS maths was written so it could be tested off the phone. By the time the screens were built, everything underneath them was already known to be right.

We also told them what not to ship. An app with public posts and comments needs reporting, blocking and moderation before Apple will pass it, which is another day's work. Sending it without would have bought a rejection and a delay.

What changed

They have gone from an app nobody could touch to one they own outright: a database designed for their sport, code any developer can open and read, and a brand that came out of the subject instead of a template. The next change they want is a conversation, not a wall.

Same problem, different business?

If you recognised yourself in this, the call is the fastest way to find out what a day would fix.

Book a 30 minute call

More work