Smartphone and Tablet Software Apps to Collect Data in Sport and Exercise Settings: Cross-sectional International Survey
Bibliographic record
Abstract
BACKGROUND: Advances in smartphone technology have facilitated an increase in the number of commercially available smartphone and tablet apps that enable the collection of physiological and biomechanical variables typically monitored in sport and exercise settings. Currently, it is not fully understood whether individuals collect data using mobile devices and tablets, independent of additional hardware, in their practice. OBJECTIVE: This study aims to explore the use of smartphone and tablet software apps to collect data by individuals working in various sport and exercise settings, such as sports coaching, strength and conditioning, and personal training. METHODS: A total of 335 practitioners completed an electronic questionnaire that surveyed their current training practices, with a focus on 2 areas: type of data collection and perceptions of reliability and validity regarding app use. An 18-item questionnaire, using a 5-point Likert scale, evaluated the perception of app use. RESULTS: A total of 204 respondents reported using apps to directly collect data, with most of them (196/335, 58.5%) collecting biomechanical data, and 41.2% (138/335) respondents reported using at least one evidence-based app. A binomial general linear model determined that evidence accessibility (β=.35, 95% CI 0.04-0.67; P=.03) was significantly related to evidence-based app use. Age (β=-.03, 95% CI -0.06 to 0.00; P=.03) had a significant negative effect on evidence-based app use. CONCLUSIONS: This study demonstrates that practitioners show a greater preference for using smartphones and tablet devices to collect biomechanical data such as sprint velocity and jump performance variables. When it is easier to access information on the quality of apps, practitioners are more likely to use evidence-based apps. App developers should seek independent research to validate their apps. In addition, app developers should seek to provide clear signposting to the scientific support of their software in alternative ways.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.007 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".