The Continued Use of Mobile Health Apps: Insights From a Longitudinal Study
Bibliographic record
Abstract
BACKGROUND: Mobile health (mHealth) apps that support individuals pursuing health and wellness goals, such as weight management, stress management, smoking cessation, and self-management of chronic conditions have been on the rise. Despite their potential benefits, the use of these tools has been limited, as most users stop using them just after a few times of use. Under this circumstance, achieving the positive outcomes of mHealth apps is less likely. OBJECTIVE: The objective of this study was to understand continued use of mHealth apps and individuals' decisions related to this behavior. METHODS: We conducted a qualitative longitudinal study on continued use of mHealth apps. We collected data through 34 pre- and postuse interviews and 193 diaries from 17 participants over two weeks. RESULTS: We identified 2 dimensions that help explain continued use decisions of users of mHealth apps: users' assessment of mHealth app and its capabilities (user experience) and their persistence at their health goals (intent). We present the key factors that influence users' assessment of an mHealth app (interface design, navigation, notifications, data collection methods and tools, goal management, depth of knowledge, system rules, actionable recommendations, and user system fit) and relate these factors to previous literature on behavior change technology design. Using these 2 dimensions, we developed a framework that illustrated 4 decisions users might make after initial interaction with mHealth apps (to abandon use, limit use, switch app, and continue use). We put forth propositions to be explored in future research on mHealth app use. CONCLUSIONS: This study provides insight into the factors that shape users' decisions to continue using mHealth apps, as well as other likely decision scenarios after the initial use experience. The findings contribute to extant knowledge of mHealth use and provide important implications for design of mHealth apps to increase long-term engagement of the users.
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.017 | 0.030 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.004 | 0.002 |
| Scholarly communication | 0.003 | 0.003 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.001 | 0.002 |
| 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".