ThoughtBeam brings scattered thoughts into daily ThoughtBundles. That everyday record could help researchers understand experience between visits, explore reflection activities and evaluate programmes in real-world settings.
Beam Boy, with his research hat on. The same curiosity. A new set of questions.
These are potential research applications, not completed validation studies. Study-specific collection, researcher access and evaluation would need to be designed and implemented with research partners.
Keep the context. Ask better questions.
A score tells part of a story. A participant’s own words can help explain what happened around it: a demanding morning, a conversation, a quiet pause.
Capturing experience close to the moment is a principle of ecological momentary assessment (EMA), which aims to reduce reliance on retrospective recall. ThoughtBeam’s voluntary journaling offers a starting point; a formal EMA study would still need a defined sampling schedule and suitable measures. [1]
More ways to participate
ThoughtBubbles, text, voice and photos offer different ways to describe an experience. Research teams could test which formats participants find useful and manageable.
A day, with its context
ThoughtBundles bring original entries together by day. This could support participant-led review and qualitative discussion alongside formal study measures.
Reflection to investigate
Reframing, grounding and breathing activities offer specific experiences to evaluate for acceptability, engagement and possible benefit.
A useful starting point. Several paths to evidence.
Begin with a defined question and a feasible pilot. Build toward evaluation with participants, appropriate methods and a clear account of the setting. [2]
Feasibility & acceptability
Can people fit a brief reflection into everyday life?
Start with a small pilot. Examine recruitment, retention, completion, time burden and reasons for stopping. Interviews can reveal friction that usage counts miss.
Useful output: a practical collection schedule and an informed decision about a larger study.
Clinical measurement validation
What does a check-in actually measure?
Compare a defined candidate measure with an appropriate validated instrument. Examine reliability, validity and sensitivity to change in the intended population and language.
Useful output: evidence about that specific measure. Free-text entries and AI summaries are not validated clinical scores.
Longitudinal experience studies
How do experiences vary within a person over time?
Explore the timing and context of participant-reported experiences across days or weeks. Combine consented entries with planned assessments; account for missing entries and unequal participation.
Useful output: contextual themes and testable hypotheses. An association does not establish causation.
Intervention studies
Does a reflection activity make a meaningful difference?
Evaluate a defined grounding, breathing or reframing programme using an appropriate comparison group and prespecified outcomes. Assess baseline and follow-up, experience of use and possible unwanted effects.
Useful output: an estimate of benefit, uncertainty and acceptability. Completing an activity is not itself evidence of a health benefit.
From individual moments to public-health questions.
For a community programme, ask who takes part, what changes and whether delivery lasts. The RE-AIM framework provides five useful assessment dimensions. The measures below are planning examples, not ThoughtBeam results. [3]
Planning a public-health effectiveness assessment
Dimension
Question
What a study could assess
Reach
Who participates—and who is missing?
Participation relative to the eligible population; differences by language, device access and digital confidence.
Effectiveness
Do outcomes improve?
Validated outcomes, comparison-group differences, unwanted effects and variation across participant groups.
Adoption
Which settings take it up?
The proportion and range of eligible organisations and staff that begin delivery.
Implementation
How is it delivered in practice?
Delivery consistency, adaptations, staff time, participant burden and programme costs.
Maintenance
Does the benefit or programme last?
Longer-term outcomes and whether participating organisations sustain delivery.
Journal data could add context to an evaluation. A self-selected group of app users cannot establish population prevalence. Plan for attrition, missing data and digital exclusion; consider interviews and other collection routes alongside the app.
An everyday app. A study built with purpose.
The app supplies reflection experiences. A research protocol determines what is collected, why it is needed and how it can be interpreted.
In the current app
ThoughtBubbles, mood check-ins, text, voice and photo capture.
Daily ThoughtBundles that retain original entries.
Structured reframing, grounding and breathing activities.
Device-based journaling and optional encrypted personal-cloud backups.
Study consent, participant identifiers and a withdrawal process.
Validated measures, assessment timing and any study reminders.
Approved data transfer, researcher permissions and audit records.
Study exports or dashboards, analysis rules and retention controls.
These research services are not presented as existing consumer-app features.
Participant control. From the beginning.
The consumer app does not automatically share journals with researchers. Journals are stored on the device; optional personal-cloud backups are encrypted before upload to the user’s own iCloud or Google Drive account, depending on platform.
AI features and voice transcription send relevant content to processing services. Account and usage information is also processed. A study must map these flows and decide which features are appropriate before recruitment.
A research deployment would require ethics review and explicit consent, minimum necessary collection, approved transfers, restricted access and a clear retention and withdrawal plan. Participant choice should cover which entries and media enter the study.
Original entries should remain distinguishable from edited transcripts and generated summaries. AI summaries and cover art should not be treated as validated endpoints.
Start with the question. Design the study around it.
A useful first discussion brings researchers, delivery partners and participant representatives together.
Define the question and population.Choose the setting, intended benefit and primary outcome. Establish whether the immediate goal is feasibility, measurement or effectiveness.
Co-design participation.Agree the capture burden, language needs, accessibility, consent and which information is actually necessary.
Pilot the complete process.Test collection, approved transfer, data quality and participant support before a larger evaluation.
Evaluate and report.Prespecify analysis, account for missing data and uncertainty, and report what worked, for whom and under which conditions.
A conversation worth bringing to your team.
Share this research overview with a collaborator, study group or public-health partner.
ThoughtBeam is a reflection app. Clinical effectiveness, research compliance and a ready-to-use research data platform are not established by this page.
Methods behind the questions.
These references inform the proposed study approach. They do not evaluate or endorse ThoughtBeam.