What TrackSpeed records
TrackSpeed turns an iPhone camera into an automatic timing point for sprint training. The athlete or coach places a visible timing line in the camera view. When the configured crossing occurs, the app records the event and uses it with the session's start event to calculate elapsed time.
A measured distance and elapsed time can also produce average speed. That number is only as trustworthy as the course measurement and the start and finish definitions, so TrackSpeed treats setup as part of the test—not as a detail to ignore.
Four parts of a trustworthy training time
1. A defined event
The timing line and start mode say exactly what starts and stops the clock. A flying split and a movement start are different tests and should be labeled differently.
2. Automatic recording
The app records the configured crossing without a coach pressing a stopwatch at the finish, removing that manual stop reaction from the workflow.
3. Reviewable evidence
The finish evidence can be inspected after the rep. If the camera moved, the view was blocked, or the line was wrong, the result should be rejected rather than explained away.
4. A repeatable protocol
Distance, start position, line placement, phone side and height, surface, footwear, recovery, and environmental conditions should remain documented and consistent.
One phone or several timing points
A single-phone session supports solo training workflows. When a test needs separate start, split, and finish locations, additional iPhones can join the session and record events at those positions.
This is useful for acceleration splits and flying-speed zones because the test can preserve clearly marked locations instead of estimating the boundaries from a general running trace. The internal coordination method is proprietary; the athlete-facing rule is simple: confirm that every phone is connected, armed, stable, and showing the correct line before the rep.
Precision, accuracy, and validity are different
Precision describes how finely a system can place an event in time. Accuracy asks how close that event is to the intended reference. Validity asks whether the event actually represents the performance question being tested.
A sensor can have excellent internal resolution and still record the wrong body part, the wrong start event, or an incorrectly measured course. This is why TrackSpeed emphasizes automatic crossings, reviewable evidence, and a repeatable protocol together.
Device model, frame visibility, lighting, stable placement, thermal conditions, course measurement, and the athlete's path can all affect a training result. Treat any product accuracy figure as a claim tied to a defined test setup—not a guarantee for every recording.
How the main timing categories differ
| Method | Recorded event | Best use | Main caution |
|---|---|---|---|
| Manual stopwatch | A person's button press | Simple group practice | Start and stop reaction become part of the time |
| Photocell gate | An object breaking one or more beams | Dedicated training-gate workflow | Gate height, limb triggers, alignment, and start method matter |
| Camera training timer | A crossing visible at a configured line | Reviewable automatic training times | Framing, visibility, placement, and protocol matter |
| Photo-finish FAT | Official start signal and finish-plane image | Official stadium competition | Specialized certified workflow and event rules |
See the research-backed comparison in our single-beam vs dual-beam timing-gate guide.
Validation boundary
TrackSpeed is a training and testing tool. It is not certified Fully Automatic Timing equipment and does not replace the system required for an official meet result, record, qualifying mark, or ranking.
For training decisions, compare like with like: the same app version, device class where practical, distance, start mode, line positions, placement, surface, and recovery. If the method changes, start a new comparison series instead of mixing the datasets.
TrackSpeed technology FAQ
How does TrackSpeed time a sprint?
You configure a timing line in the phone's camera view. TrackSpeed records an automatic crossing event at that line and uses the start and finish events to calculate elapsed time. With a measured distance, it can also show average speed.
Why is reviewable crossing evidence useful?
It lets an athlete or coach check whether the view was blocked, the line was misplaced, or the detected event did not match the intended test. A visible event is easier to audit than an unexplained number.
Does TrackSpeed work with more than one phone?
Yes. Multiple iPhones can cover start, split, and finish positions in one session. Keep every phone stable, correctly positioned, and on the same documented protocol.
Is TrackSpeed official race timing?
No. TrackSpeed is designed for training, testing, and unofficial timing. Official results must use the timing system required by the relevant governing body and event rules.
See the timing evidence on your own sprint
Download TrackSpeed on iPhone, mark a measured course, keep the protocol fixed, and review every result that looks unusual.
