MatchVision beta: compatibility, setup and limitations

Devices and compatibility

The native project targets iOS 16 and watchOS 9 or later. The camera app targets iPhone; Apple Watch is a phone companion. These software minimums are not a tested-device list. A physically validated model matrix has not yet been published.

Capture uses the rear wide camera configured for 1080p at 60 frames per second. Available formats, lighting, framing and heat must be checked on the actual phone. Do not buy equipment solely on the OS requirement.

The camera version reviewed is native to iPhone. This review found no evidence of an Android or browser camera release, or validated iPad compatibility. The MatchPoint website is a separate web product.

Two cameras means two iPhones, one behind each baseline. It does not mean two lenses on one phone. Synchronized wide and telephoto capture on one phone remains a technical investigation.

Before starting

Confirm beta availability and the installation channel with MatchPoint before subscribing or preparing a court. This review does not confirm a public App Store listing or public TestFlight invitation.

See MatchPoint Plus for current access terms. Each phone in a two-camera setup needs an account with valid access. The server revalidates authorization; do not expect indefinite offline camera access.

Prepare a beta session

1. Install an authorized beta build, sign in and confirm access. Grant camera permission when requested.
2. Secure the iPhone behind the baseline in landscape orientation. Include both baselines and the singles sidelines; avoid backlighting and missing parts of the court.
3. Start capture and check the court overlay. If the build offers manual adjustment, align the four singles corners with the real lines. A visually aligned overlay does not prove call accuracy.
4. Wait for calibration status. Tracking may continue without IN/OUT calls when geometry is untrusted. Silence or a missing call does not mean IN.
5. Try a short rally before playing. Check the image and available calls. Stop and repeat setup if the mount moves, court lines are lost or the camera is interrupted.
6. Stop the session when finished. If recording was selected, wait for finalization and check files before sharing them.

Screens and controls may differ between beta builds. Agree with players how to resolve uncertain shots; the system does not replace official officiating.

Two cameras and Apple Watch

In the implemented flow, place one phone behind each baseline. Open Two cameras: the host creates a session and the second phone joins with its six-digit code. Start from the host and check both connections and calibrations.

The implementation synchronizes observations and shares tentative calls. Generated trajectories and two simulators exercised this flow; they do not establish performance with two physical cameras recording a match.

A paired Watch can show the latest call, start and stop sessions, accept manual scoring and offer court adjustments. Manual scoring does not identify the point winner automatically. Latency, wrist-down operation and editing on a physical Watch still require field tests.

Limitations affecting play

Player occlusion, low light, an unstable mount and incorrectly identified lines can prevent reliable readings. Far-baseline identity and distinguishing ground from racket contact remain validation gaps.

Automatic calibration has not met the full release criterion. The experimental court model remains excluded from Release. No field accuracy percentage, certification or guaranteed line calling is published.

Ball speed and spin have no demonstrated validation in this review. Tennis tests do not establish performance for padel, beach tennis or pickleball.

Troubleshooting

No calls: check access, camera permission, framing and calibration status. Do not force confirmation to obtain calls. If the image freezes or the camera is interrupted, stop and restart with a fresh court check.

Second phone disconnected: check the code and session status on both phones. Wait for connection and synchronization; a connected indicator does not prove accuracy.

Hot phone or interrupted session: end the test and record device model, version, elapsed time and conditions. Thermal protection can reduce or pause analysis. Do not disable it to finish a match.

Recording and data

Video recording is optional and selected per match. The documented flow saves local clips without audio. The two-camera mode exchanges observations and controls rather than raw peer video. This does not mean the entire product works without online services.

Obtain the necessary participant and venue permissions before recording or publishing. Private test footage is not automatically cleared for publicity.

Evaluation and what tests establish

Engineering records dated September 8–11, 2026 describe camera lifecycle, geometry, synchronization and messaging tests, plus iPhone builds. Synthetic tests use known ball positions; recorded-image experiments evaluate court lines. None alone measures call accuracy in a physical match.

The next field protocol should record device and OS models, app build, mount placement, lighting, surface, synchronization and temperature. Compare calls against independently annotated shots, including wrong calls, missing calls and abstentions, especially near lines and at the far baseline.

The protocol includes a 45-minute thermal session with recording on and off in separate runs. This is a proposed test, not guaranteed battery life. Published results need sample size, conditions, method, limitations and footage permissions.

Frequently asked questions

Is it official officiating? No. It is a beta aid without published certification or guaranteed accuracy.

Do I need two cameras? There is a one-phone flow and a two-phone implementation. The second camera does not remove current calibration and validation limits.

What does it cost? Check current MatchPoint Plus terms and confirm availability before subscribing. This guide does not maintain a separate price table.

Where are the official sources? MatchPoint: usematchpoint.app. MatchVision: usematchpoint.app/matchvision. Plans: usematchpoint.app/plus.