Smartphone jump testing versus force plates for a basketball club
A basketball club with 16 players wants to replace its force-plate testing with a smartphone app that estimates countermovement jump height from a phone placed on the floor. In a pilot, 12 players performed three jumps on each system in one session. The app showed an ICC of 0.82 versus force plates, a coefficient of variation of 6.8%, a fixed bias of +1.4 cm, and 95% limits of agreement from −1.9 to +4.7 cm. Testing used one iPhone model and one experienced tester. The sport scientist now wants weekly monitoring and to use the app for return-to-play decisions after ankle sprains. The club has two sites, three assistant coaches who could test, and no budget for new force plates this season. Coaches like the app because it gives immediate feedback and stores data in the cloud. You are asked whether to approve club-wide use, what additional validation is needed, and how to operate if approved.
1. Is the smartphone jump test suitable for weekly monitoring and return-to-play decisions? Justify with the pilot data.
Read the worked answer
Not yet for individual return-to-play. The ICC of 0.82 suggests moderate-to-good group-level agreement, but ICC alone is insufficient. A CV of 6.8% and 95% LoA of −1.9 to +4.7 cm mean an individual’s app score can differ meaningfully from force plate and from day to day. The +1.4 cm fixed bias means the app systematically overestimates, so thresholds cannot be transferred directly. For weekly group trends, the app may be acceptable if the same protocol and device are used and the smallest worthwhile change exceeds the measurement error. For RTP after ankle sprain, decisions are individual and often hinge on small asymmetries; this error is too large to be the sole criterion. Approve only conditional use: not club-wide interchangeability, not RTP clearance, and not comparison across phone models.
2. What validation gaps must be addressed before club-wide use?
Read the worked answer
Validation gaps. The pilot is small (n=12), single-session, one iPhone model, one tester, and likely healthy players; it does not cover the ankle-sprain population or the assistant coaches. Needed: test-retest reliability across days; inter-tester and inter-device agreement; women and men; players with prior injury; fresh and fatigued states; and comparison against force plates at both sites. Use standardized jump instructions, same phone placement, and blinded analysis. Report typical error, MDC, and Bland–Altman rather than only ICC. If the club cannot fund a proper validation, limit claims to internal tracking and keep force plates for high-stakes decisions.
3. Design an operational protocol that uses the app responsibly if force plates are unavailable.
Read the worked answer
Operational protocol if approved. Use one phone model per site, same app version, same floor surface, and a standardized warm-up and jump cue. Record best of three and keep raw data; do not delete poor trials without a rule. Compare each athlete to their own baseline and use a pre-specified MDC, not a coach’s eye. For ankle sprain RTP, combine jump data with pain, swelling, single-leg hop, strength, and sport-specific drills; the app cannot clear an athlete. Audit monthly against force plates on a subsample. Train assistant coaches with a competency check and inter-rater reliability. Communicate that the app is a monitoring tool, not a diagnostic device, and escalate inconsistent results.