simple-coding

Field hockey match coding and review in one browser app. Log the game on the sideline or from an MP4, keep a lead/lag window on every event, and present the clips without an NLE or a render queue. Games stay in the browser.

The full product test for what we build next is Core Friction Points & Product Intent.

Run it

You need Node.js 20 or newer. Open this folder in Cursor or VS Code.

git clone https://github.com/dneimke/simple-coding.git
cd simple-coding
npm install

Press F5.

The simple-coding launch config starts the server, attaches the browser debugger, and opens Matches with the sample match already listed (8 events, FIRE and TIGERS). Breakpoints in src/ bind to the page. The server uses port 3000 and moves to the next free port if 3000 is taken. F5 follows the port it prints.

Launch config	What opens
simple-coding	Matches, with the sample game. This is F5.
simple-coding (Edge)	The same page in Edge, when Chrome is not installed.
Live capture	The event board, clock at 07:05, four events already logged.
Match review	The sample timeline, favorites, and video player.
Jest: current file	The test file you have open, under the debugger.

From a terminal, npm start prints those same URLs and opens Matches. BROWSER=none npm start leaves the browser alone (F5 sets this).

npm test
npm run test:watch
npm run test:coverage

Screen	URL once the server is up
Matches, sample game	http://localhost:3000/index.html#saved-games?mock=sample
Live capture, in progress	http://localhost:3000/index.html#event-capture?mock=active
Match review	http://localhost:3000/timeline-video.html?game=sample-game
Continue coding	http://localhost:3000/timeline-video.html?game=sample-game&mode=tag
In-app guide	http://localhost:3000/index.html#help

The three problems

Coaches currently split one match across Sportscode, a video editor, a spreadsheet, and a lot of scrubbing. simple-coding exists to take those three costs out of the week.

1. Game setup divergence

Setting up two teams, then taking a different path for a live sideline game than for an MP4, burns the minutes before pushback.

Today, every match starts from + Create Match on the Matches screen. The same hub offers three starts, and each one sets the clock for the way you are working:

• Live Match is the pitch stopwatch. Tap Start on the whistle. Team-coloured buttons stay put, sticky zones 1–4 ride along with each tap, and the top bar shows Last: <Event> · mm:ss so a glance confirms the code. Undo is one tap, or Ctrl+Z.
• From Video has no separate stopwatch. Scrub or pause at 14:20, tap a code, and the event is stored at 14:20 with that button's lead and lag. Playback runs at 1.5x or 2x, with -5s / +5s / +10s to skip stoppages.
• Import XML turns a Sportscode or MyVA file into a saved match. Each instance keeps its start and end, so a click seeks to the build-up of the play.

Product goal: teams are defined once and chosen from a short list, and one clock engine accepts either the match stopwatch or video.currentTime without a different workflow. See Friction 1.

2. The two-pass coding slog

Coding at 2x can turn 80 minutes of video into about 40. A required second pass for zones, where the ball came from, and tactical modifiers puts another 15 minutes on the end and stalls review.

Today the first pass already carries the spatial code, and the second pass is a short sweep instead of a re-watch:

• On the sideline, tap a zone once as the ball changes quarter. Later buttons inherit it (FIRE BS2) without a second tap per event.
• From video, the Quick Tag bar sits under the player. Tags save as you go. Continue coding on any saved match opens that same timeline at 1x, 1.5x, or 2x so a coach tag (Press, Outlet, Turnover) lands on the events you already have.
• In Match Review, Sweep jumps about 3 seconds before each unlabelled clip. Keys 1–3 assign the pill (Left, Center, Right), Space skips, and the next clip loads immediately. Twenty circle entries can be flanked in about a minute. Possession origin is derived: a Ball Won within 10 seconds marks the entry as a counter-attack; otherwise it is settled build-up. You do not tap a separate origin button.

Product goal: the modifier is part of the first tag. Tap C for Circle Entry and a short overlay offers Left, Center, or Right before the moment is gone, and state memory fills the modifiers that follow from the code you just logged. See Friction 2.

3. Post-match clip assembly

After the codes exist, scrubbing in and out points and rendering slices for the coach meeting takes about 45 minutes.

Today the clip window is decided when the button is designed, and review plays those windows in the browser:

This is the beginning of the README. Read the rest at the original. Read the full README ↗