Local-first football match analysis. Import your own match video, tag moments with a single keystroke while you watch, and export clips around them.
Everything runs on your machine. No account, no upload, no backend.
R1 is feature-complete and deliberately not released. R0 made a working tagging tool — import a match, tag it, review it, export clips. R1 adds the analysis half: draw on the frame, mark where the pitch is, record where players were, see the shape on a top-down pitch, and burn the drawings into exported clips. It is used daily by its author; it has not been published, and the manual acceptance checklist has not yet been run end to end.
R2 (Analyse & Report) is feature-complete and deliberately not released, on the same arrangement as R1: every Must in plans/PRD-R2.md is implemented, the automated suite is green, and the manual acceptance checklist in plans/qa-R2.md has not yet been run end to end. Nothing is recorded as not done: every Must and every Should in PRD-R2.md is built. Charts (FR-90, §18) remain planned for after this release.
See plans/roadmap-R1.md for the milestones and what each one proves (kept locally; see Documentation).
- Import one or more videos per match — halves, or several camera angles. Anything the OS player cannot open directly is prepared for you, losslessly where possible, with progress.
- Playback with full keyboard control: play, seek, frame step, speed, and a transport that keeps up with large 1080p files.
- Your own taxonomy: categories and nested tags, colours, and the keys you bind to them. A standard football vocabulary ships as an editable starting point.
- One-key capture while watching, with pre-roll and post-roll you set once. Events inherit the team and player you are currently focused on.
- A timeline you can zoom, pan, click to seek, drag to select a range from, and filter by tag, team or player.
- Events in chronological order, each jumpable, each with a note, each carrying the moment you actually tagged.
- Review mode that plays a filtered set back to back.
- Clip export, single or in bulk, fast or frame-accurate, optionally joined into one file, with file names templated from match, tag and time. Existing files are never overwritten.
- Thumbnails, analysis export, and taxonomy export/import so a vocabulary can be shared.
- Draw on a paused frame — arrow, line, rectangle, ellipse, polygon, freehand stroke and text, with move, resize, rotate, restyle, layer order, and undo/redo. Each shape has its own time window: its moment, its event's range, or the whole clip.
- Reshape a drawing corner by corner — drag a corner to move it, click the small hollow grip on an edge to add one, and remove a corner with
Deleteor a double click. A rectangle that loses a corner becomes a zone with three sides, without redrawing it. The whole edit is one undo step. - Fill a zone with a pattern — solid, hatch, cross-hatch, or outline only, with the line colour and the fill colour set independently. A patterned zone marks an area without hiding the players in it, and it is what tells two zones apart when colour is not an option. Patterns are drawn from the shape's geometry, so they stay sharp in an exported clip.
- Calibrate the pitch once per video by picking named landmarks (spots, area corners, the centre circle). The app draws the pitch those clicks imply over the frame, so a wrong pick is visible immediately, and it reports how closely the fit lines up and how much of the pitch your points actually cover.
- Pick on a magnified frame when the video is too small to click precisely — the frame at full resolution, zoomed, with the outline drawn on it. The same view is used for marking players.
- Draw on the pitch, in metres — open the Pitch tab on a calibrated video and draw a zone, line or arrow on the pitch diagram. The shape is stored in metres and projected into the camera's perspective, so it sits correctly over the video and follows the calibration if you correct it. Shapes drawn on the video frame stay on the frame and never move. Freehand and text stay frame-only, and the panel says so.
- Give each team a colour in the squads panel, and every marker, position and swatch follows it. Colour is never the only signal: a marker always shows the shirt number — or the player's initials when no number is recorded — plus the team's name.
- Edit a tagged moment on the timeline — the timeline is tracks, one lane per tag with its colour, name and key binding, so you can see which concept happened when. Each event is a bar covering its whole clip, not a tick, so you can see how long it lasts; click a track's name to filter to that tag. Drag the bar to move it in time, drag either end to trim it, or cut it in two at the playhead (the first half keeps the drawings). If a filter is hiding events, the timeline says how many it is showing.
- See the pitch from an angle — switch the pitch diagram between top-down and an angled view with two fixed camera poses (broadcast and a steeper tactical one). The angled view is the same flat pitch and the same shapes, with no height invented: a marker is a label over its position, not a body. You can draw and move shapes there; reshaping a corner is done top-down, where a metre maps straight to the screen.
- Mark where players were by clicking them on the frame. Positions are stored as pitch metres, survive a window resize, and appear on a top-down pitch with shirt numbers and team names. Markers show while the playhead is inside the event and hide when you scrub away, since a position only tells the truth at its own moment. Two moments can be compared, told apart by marker shape as well as colour.
- Burn the drawings into exported clips, each shape at its own time. Off by default, because carrying drawings means re-encoding the picture — the app says so, and the measured cost is about 14% over an accurate cut.
- Analysis files carry the drawings, the calibration and the positions, so a match can be handed to another machine whole. Importing the same file twice adds nothing.
- Reshape a drawing corner by corner — drag a corner, add one with the hollow edge grip, remove one with
Delete. A rectangle that loses a corner becomes a zone with three sides, and the whole edit is one undo step. - Fill a zone with a pattern — solid, hatch or cross-hatch, drawn from the shape's own geometry so it stays sharp in an exported clip and tells two zones apart without relying on colour.
- Draw on the pitch, in metres — the same zone drawn on the pitch diagram appears over the video in the camera's perspective, and follows the calibration if you correct it. Shapes stay in one space or the other, and the app says which.
- See the pitch from an angle — two fixed camera poses beside the top-down view, the same flat pitch and the same shapes, with no height invented.
- Phases — mark a tag as a phase and pressing its key starts a run: a bar that grows as the footage plays, ends where you stopped it, and carries the actions you tagged inside it.
- A drawing's vocabulary — line styles (solid, dashed, dotted, dash-dot) measured in stroke widths so the exported clip matches, named presets (pass, run, dribble, press, cover), curves and line ends (heads, T-bars), and labels drawn with the shape rather than only listed in a panel.
- When each drawing is on screen — a drawing timeline in the Draw panel: one bar per drawing of the open moment, over the event's own span, ordered by layer. Drag a bar to move it and its ends to trim it (the same gestures as a clip), click it to select that drawing on the video, and the playhead crosses every row. A bar with a range you set is solid; a hollow one is following its window, and dragging it gives it a range of its own.
- A drawing that reveals itself — set a pass or shot line to draw itself over the run-up to its moment. It behaves the same while scrubbing and in an exported clip, because both read the same function of the playhead.
- Statistics that say what they counted — group by tag, category, team, player, time or pitch zone; drill into any number and open the moments behind it; compare two groups on one scale. A count of moments and time recorded as a phase are labelled apart and never added together, and a pitch-based breakdown is not offered without a calibration.
- Where the ball went — a density map of where moments were recorded, a pass map and a shot map. A guessed position is drawn hollow, an unknowable one hollow and dashed, and the legend says how many of each.
- The library: one filter across every match — search every match by tag (with sub-tags), team, player, competition, season, date and time, review a result as a sequence that crosses matches, and save a search as a collection (a query, re-run when opened, not a frozen list).
- One report to hand over — a single self-contained HTML file carrying the chosen statistics, the maps and the moments with their frames and drawings. It opens on a machine that has never had the app, with the network off, and two exports of unchanged analysis are byte-identical.
- A project file (
.cpbl) — save a match's analysis as one readable file with a name you recognise (Save project…, Open a project, and a list of recent ones). It records where the footage lives and does not contain the footage. Opening merges into the library and never overwrites. - A pitch inset in exported clips — off by default, top-down, in the corner, with this moment's positions on it and the moment named.
R1 is deliberate about what it does not claim:
- No height. A position is where a player stood on the pitch plane, never how high. One camera cannot recover height, so none is invented.
- No automatic detection or tracking. Every position is placed by hand. Nothing guesses who a player is or follows them between frames.
- One moment per event. Positions belong to a tagged moment, not to a range of frames.
- A partial view is honest, not magic. Where your reference points do not reach, a position is reported as a guess and the pitch outline is not drawn there. Calibrating from a single penalty area is usable inside that area and unreliable outside it.
- A drawing needs a tagged moment. Drawings belong to events; there are no loose annotations.
R2 is equally deliberate about what it does not claim:
- Nothing is inferred from a tag's name. A shot is declared, never read from a tag called "Shot". No number anywhere is a claim about the match — every one counts moments you recorded, and says so on the view.
- No possession, expected goals, expected threat, pass completion, distance covered or sprint speed. The data cannot support them, so the app will not invent them.
- A zone's label comes from the pitch's own axes (
left/middle/right,top/centre/bottom), never "defensive" or "attacking": nothing records which goal a team attacks. - A partial calibration is stated, not smoothed over. Positions outside the area your picks cover are reported as guesses, and counted as guesses.
- A report is a document, not a data store. It is the readable companion to the analysis file; nothing in it can be imported back, and it is not editable in the app.
- Animation is a reduced rate in a clip — 12 frames a second, capped, and a reveal too long to produce is drawn complete and reported rather than silently becoming a static line.
The manual acceptance checklists are in plans/qa-R1.md (R1) and plans/qa-R2.md (R2). Both are written to be run with no developer in the room.
| Layer | Choice |
|---|---|
| Desktop shell | Tauri 2 |
| Frontend | React + TypeScript + Vite |
| UI | Tailwind CSS + shadcn/ui |
| Client state | Zustand |
| Database | SQLite via tauri-plugin-sql, with Drizzle ORM (sqlite-proxy driver) |
| Media processing | FFmpeg, invoked as a subprocess |
| Package manager | bun |
- macOS 12.3 or later (Windows and Linux are planned)
- bun
- Rust toolchain (stable) and Xcode command line tools for the desktop build
- FFmpeg — detected at startup. If it is missing, importing and tagging still work; preparing files and exporting need it, and the app says so and points you at an install rather than failing later.
bun install
# Desktop app — the real development target
bun run tauri dev
# Frontend only, in a browser. Useful for UI work, but Tauri APIs are unavailable.
bun run dev| Task | Command |
|---|---|
| Frontend dev server | bun run dev |
| Desktop app | bun run tauri dev |
| Production desktop build | bun run tauri build |
| Lint / format | bun run lint / bun run format |
| Typecheck | bun run typecheck |
| Unit and integration tests | bun run test |
| Rust tests | cargo test --manifest-path src-tauri/Cargo.toml |
| Generate a database migration | bun run db:generate |
| Generate test footage | ./scripts/make-demo-clip.sh |
src/features/ one slice per product area: library, player, timeline, tagging, events,
review, annotate, pitch, export, settings
src/lib/ ipc (the only place that talks to Tauri), db (Drizzle), media, jobs, playback,
time, settings, transfer, annotate (pure geometry), pitch (pure maths),
render (the one canvas renderer)
src-tauri/ thin Rust shell: plugins, commands, subprocess jobs
tests/ unit tests, and integration tests that run the shipped SQL against real SQLite
Committed to this repository:
DESIGN.md— design system, tokens, and UI rulesAGENTS.md— instructions for coding agents, including the architecture rules
Kept locally and intentionally not published: the product requirements, technical design, roadmap, and architecture decision records. They are working documents that change faster than the code.
This repository ships no match footage, and it never will. Generate synthetic clips for development and tests:
./scripts/make-demo-clip.shThis writes an H.264/AAC MP4 (plays directly) and an equivalent Matroska file into tmp/demo/, which is gitignored.
Read CONTRIBUTING.md and AGENTS.md before opening a pull request. In short: run bun run lint, bun run typecheck, bun run test, and cargo test --manifest-path src-tauri/Cargo.toml before submitting, and use Conventional Commits.
AGPL-3.0 — see LICENSE.
You are responsible for the footage you analyse with this tool.