PlayProtocol & the Protocol family

Drills a coach can actually run.

PlayProtocol grew out of the injury-prevention movement screenings that Cape Concierge Physical Therapy runs for school sports programs. The screenings kept surfacing the same gap: coaches wanted the warm-up, strength, and recovery work the PTs prescribed, in a form a team could actually follow — not a PDF, not a YouTube playlist. So we built it as a product: over 75 drills, every one filmed rep by rep by physical therapists, organized by sport across soccer, football, field hockey, and lacrosse.

The trust model is deliberate: every sport opens with free warm-up drills a coach can run at the next practice — no account, no sign-up, nothing collected. Programs that enroll with the PT team get their teams' prescribed drill protocols and daily check-ins layered on top.

LAXProtocol was the first sibling: its own brand, its own content line, a full season of lacrosse-specific work — running on the same backend, the same content pipeline, and the same client codebases. Both ship on the App Store and Google Play.

SoccerProtocol and HoopsProtocol followed the same road — soccer's agility and first-touch work, basketball's landing mechanics and form shooting — each with its own home screen, its own vocabulary and a habit built for the player alone. Both ship on the App Store and Google Play.

HomeProtocol points the same system at a different reader entirely: not a coach or a squad but the patient at home. Everyday warm-ups for the walk, the golf round and the pickleball match, and — when a physical therapist hands one over — the patient's own plan, loaded by a single code into the same player. Free, with nothing for sale, on the App Store and Google Play. Five store identities, one system.

Five apps, one clinical program.

Each app is its own store identity with its own home screen, vocabulary and content line — forked at the symbol level, not re-skinned — on one backend and one content pipeline. What each one is for:

PlayProtocol

iOS · Android

The original. Warm-up, strength and recovery drills across soccer, football, field hockey and lacrosse; free warm-ups in every sport, and enrolled programs' prescribed protocols and daily check-ins layered on top.

Site →

LAXProtocol

iOS · Android

Lacrosse, under its own brand. Most lacrosse injuries never involve contact; this is the warm-up, speed and strength work that lowers that risk, with free drills in every part of the program and printable handouts, and no account anywhere.

Site →

SoccerProtocol

iOS · Android

Home is laid out the way a match unfolds, Pre-Match through Full Time. The habit for a player alone is a timed nine-station wall routine and a juggling ladder — counted, not clocked. Touchline calculators for sweat rate, single-leg hop symmetry, workload spikes and heat index; handouts a coach can text to a parent.

Site →

HoopsProtocol

iOS · Android

Home is a coach's half-court diagram, each section anchored where its work happens. Landing is taught as a skill, and form shooting keeps score: nine timed stations from Mikans to free throws, two thumb-sized make and miss buttons, and a shot chart drawn on the floor the session happened on.

Site →

HomeProtocol

iOS · Android

The patient at home. Warm-ups for walking, golf, pickleball and the garden, a ten-minute morning routine, and timed balance practice logged as plain seconds. A physical therapist's plan arrives as one eight-character code and runs in the same big-type player. Free, nothing for sale, no account.

Site →

What it does.

How it's built.

Ten native clients across five apps collapse into one Go backend, one SQLite database, and one content pipeline. Each client is native: SwiftUI on iOS, Kotlin / Jetpack Compose on Android, sharing the same API. Drill video lives in S3-compatible object storage and is served through time-limited signed URLs, minted only after the server has decided what that caller is entitled to see.

The paywall decision is made once, server-side, per catalog request: the client sends its store receipt, the server verifies it against Apple's and Google's APIs, and locked content is simply absent from the response — no signed URL is ever minted for a tier the caller hasn't bought. A client bug can't leak what the client never received.

The parts worth writing down.