Assessment of Mobile Health Apps Using Built-In Smartphone Sensors for Diagnosis and Treatment: Systematic Survey of Apps Listed in International Curated Health App Libraries
Bibliographic record
Abstract
BACKGROUND: More than a million health and well-being apps are available from the Apple and Google app stores. Some apps use built-in mobile phone sensors to generate health data. Clinicians and patients can find information regarding safe and effective mobile health (mHealth) apps in third party-curated mHealth app libraries. OBJECTIVE: These independent Web-based repositories guide app selection from trusted lists, but do they offer apps using ubiquitous, low-cost smartphone sensors to improve health? This study aimed to identify the types of built-in mobile phone sensors used in apps listed on curated health app libraries, the range of health conditions these apps address, and the cross-platform availability of the apps. METHODS: This systematic survey reviewed three such repositories (National Health Service Apps Library, AppScript, and MyHealthApps), assessing the availability of apps using built-in mobile phone sensors for the diagnosis or treatment of health conditions. RESULTS: A total of 18 such apps were identified and included in this survey, representing 1.1% (8/699) to 3% (2/76) of all apps offered by the respective libraries examined. About one-third (7/18, 39%) of the identified apps offered cross-platform Apple and Android versions, with a further 50% (9/18) only dedicated to Apple and 11% (2/18) to Android. About one-fourth (4/18, 22%) of the identified apps offered dedicated diagnostic functions, with a majority featuring therapeutic (9/18, 50%) or combined functionality (5/18, 28%). Cameras, touch screens, and microphones were the most frequently used built-in sensors. Health concerns addressed by these apps included respiratory, dermatological, neurological, and anxiety conditions. CONCLUSIONS: Diligent mHealth app library curation, medical device regulation constraints, and cross-platform differences in mobile phone sensor architectures may all contribute to the observed limited availability of mHealth apps using built-in phone sensors in curated mHealth app libraries. However, more efforts are needed to increase the number of such apps on curated lists, as they offer easily accessible low-cost options to assist people in managing clinical conditions.
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.013 | 0.056 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.003 |
| Bibliometrics | 0.014 | 0.012 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.004 |
| Open science | 0.001 | 0.004 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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".