Employing a Phased, Interdisciplinary Approach Across Healthcare and School Settings: mHealth Adaptations for Youth with Autism Spectrum Disorder At-Risk of Experiencing Obesity.

Emerson et al. (2025) interviewed parents, teachers, doctors, and kids with autism. They asked what features an mHealth chatbot needs to help youth who are at risk for obesity.

The team wanted to build WE CHAT, a phone app that gives diet and exercise tips. They talked to people in both clinics and schools to learn what would make the tool useful and easy to use.

Four big ideas came up again and again. First, autism symptoms change from day to day, so the app must bend with the child’s mood and energy. Second, adults disagree on how much they trust health apps; some love quick texts, others want face-to-face care.

Third, families need one place that speaks for the whole team—parent, teacher, doctor. Fourth, an obesity app must cut caregiver workload, not add to it.

TVEmerson et al. (2023) ran an RCT with an autism nutrition app and saw almost no group-wide gains. Caroline’s interviews help explain why: parents who already doubt apps won’t use them. The new study says ‘add branching logic so the chatbot feels personal’—a design fix the earlier trial lacked.

Welsh et al. (2019) showed that weight talk upsets autistic kids. Caroline’s team took that warning and built softer, child-friendly language into WE CHAT. Instead of saying ‘lose weight,’ the bot will use neutral words like ‘strong body.’

Chistol et al. (2024) surveyed adults and found teachers, therapists, and parents each want different tech features. Caroline confirms the split and offers a fix: one dashboard with role-based views so everyone sees what they need without extra clicks.

If you coach autistic youth who are overweight, ask the family how they feel about apps before you assign one. Use Caroline’s four themes as a quick checklist: daily flexibility, trust level, team hub, and caregiver burden. When you demo an mHealth tool, point out features that adjust to symptom swings and share data with the whole team—those touches boost buy-in and daily use.