Development of an mHealth App–Based Intervention for Depressive Rumination (RuminAid): Mixed Methods Focus Group Evaluation
Bibliographic record
Abstract
BACKGROUND: Depression is a common mental health condition that poses a significant public health burden. Effective treatments for depression exist; however, access to evidence-based care remains limited. Mobile health (mHealth) apps offer an avenue for improving access. However, few mHealth apps are informed by evidence-based treatments and even fewer are empirically evaluated before dissemination. To address this gap, we developed RuminAid, an mHealth app that uses evidence-based treatment components to reduce depression by targeting a single key depressogenic process-rumination. OBJECTIVE: The primary objective of this study was to collect qualitative and quantitative feedback that could be used to improve the design of RuminAid before the software development phase. METHODS: We reviewed empirically supported interventions for depression and rumination and used the key aspects of each to create a storyboard version of RuminAid. We distributed an audio-guided presentation of the RuminAid storyboard to 22 individuals for viewing and solicited user feedback on app content, design, and perceived functionality across 7 focus group sessions. RESULTS: The consumer-rated quality of the storyboard version of RuminAid was in the acceptable to good range. Indeed, most participants reported that they thought RuminAid would be an engaging, functional, and informational app. Likewise, they endorsed overwhelming positive beliefs about the perceived impact of RuminAid; specifically, 96% (21/22) believed that RuminAid will help depressed ruminators with depression and rumination. Nevertheless, the results highlighted the need for improved app aesthetics (eg, a more appealing color scheme and modern design). CONCLUSIONS: Focus group members reported that the quality of information was quite good and had the potential to help adults who struggle with depression and rumination but expressed concern that poor aesthetics would interfere with users' desire to continue using the app. To address these comments, we hired a graphic designer and redesigned each screen to improve visual appeal. We also removed time gating from the app based on participant feedback and findings from related research. These changes helped elevate RuminAid and informed its initial software build for a pilot trial that focused on evaluating its feasibility and acceptability.
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.030 | 0.028 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.003 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.003 | 0.002 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.006 | 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".