Everything BatSwing does, and how far along it is.

Ball splitting with one‑tap confirm

One continuous side-on recording per batter, up to about 10 minutes, split into balls automatically. BatSwing listens for bat on ball and watches the downswing. The coach reviews the detected balls, drops a false one or adds one it missed.

Then a one-tap ball sheet: middled, edge, beaten, missed, left (good or poor) or unknown. The computer suggests, the coach confirms. A suggestion never counts until the coach taps, and the latest tap wins.

One bowler, one clip, split into deliveries

The coach films the whole spell side-on from the bowling-arm side, up to about 10 minutes, one bowler per clip. BatSwing finds each delivery from the bowler's movement, so sound is not needed.

The coach reviews the deliveries it found, drops a false one or adds one it missed.

Tested on demo data and broadcast clips so far.

Key frames, suggested and confirmed

Four moments of each delivery: the back foot lands, the front foot lands, the approximate release and the end of the follow-through. BatSwing suggests each one. The coach goes to it, steps a frame or two if needed, and confirms it or marks it as not visible.

Suggestions hold up on clear side-on video; filmed through a net, the coach marks more of them.

Where it met the bat (coach-marked)

BatSwing offers the frames around each shot. The coach picks the contact frame, taps where the ball met the bat face and says which foot it was played off.

Over a session the marks build up on one bat, by foot and by drill, with the unknowns counted. The coach's call, not a measurement.

Pilot feature. On real recordings the suggested frame is only a starting point.

Where it went (coach-tagged)

On the ball sheet the coach taps which of eight areas each hit went to, or marks it unknown. BatSwing counts them per area, seen from the bowler's end and mirrored for a left-hander.

A count per area, never a distance. A share shows only from 15 tagged balls. The coach's call, not a measurement.

Pilot feature. Tried on demo data so far, not yet on an academy's sessions.

Where it landed (coach-tagged)

For each delivery the coach tags the length it landed on (full, good or short) or marks it not seen. BatSwing counts them against the target the coach set. A side-on phone shows length, not line.

The coach can also note where the front foot landed against the popping crease: behind, on or over the line. The coach's call, not ball tracking and not a no-ball call.

The coach's call, not ball tracking. Shown on demo data.

Footwork vs crease (coach-calibrated)

The coach taps the four corners of the crease once per session, then marks where each foot landed. BatSwing shows the marks against the popping crease and the middle-stump line, as counts.

A foot too close to a line is not counted either way. Positions only: no distances. It needs a still, raised phone that sees the whole crease.

Pilot feature. Tested on demo data only; needs that phone position at an academy next.

Progress and trends

Control by drill, session after session, always with its denominator: "15 of 20 attempted balls middled". Leaves are counted separately, because a good leave is a good decision. Every trend links back to the clips behind it.

A trend arrow appears only when all five hold:

1. The latest 3 sessions are compared with the previous 3, not one good day.
2. Each of those sessions has 15 or more attempted balls.
3. The drill is the same: shot, bowling, length, feed and pace.
4. The ranges don't overlap, and every recent session beats every earlier one.
5. There's no camera or software change in between.

Otherwise it says which applies: not enough data, change not yet clear, or withheld.

Recorded bowling, beside your guideline

Confirmed deliveries add up to bowling days, spells and overs. On the coach's screen they sit beside the junior bowling guideline the academy chooses. In Australia and the UK it starts on Cricket Australia's or the ECB's; elsewhere the academy picks one.

It counts what was filmed, so bowling outside these sessions may be missing.

A record of filmed sessions, not a full workload record.

2.5D replay

Cut-outs from the real frames, layered with gentle parallax, so a coach and player can revisit a ball together. Trails follow points on the body and the bat. The bat trail is left out when the detector isn't sure, rather than guessed.

It says what it is on screen: "2.5D replay from one camera. Not a 3D measurement."

Ghost overlay

An earlier ball faded over a later one, lined up on the moment the bat meets the ball, so a player can see how the swing has changed. A picture to compare, not a measurement.

Pilot feature. Lines up only when the phone stood in the same place both times.

Ghost overlay for bowlers

An earlier delivery faded over a later one, lined up on the moment the front foot lands. If the phone stood nearer or further away, the earlier picture is sized to pin the front foot. A picture to compare, not a measurement.

If the phone moved, the bowler lines up but the ground may not.

Focus: one cue, checked next session

The coach sets one thing to work on, with a drill and an aim. It is on the coach's screen before the next session. Afterwards the coach enters what they saw: balls checked, the aim met or not, and any they couldn't see.

Unknown balls stay in the count, so the outcome reads met, not met or unclear. The player sees what they are practising, what happened and what is next.

Pilot feature. For bowlers, the Focus is carried onto the bowling report. Email updates to players are not switched on yet.

Teaching clip

One ball, slowed down and held still at the moment of contact, with the coach's caption and your academy's name on it. Made on the coach's phone and sent from its share sheet, to WhatsApp or any messaging app.

Pilot feature. Not yet checked in WhatsApp on real Android phones and iPhones.

Two-angle synced playback

Add a second phone front-on, behind the bowler's end. BatSwing lines it up with the side-on phone using the sound of bat on ball, and each ball plays back from both angles in sync.

Pilot feature. Sync thresholds are not yet validated on real footage. The extra set-up

See the shot from any side

With a second phone, a view of the batter's pose that the coach can turn round and look at from the off side, the leg side or the bowler's end.

Not built for real recordings. The preview here is simulated on demo data: nobody's video went into it.

3D estimate from one camera

From one phone video, BatSwing wraps the player's own video onto a 3D estimate of their body, so the real gloves and bat show. In the viewer, drag to turn it, zoom and pan.

It stays near the camera that filmed it, because one camera cannot judge depth well. The yellow ribbon is the bat's path, dashed where the bat was a blur. A preview, not a measurement: no numbers, never in a report.

Not in the app yet: one library clip. Bowling comes next.

The same shot, replayed phase by phase

The replay pauses at stance, backlift, stride, impact and follow-through. The pose skeleton, where each foot landed and the bat's path are drawn over the same 3D estimate. The bat's path is a yellow ribbon with a thin ink edge; it is dashed where the video shows the bat only as a blur, so that stretch is an estimate, not something the camera saw.

Same library clip, same limits: shapes only, no numbers, never in a report.