Predictors of the Number of Installs in Psychiatry Smartphone Apps: Systematic Search on App Stores and Content Analysis
Bibliographic record
Abstract
BACKGROUND: Mental health is integral to our salubrity, but mental disorders are very debilitating and common. Therefore, it is critical to provide accessible, timely, and inexpensive mental care. This can be done through mobile health (mHealth), namely, mobile medical apps, which are gaining popularity among clinicians and patients. mHealth is a fast-paced field, and there is significant variation in the number of installs among psychiatry apps. However, the factors that influence psychiatry app installs have yet to be studied. OBJECTIVE: This study aimed to identify predictors of the number of app installs in psychiatry. METHODS: A literature review identified which factors influence app installs. Psychiatry apps available in the Google Play Store were reviewed, and publicly available data were collected. A multivariate ordinal logistic regression analysis was performed to evaluate the effect of said factors on the number of installs. RESULTS: Our search identified 128 psychiatry apps: 2.3% (3/128) had never been installed, approximately half (53.1%, 68/128) had less than 500 installs, and only 0.8% (1/128) had over 10,000,000 installs. A multivariate logistic regression analysis identified that apps with a lower price (P<.001), a higher rating (P<.001), optional in-app purchases (P<.001), and age restriction (P=.04) had a higher number of installs. The involvement of a psychiatrist or other health care professional (HCP) had no statistically significant influence on the number of installs. Only data from the Google Play Store and the developers' websites were available for analysis, and the depth of involvement of HCPs was impossible to document. CONCLUSIONS: Psychiatry apps with a lower price, optional in-app purchases, age restriction, and a higher rating are expected to have a higher number of installs. Unlike other medical fields, in this study, the explicit participation of psychiatrists in app development was not a significant predictor of the number of installs. Research is needed to identify other factors that may influence the number of installs, as that can help mHealth app development.
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.023 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.003 | 0.003 |
| Bibliometrics | 0.020 | 0.022 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.003 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 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".