LaneLab

The problem

The service is simple to describe and hard to sell from a brochure page. A swimmer has to see the loop before paying for it: footage goes up, and a marked-up review comes back with the one fix that matters. Writing that down as a spec would have taken weeks and still left everyone imagining a different product.

What got built

Fifty-three routes across three areas (marketing site, member portal, coach console) on Next.js 16 and Tailwind v4, with no runtime dependencies beyond React itself. The mock data sits in typed modules shaped like the API responses a real backend would return, so phase two swaps the data layer instead of rewriting screens. A shared password gate signs an HMAC cookie and fails closed: no password configured means nothing is served.

Details worth naming

• Three app areas in one build: public marketing site, member portal, and coach console, sharing a single shell.
• The whole loop is clickable: attach camera angles against a validation rule, then read the annotated review with its timestamped fixes and prescribed drills.
• The coach queue sorts on the 72-hour review deadline and flags anything past it, because that turnaround is the product's actual promise.
• Typed mock data modelled on real API responses, so the database work ahead is a swap rather than a rewrite.
• Placeholder copy, sample testimonials, and stand-in photography are all flagged on the page itself, so nothing in a review build can be mistaken for signed-off content.