aceModerate evidence
Published recordLifestyleProblem Space
More
Problematic smartphone use and AI chatbot dependence: A cross-sectional study using latent profile and dimensional analyses
- Truvace record
- TRV-2026-2531raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- b92e4f027cd8…check it
ABSTRACT As generative artificial intelligence becomes increasingly embedded in everyday, educational, and work-related contexts, increasing attention has been directed to dependency-related forms of AI chatbot use. Problematic smartphone use (PSU) may reflect broader dysregulated digital engagement and may therefore be relevant to understanding dependency-related AI chatbot use. However, little is known about whether PSU is associated with AI chatbot dependency or whether AI-related evaluative factors show diff…
The problem
In a cross-sectional study of 538 AI chatbot users, higher problematic smartphone use was positively associated with AI chatbot dependency, and 38% of users fell in the high-symptom group.
What this doesn’t fix
The study used a cross-sectional, self-report design, and the profile-specific performance expectancy finding was not reproduced in the continuous model, so it is exploratory.
Sources
1 on file- Computers in Human Behavior Reportsdoi:10.1016/j.chbr.2026.101337
Cite this record
v1Truvace Impact Record TRV-2026-2531, v1: “Problematic smartphone use and AI chatbot dependence: A cross-sectional study using latent profile and dimensional analyses.” Truvace, 2026-11-12. /record/TRV-2026-2531 (accessed on the day you copy it). sha256 b92e4f027cd8704d…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2531 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.