<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Diabetes</journal-id><journal-id journal-id-type="publisher-id">diabetes</journal-id><journal-id journal-id-type="index">23</journal-id><journal-title>JMIR Diabetes</journal-title><abbrev-journal-title>JMIR Diabetes</abbrev-journal-title><issn pub-type="epub">2371-4379</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v11i1e71733</article-id><article-id pub-id-type="doi">10.2196/71733</article-id><article-categories><subj-group subj-group-type="heading"><subject>Viewpoint</subject></subj-group></article-categories><title-group><article-title>T1D REACHOUT&#x2013;A Mobile App to Deliver Peer-Led Mental Health Support to Adults Living With Type 1 Diabetes: Co-Design and Development Process</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Lee</surname><given-names>Sadie</given-names></name><degrees>BA</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Sidhu</surname><given-names>Baray</given-names></name><degrees>BSc</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Johal</surname><given-names>Parteek</given-names></name><degrees>BSc</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Azhar</surname><given-names>Ayman</given-names></name><degrees>BSc, BCS</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Sujan</surname><given-names>Jonath</given-names></name><degrees>MEng</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author" corresp="yes" equal-contrib="yes"><name name-style="western"><surname>G&#x00F6;rges</surname><given-names>Matthias</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff5">5</xref><xref ref-type="aff" rid="aff6">6</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Tang</surname><given-names>Tricia S</given-names></name><degrees>PhD, RPsych</degrees><xref ref-type="aff" rid="aff7">7</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib></contrib-group><aff id="aff1"><institution>Faculty of Arts, University of British Columbia</institution><addr-line>Vancouver</addr-line><addr-line>BC</addr-line><country>Canada</country></aff><aff id="aff2"><institution>Faculty of Science, University of British Columbia</institution><addr-line>Vancouver</addr-line><addr-line>BC</addr-line><country>Canada</country></aff><aff id="aff3"><institution>Division of Respiratory Medicine, Department of Medicine, University of British Columbia</institution><addr-line>Vancouver</addr-line><addr-line>BC</addr-line><country>Canada</country></aff><aff id="aff4"><institution>Department of Computer Science, University of British Columbia</institution><addr-line>Vancouver</addr-line><addr-line>BC</addr-line><country>Canada</country></aff><aff id="aff5"><institution>AI and Data Science Unit, Research Institute, BC Children's Hospital</institution><addr-line>Rm V3-324, 950 West 28th Avenue</addr-line><addr-line>Vancouver</addr-line><addr-line>BC</addr-line><country>Canada</country></aff><aff id="aff6"><institution>Department of Anesthesiology, Pharmacology and Therapeutics, University of British Columbia</institution><addr-line>Vancouver</addr-line><addr-line>BC</addr-line><country>Canada</country></aff><aff id="aff7"><institution>Division of Endocrinology, Department of Medicine, University of British Columbia</institution><addr-line>Vancouver</addr-line><addr-line>BC</addr-line><country>Canada</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Correa</surname><given-names>Ricardo</given-names></name></contrib><contrib contrib-type="editor"><name name-style="western"><surname>Cahill</surname><given-names>Naomi</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>br</surname><given-names>chandrashekar</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Pankhurst</surname><given-names>Christian</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>David</surname><given-names>Temitope</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Hemetek</surname><given-names>Ursula</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Matthias G&#x00F6;rges, PhD, AI and Data Science Unit, Research Institute, BC Children's Hospital, Rm V3-324, 950 West 28th Avenue, Vancouver, BC, V5Z 4H4, Canada, 1 604-875-2000 ext 5616; <email>mgoerges@bcchr.ca</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>these authors contributed equally</p></fn></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>20</day><month>3</month><year>2026</year></pub-date><volume>11</volume><elocation-id>e71733</elocation-id><history><date date-type="received"><day>24</day><month>01</month><year>2025</year></date><date date-type="accepted"><day>06</day><month>02</month><year>2026</year></date></history><copyright-statement>&#x00A9; Sadie Lee, Baray Sidhu, Parteek Johal, Ayman Azhar, Jonath Sujan, Matthias G&#x00F6;rges, Tricia S Tang. Originally published in JMIR Diabetes (<ext-link ext-link-type="uri" xlink:href="https://diabetes.jmir.org">https://diabetes.jmir.org</ext-link>), 20.3.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Diabetes, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://diabetes.jmir.org/">https://diabetes.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://diabetes.jmir.org/2026/1/e71733"/><abstract><p>For adults living with type 1 diabetes (T1D), diabetes-specific mental health support is limited. Peer support and digital health platforms are promising strategies for delivering this support to this population, particularly those from geographically marginalized communities. Mobile apps, in particular, can enhance self-management and deliver support. This paper describes the iterative co-design and development process of a novel mobile app for use in a pilot trial, T1D REACHOUT (REACHOUT), that aims to reduce the diabetes distress, a core facet of diabetes-specific mental health, of adults with T1D. An initial think tank and 6 focus groups were conducted with adults with T1D to better understand their support needs and identify platform requirements. Following this, we partnered with adults living with T1D, the &#x201C;end users,&#x201D; to iteratively co-design the REACHOUT app, enhancing usability and ensuring relevance. Adapting the open-source Rocket.Chat platform to user-defined requirements, we deployed the app in a single cohort pilot study. A network analysis of messages exchanged during the pilot study was performed to explore trends and patterns and demonstrate implementation feasibility. Pilot study outcomes informed further refinement before implementation in a randomized controlled trial. The implementation of the REACHOUT app features 6 key components identified in 6 initial focus groups: a 24/7 chatroom (a customized group messaging function with threads), topic-specific discussion boards, a peer supporter library, peer supporter profiles for a user-driven matching process, small group virtual sessions, and direct (one-to-one) messaging. Forty-six participants were encouraged to use any or all of the features as frequently as desired over a 6-month period during the pilot study. During this time, 179 private small groups were created, and 10,410 messages were sent, including 1389 chat room messages and 7116 direct messages; among these were 3446 messages exchanged between participants and their self-selected peer supporters. Key factors for successful implementation included (1) the co-design process involving comprehensive user engagement and (2) the opportunities realized through hybrid development. These findings offer generalizable lessons for mobile health research teams developing similar app-based interventions.</p></abstract><kwd-group><kwd>peer support</kwd><kwd>type 1 diabetes</kwd><kwd>digital interventions</kwd><kwd>user-centered design</kwd><kwd>mobile phone</kwd><kwd>mobile health</kwd><kwd>mHealth</kwd><kwd>app development</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><sec id="s1-1"><title>Mobile Apps for Type 1 Diabetes Management</title><p>In the era of digital health, mobile apps have increasingly been used to improve diabetes care. These platforms are vital for individuals living in geographically marginalized settings with limited access to conventional, in-person diabetes support [<xref ref-type="bibr" rid="ref1">1</xref>]. Particularly, adults with type 1 diabetes (T1D) living in rural and remote communities in British Columbia have reported that peers with T1D share first-hand lived experience [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>], from which they may benefit. As such, digitally delivered mental health support may be a promising solution for underserved populations.</p><p>Several systematic reviews and meta-analyses involving children or adults with T1D have examined mobile apps [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref7">7</xref>] designed to improve self-management [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref10">10</xref>], monitor treatment through data visualization [<xref ref-type="bibr" rid="ref11">11</xref>], and deliver psychosocial interventions [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. Notably, research in this area has mainly focused on mobile app evaluation, while descriptions of app development lag behind.</p></sec><sec id="s1-2"><title>Benefits of Involving End Users in App Development</title><p>Digital platforms that engage end users early in the development process are more likely to produce favorable results [<xref ref-type="bibr" rid="ref16">16</xref>]. Specifically, co-design is a research methodology that, in principle, involves shared decision-making through the collaborative engagement of end users, researchers, and health care professionals to create and develop the technology to be used [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. Thus, research exploring the mobile app preferences and perspectives of individuals with T1D has grown steadily [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. Not surprisingly, 2 of the 4 best practices in app development involve &#x201C;prioritizing user preferences&#x201D; and &#x201C;engaging stakeholders&#x201D; [<xref ref-type="bibr" rid="ref21">21</xref>].</p><p>While there is increased interest in collecting user feedback, how these data are integrated during the app development process has not been clearly described. Although several other T1D-specific apps provide detailed descriptions of their development, their goals are to improve glycated hemoglobin and blood glucose management by promoting self-care practices (carbohydrate counting, injection site rotation, insulin dosing, physical activity, etc) [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref25">25</xref>]. To our knowledge, no studies describe the comprehensive development process for a mobile app focused on reducing diabetes distress by offering peer-led mental health support to adults with T1D.</p></sec><sec id="s1-3"><title>The T1D REACHOUT Intervention</title><p>T1D REACHOUT (REACHOUT) is a mobile app designed to reduce diabetes distress by offering peer-led mental health support to adults with T1D living in rural and remote areas of Interior British Columbia [<xref ref-type="bibr" rid="ref2">2</xref>]. Based on self-determination theory, which highlights what motivates patients to make support-related decisions [<xref ref-type="bibr" rid="ref26">26</xref>], REACHOUT is a 6-month intervention that offers a range of support delivery modalities to meet users&#x2019; individual needs.</p><p>The use of the app is not intended to replace standard health care provision but rather to enable increased access to peer-led support and fill a gap in the health care system. While interdisciplinary diabetes care typically involves a team of endocrinologists, diabetes nurses, and dietitians, what is often overlooked and undervalued are the peers who understand first-hand the day-to-day experience of living with T1D.</p></sec><sec id="s1-4"><title>Aims</title><p>This paper describes the iterative co-design and development process of the REACHOUT mobile app, including its use in a pilot trial and subsequent revisions made prior to its implementation in a randomized controlled trial (RCT). While empirical outcomes from the REACHOUT pilot intervention have been reported elsewhere [<xref ref-type="bibr" rid="ref2">2</xref>], we focus specifically on the technical development and implementation of the app used in the intervention and aim to share generalizable lessons with other mobile health (mHealth) research teams.</p><p>Specifically, this paper reflects on the (1) collaboration process between researchers and end users (ie, adults with T1D) to identify information needs and support requirements that informed app functionality, (2) iterative design of the app with end users to enhance usability and meet key user needs, (3) deployment of the app in a pilot study to understand feasibility, and (4) incorporation of feedback from the pilot study to further refine the app before launching the RCT.</p><p>This paper is organized in the following sections: Ethical Considerations; Recruitment; Platform Design and Implementation, which includes all stages of the co-design process; Platform Features, which outlines the functionality of the designed app; Initial Platform Utilization Patterns, which includes a network analysis of app usage during the pilot study; Insights and Observations, which specifically addresses challenges to co-design in mHealth; and Discussion, which includes an overview of our findings, limitations, and future work.</p></sec></sec><sec id="s2"><title>Ethical Considerations</title><p>The University of British Columbia Behavioural Research Ethics Board approved this project (H20-00276, PI Tang, date of first approval 2020-03-31), with additional harmonized review by the Interior Health Research Ethics Board (same approval number). Participants were given study information, allowed to ask questions, and provided electronic consent. Focus group participants received a US $50 gift card upon completion. Pilot study participants received a US $25 and a US $50 Amazon gift card at baseline and at 6&#x2009;months, respectively. Focus group discussions throughout the co-design process were recorded, transcribed verbatim, and then de-identified. Study data were stored securely with access limited to study team members.</p></sec><sec id="s3"><title>Recruitment</title><p>For our preliminary think tank session, we recruited participants (n=17) from a list of adults with T1D who expressed interest in T1D-specific mental health support at a Diabetes Canada-sponsored T1D patient advocacy event.</p><p>Focus group participants (n=38) were recruited using several modalities: (1) inviting participants from previous T1D diabetes studies, (2) obtaining referrals from health care providers, (3) sending emails to members of Breakthrough T1D living in the Interior British Columbia regions, (4) posting messages on T1D-specific social media sites, and (5) word of mouth [<xref ref-type="bibr" rid="ref1">1</xref>]. Eligibility criteria included being diagnosed with T1D, &#x2265;19 years, living in the Interior Health Authority region, and able to speak English [<xref ref-type="bibr" rid="ref1">1</xref>].</p><p>Pilot study participants (n=46) were also identified and recruited via (1) diabetes education centers in the Interior Health Authority region, (2) T1D advocacy organizations, (3) T1D-specific Facebook support groups and social media outlets, (4) referrals from health care providers, and (5) word of mouth [<xref ref-type="bibr" rid="ref2">2</xref>]. Eligibility criteria were similar to those of the focus group study, except that participants also needed to have access to the internet and/or a smartphone [<xref ref-type="bibr" rid="ref2">2</xref>].</p><p>End user partners (n=11) were adults living with T1D who contributed to the iterative development process and were recruited from participants in the previous focus groups.</p></sec><sec id="s4"><title>Platform Design and Implementation</title><sec id="s4-1"><title>Overview</title><p>Our development process occurred in 3 stages: predevelopment, co-design and development, and revision (<xref ref-type="fig" rid="figure1">Figure 1</xref>). As people with T1D are the end users of the REACHOUT app, their involvement was imperative; hence, their feedback and guidance were sought throughout the app&#x2019;s development process to ensure it met end user needs. Through focus groups, informal think tanks, and feedback sessions, the co-design approach defined requirements and critical features for the peer support&#x2013;based mobile app (<xref ref-type="fig" rid="figure2">Figure 2</xref>).</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Timeline of the REACHOUT mobile app development process. Stage 1: predevelopment is indicated by blue arrows; stage 2: co-design and development are indicated by red arrows; and stage 3: deployment and revision are indicated by yellow arrows. Study milestones, including the pilot trial and the randomized controlled trial (RCT), are indicated by green circles. SaaS: software as a service.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig01.png"/></fig><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Co-design and development process, with each of the user groups engaged and the actions performed as a result of the activity.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig02.png"/></fig></sec><sec id="s4-2"><title>Stage 1: Predevelopment</title><sec id="s4-2-1"><title>Think Tank</title><p>A preliminary think tank of adults with T1D was used as a scoping activity to elicit the support needs of this group and explore the possibility of a digital platform as the modality for emotional support. The session lasted approximately 60 minutes and was audio-recorded, with only an audio transcript available. Insights from this discussion informed the subsequent pursuit of a mobile app&#x2013;based intervention and the continued use of a co-design approach.</p><p>Participants identified potential support delivery features that would be beneficial, including individual peer-to-peer support, group-based messaging, professional moderators, and discussion boards. Additionally, participants discussed considerations when choosing peer supporters, such as using the same technologies (eg, the same continuous glucose monitor).</p></sec><sec id="s4-2-2"><title>Platform and Software Selection</title><p>Given the anticipated benefits of a flexible setup and the ability to customize the app, digital health software companies were first reviewed. These included Weltel, Latero Labs, Freshworks, Tactica Interactive, and Tech Samurais (currently Four Nine Digital). However, due to financial constraints prohibiting the development of a de novo app, we decided to develop the app by adapting and expanding existing communication&#x2013;based software. Alternative solutions were researched to identify which would best fit the identified requirements while making only limited changes to the app.</p><p>Slack, Mattermost, and Rocket.Chat were identified as potential platforms (<xref ref-type="table" rid="table1">Table 1</xref>). Slack was disqualified due to a lack of options for modification given its closed-source software, leaving Mattermost and Rocket.Chat as the final candidates for consideration. Rocket.Chat was selected for its customization, comprehensive documentation, and polished user interface and user experience design. Subsequently, Rocket.Chat was tested with end user partners (n=11) to evaluate user experience before being modified to create the REACHOUT app.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Alternative software options and criteria researched<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup>.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Property</td><td align="left" valign="bottom">Slack [<xref ref-type="bibr" rid="ref27">27</xref>]</td><td align="left" valign="bottom">Rocket.Chat [<xref ref-type="bibr" rid="ref28">28</xref>]</td><td align="left" valign="bottom">Mattermost [<xref ref-type="bibr" rid="ref29">29</xref>]</td></tr></thead><tbody><tr><td align="left" valign="top">Customizability</td><td align="left" valign="top">Slightly customizable</td><td align="left" valign="top">Very customizable</td><td align="left" valign="top">Very customizable</td></tr><tr><td align="left" valign="top">Pricing (per user)</td><td align="left" valign="top">CAD $207/year; US $ ~145/year</td><td align="left" valign="top">Free if self-hosted or CAD $55/year; US $ ~38/year</td><td align="left" valign="top">Free if self-hosted or CAD $141/year; US $ ~99/year</td></tr><tr><td align="left" valign="top">Hosting costs</td><td align="left" valign="top">Included</td><td align="left" valign="top">CAD $2045/year; US $ ~1430/year</td><td align="left" valign="top">&#x2264;CAD $2100/year; US $ ~1469/year</td></tr><tr><td align="left" valign="top">Setup and maintenance</td><td align="left" valign="top">Easy and nontechnical</td><td align="left" valign="top">Complex</td><td align="left" valign="top">Complex</td></tr><tr><td align="left" valign="top">Hosting location</td><td align="left" valign="top">United States</td><td align="left" valign="top">Canada</td><td align="left" valign="top">Canada</td></tr><tr><td align="left" valign="top">Source</td><td align="left" valign="top">Closed-source</td><td align="left" valign="top">Open-source</td><td align="left" valign="top">Open-source</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Pricing in Canadian dollars reflects amounts at the time of inquiry. Conversion to US dollars was done on January 20, 2025.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s4-2-3"><title>Technology Stack and Platform Architecture</title><p>REACHOUT is built on the Rocket.Chat cross-platform messaging platform, powered by React Native. When new updates are made to the app, we build iOS and Android app files from the latest code changes using Xcode and Android Studio. The client-facing component includes an app for Android and iOS devices that interacts with our Amazon Web Services (AWS) backend via a firewall. An Amazon Elastic Cloud Compute instance provides compute capacity with Amazon Elastic Block Storage for long-term data storage. Initially hosted on DigitalOcean&#x2019;s cloud, it was later migrated to a Canadian AWS instance at the recommendation of initial contractors and supported by more robust documentation from Rocket.Chat for AWS deployment. Push notifications use Apple Push Notification Service for iOS devices and Firebase Cloud Messaging for Android devices (<xref ref-type="fig" rid="figure3">Figure 3</xref>).</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Overview of the current app architecture with interactions between client components, server and storage components, and third-party notification services. T1D: type 1 diabetes.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig03.png"/></fig></sec><sec id="s4-2-4"><title>Focus Groups</title><p>Six focus groups with 38 participants (5&#x2010;7 participants per focus group) were held to identify users&#x2019; current and past T1D-related mental health needs, explore desired features for the app, elicit peer supporter communication mode preferences, and understand patterns of social media use for diabetes-specific support [<xref ref-type="bibr" rid="ref1">1</xref>]. Detailed results have been reported previously [<xref ref-type="bibr" rid="ref1">1</xref>].</p><p>Through these focus groups, participants established the following key requirements:</p><list list-type="order"><list-item><p>One-to-one support from a peer supporter (an individual with similar firsthand experience) could help users navigate the &#x201C;ups and downs&#x201D; of living with T1D.</p></list-item><list-item><p>24/7 group support allows participants to receive support at any time of day, including evenings and weekends. It is difficult to predict when users need immediate emotional validation, normalization, advice, and acceptance. For example, participants cited hypoglycemia, which can occur in the middle of the night, as a situation in which immediate emotional support can provide reassurance and comfort.</p></list-item><list-item><p>Synchronous and asynchronous support options are available for meeting virtually with others or asking or responding to questions in participants&#x2019; own time.</p></list-item></list><p>Focus group participants also provided feedback on specific app features that would be beneficial, further informing development [<xref ref-type="bibr" rid="ref1">1</xref>]. These recommendations included (1) which data to incorporate in peer supporter profiles, such as age of diagnosis, hobbies, stage of life, and T1D monitoring and treatment technologies used (eg, brand of continuous glucose monitor) so that participants can determine a suitable match; (2) having trained health professionals on the platform to prevent the exchange of medical information; (3) including resources and links to keep up with best practices; and (4) hosting topic-specific group discussions on subjects specific to living with T1D.</p><p>From focus group discussions, we identified 6 key features based on recurring needs and priorities articulated by participants and prioritized in development based on feasibility [<xref ref-type="bibr" rid="ref1">1</xref>]: peer supporter profiles, a peer supporter library, one-to-one messaging, group messaging, topic-specific discussion boards, and virtual huddles.</p></sec></sec><sec id="s4-3"><title>Stage 2: Co-Design and Development</title><sec id="s4-3-1"><title>Release and Feedback Cycle</title><p>An external developer was contracted to translate the user-identified key features into an initial prototype. Three iterations of the prototype were developed and released to subsequent groups of test users. Over the course of each iteration, users were asked to provide feedback to the research team via Zoom meetings regarding feature design preferences, functionality, and pain points (eg, a lack of intuitiveness in performing an action).</p><p>The first iteration (released to 23 users: 17 iOS users and 5 Android users) included peer supporter profiles, one-to-one messaging, and group messaging, which were more feasible to implement given Rocket.Chat&#x2019;s existing functionality. Feedback was received and implemented in the following iteration. The second iteration (released to 43 users: 31 iOS users and 12 Android users) included the existing features and added video huddles. The third iteration retained the features we had already updated (peer supporter profiles, one-to-one messaging, and group messaging), updated the video huddles feature, and added a peer supporter library.</p><p>There was approximately 25% overlap in users across iterations, as users participated in consecutive app iterations. We sought to recruit 50 participants and recruited 46. Given that this was a feasibility study, no power calculation was required. To determine a reasonable sample size, we conducted a literature review and identified other pilot studies similar in topic. According to a systematic review of mHealth apps for chronic illness and/or social support, 12 of the 13 studies reported samples of fewer than 50 participants, with an age range of 12 to 49 years [<xref ref-type="bibr" rid="ref30">30</xref>]. Considering these studies, we elected to recruit a sample size of 50 participants.</p></sec><sec id="s4-3-2"><title>End User Partners</title><p>A small group of end user partners (n=11) was engaged to support iterative collaboration throughout development. End user partners contributed to wireframe development, design recommendations, and postimplementation feedback, such as ranking the importance of content on peer supporter profiles and rating the usefulness of proposed features. Feedback was elicited through 3 group meetings, a one-on-one phone call, and an email discussion. This enabled end users to influence design decisions and support iterative development grounded in lived experience.</p><p>The mean age of end user partners was 39 (SD 11) years; 55% (n=6) identified as female. The small number of end user partners was not intended to be representative of the T1D population as a whole but rather to support meaningful co-design through in-depth engagement.</p></sec></sec><sec id="s4-4"><title>Stage 3: Deployment and Revision</title><sec id="s4-4-1"><title>Deployment</title><p>Following these 3 development iterations, the app was tested in a pilot study published elsewhere [<xref ref-type="bibr" rid="ref2">2</xref>] and involved 46 users receiving support and 36 peer supporters delivering support. The mean age of users receiving support was 44 (SD 15) years, with the majority (n=29, 76%) identifying as women. The mean age of peer supporters was 41 (SD 16) years, with 37 (73%) identifying as women [<xref ref-type="bibr" rid="ref12">12</xref>]. Of the 46 participants onboarded during app deployment, 8 withdrew for personal reasons. Of the 37 peer supporters onboarded, 2 withdrew, also for personal reasons.</p><p>We determined which participants were iOS or Android users and collected their respective App Store and Google Play Store email addresses. For iOS users, we used TestFlight to distribute the app builds. Users were provided access to a test version of the app. When new versions of the app were released, they were either automatically updated on the users&#x2019; mobile phones or could be downloaded manually via the TestFlight app. For Android users, we initially distributed an Android Package Kit file that users downloaded, but later pivoted to releases on the Google Play Store for ease of use. Users were sent a link to download the app, and any updates were automatically downloaded to their mobile phones. Only invited users could download the app for either Android or iOS.</p></sec><sec id="s4-4-2"><title>Platform Modification Focus Groups</title><p>A further set of postpilot focus groups was held to receive feedback on user priorities for the app and potential modifications. Features that needed to be fixed and features to add based on user feedback were presented [<xref ref-type="bibr" rid="ref31">31</xref>], and users (n=8) completed a prioritization exercise, classifying features into must have, should have, could have, and won&#x2019;t have [<xref ref-type="bibr" rid="ref32">32</xref>].</p></sec><sec id="s4-4-3"><title>User Testing of Discussion Board and Home Page</title><p>Given discussion boards as a high priority, user testing was conducted to determine user flows that support both anonymous and identifiable posts on a discussion board and to allow users to bookmark (save) posts for later reference. Feedback was also received on the design of the discussion board menu and the home page (<xref ref-type="fig" rid="figure4">Figure 4</xref>).</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Home page user testing with 2 layout options and 4 color options. Layout A uses a card layout with larger icons, while layout B uses a grid layout with smaller icons. Both layouts were presented with each color option.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig04.png"/></fig></sec><sec id="s4-4-4"><title>Further Postdeployment Development and Implementation</title><p>The new features and modifications identified through the postpilot focus groups and user testing were translated into wireframes by a contracted designer and then implemented by a contracted developer for the RCT of REACHOUT. Our platform team was required to fix bugs and defects internally and implement user-requested features that the developer had not delivered. These internal changes resulted in a 4-month delay in the launch of the REACHOUT app for the RCT.</p></sec></sec></sec><sec id="s5"><title>Platform Features</title><sec id="s5-1"><title>Overview</title><p>The iteration of the REACHOUT app that was released for the RCT contains the following 6 key features identified in the initial stage 1 focus groups: a 24/7 community chat room (group text messaging), topic-specific discussion boards, a peer supporter library, peer supporter profiles, small group virtual sessions (ie, virtual happy hours), and direct (one-to-one) messaging. Each of these features is described below, along with an accompanying figure showing the progression of development based on user feedback, from earliest design (conception) to the final iteration used for the RCT.</p></sec><sec id="s5-2"><title>24/7 Community Chat Room</title><p>The 24/7 chat room is a feature built upon Rocket.Chat&#x2019;s existing microservices architecture (<xref ref-type="fig" rid="figure5">Figure 5</xref>). Users can access a general-purpose discussion forum and send text, images, and voice messages. A banner reminds users of community rules, such as not providing peers with medical advice. In fact, group exchanges are monitored by research assistants and health care professionals (registered psychologist, dietitian, diabetes nurse, and pharmacist).</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>The concept and randomized controlled trial (RCT) interface of the 24/7 chatroom.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig05.png"/></fig></sec><sec id="s5-3"><title>Topic-Specific Discussion Boards</title><p>According to pilot study feedback, exchanges on the 24/7 chat room were perceived as overwhelming to some users, and message threads could easily be lost [<xref ref-type="bibr" rid="ref31">31</xref>]. This formed a new requirement: creating topic-specific discussion boards for focused messaging channels limited to a specific T1D topic. These discussion boards were developed as separate public messaging channels using Rocket.Chat&#x2019;s channel creation feature. The app was modified to create a designated menu page for topic-specific discussion boards. User-identified topics on current discussion boards include exercise, multiple daily injections, insulin pumps, insurance coverage, continuous glucose monitors, and traveling (<xref ref-type="fig" rid="figure6">Figure 6</xref>). The research team can add additional discussion boards, and frequently initiated topics will be retained for future platform instances.</p><fig position="float" id="figure6"><label>Figure 6.</label><caption><p>Discussion board iterations, including conception, wireframe, pilot iteration, and the randomized controlled trial (RCT) iteration, based on user feedback from the co-design and development process.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig06.png"/></fig></sec><sec id="s5-4"><title>Peer Supporter Library</title><p>The peer supporter library invites participants to self-select a peer supporter [<xref ref-type="bibr" rid="ref2">2</xref>]. The implementation of this feature was initially explored in two ways: (1) a participant (one who receives support) browses profiles from the library and then chooses their own peer supporter (active matching) or (2) a participant conveys their preferences to the research team, which assists with selection (passive matching). The active approach was adopted so that users could identify a peer supporter who best fits their unique support needs. For example, participants considering having children might prefer a peer supporter who is already a parent. Rocket.Chat&#x2019;s mobile app was customized to add this peer supporter library view (<xref ref-type="fig" rid="figure7">Figure 7</xref>). The library previews the first name and last initial, location, and age displayed as a card, with access to review the complete peer supporter profile enabled by tapping each profile card.</p><fig position="float" id="figure7"><label>Figure 7.</label><caption><p>Peer supporter library iterations, including conception, a second conception with a location-based library, a wireframe, and the randomized controlled trial (RCT) iteration.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig07.png"/></fig></sec><sec id="s5-5"><title>Peer Supporter Profile</title><p>To initiate an active matching approach, participants must determine which peer supporter best fits their support needs. To aid this, each peer supporter completes a profile that can be accessed through the peer supporter library [<xref ref-type="bibr" rid="ref2">2</xref>]. The characteristics included in each profile (<xref ref-type="fig" rid="figure8">Figure 8</xref>) are first name and initial of last name, age, age at the time of diagnosis, and devices used (eg, type of insulin pump and continuous glucose monitor). Each profile also contains a written biography and a 1-minute video biography accessible via a private YouTube link [<xref ref-type="bibr" rid="ref2">2</xref>].</p><fig position="float" id="figure8"><label>Figure 8.</label><caption><p>Peer supporter profile iterations, including conception, wireframe, pilot iteration in dark mode, and the randomized controlled trial (RCT) iteration.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig08.png"/></fig></sec><sec id="s5-6"><title>Small Group Virtual &#x201C;Happy Hour&#x201D; Sessions</title><p>&#x201C;Happy hours&#x201D; are virtual synchronous small group meetings led by peer supporters. They highlight distress-related themes, such as workplace bias and discrimination. Currently, information on virtual happy hours is shared via announcements posted to a discussion board, and sessions are held on Zoom (Zoom Video Communications Inc.). For the RCT, virtual happy hours replaced virtual huddles, featured in the previous pilot study [<xref ref-type="bibr" rid="ref2">2</xref>].</p></sec><sec id="s5-7"><title>Home Page</title><p>Adolescent focus groups identified a new requirement [<xref ref-type="bibr" rid="ref33">33</xref>]: an enhanced user interface and user experience, achieved by making the home page less intimidating and more visually appealing. One example was a landing page shown when the app opened (<xref ref-type="fig" rid="figure9">Figure 9</xref>). The home page also functions as a directory where users can navigate to other app areas.</p><fig position="float" id="figure9"><label>Figure 9.</label><caption><p>Home page iterations, including conception, pilot iteration without a home page (which directly jumped into the 24/7 chat room), and the randomized controlled trial (RCT) iteration after feedback from adolescent focus groups.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig09.png"/></fig></sec></sec><sec id="s6"><title>Initial Platform Utilization Patterns</title><p>To analyze trends in this peer network intervention, timestamps of messages, along with their senders and recipients, were logged between October 12, 2021, and March 15, 2022. A network analysis was performed using NetworkX [<xref ref-type="bibr" rid="ref34">34</xref>], and usage patterns were interpreted qualitatively by identifying patterns (numbers and widths) in edges, direction of communication, and temporal characteristics as the study progressed.</p><p>During a 6-month period when the app was deployed for the REACHOUT pilot study, 10,410 messages were sent, including 7116 one-to-one direct messages and 1389 chatroom messages; 179 private messaging groups were created. One-to-one messaging was the app&#x2019;s most common mode of written communication and was a key requirement. The most one-to-one messages were between peer supporter-participant pairs (3446), followed by 802 between peer supporters and health care team members. Users explained that group messaging, such as the 24/7 chatroom, was more commonly browsed than contributed to.</p><p>Substantial communication occurred between participants and their self-selected peer supporters (<xref ref-type="fig" rid="figure10">Figure 10</xref>), likely driven by an intervention requirement to engage with their assigned participants at least weekly (later changed to every 2 weeks based on feedback). This illustrates the app being used as intended, that is, as a mechanism to deliver peer-led mental health support primarily between a participant and their self-selected peer supporter. A total of 3446 messages were exchanged between participants and their self-selected peer supporters. However, communication methods varied among peer supporter-participant pairs, with some preferring Zoom or phone calls, which were not captured in the network graphs. Frequent communication also appeared to occur between peer supporters themselves and between peer supporters and the health care team.</p><fig position="float" id="figure10"><label>Figure 10.</label><caption><p>Network analysis showing communication patterns among app users by user type, specifically the defined roles assigned to users within the app (blue: research team, purple: health care team, orange: peer supporters, and green: participants). The number of messages sent is represented by the line width (edge weight), while the directionality of messages is not considered in this graph.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="diabetes_v11i1e71733_fig10.png"/></fig></sec><sec id="s7"><title>Insights and Observations: Challenges to Co-Design in mHealth</title><p>Through an iterative co-design process, we learned the importance of end-to-end user engagement to improve the user experience and ensure users&#x2019; needs are met. This collaboration refined the features developed from early iterations (eg, user-identified requirements for one-to-one support via direct messaging and group support in the 24/7 chatroom) into later iterations (eg, developing topic-specific discussion boards based on user feedback). Yet, the process was also challenging, particularly in establishing consensus on requirements across several focus groups, and when users&#x2019; stated wants did not align with what they needed [<xref ref-type="bibr" rid="ref35">35</xref>].</p><p>The focus groups used in the app design process varied in size&#x2014;this meant that the needs of 1 group were not necessarily representative of all users&#x2019; needs. We would seek input from different groups and, understandably, receive different opinions from each. It may have been beneficial to have a process to make the final call in these scenarios. We attempted strategies, such as voting or &#x201C;buying&#x201D; features, but ultimately<underline>,</underline> not everyone would be satisfied, as users will necessarily have unique needs.</p><p>While we had a general understanding of how features should function, the design and functional requirements were often not communicated clearly between the designer and the developer. Consequently, the delivered features sometimes differed from the research team&#x2019;s expectations. For example, the home page design was not implemented as displayed in the mock-up. We sought to resolve this by adding wireframes and gathering feedback from the team or participants earlier. However, frequently incorporating participant feedback to enhance the user experience sometimes led to revising features already developed or in progress, which hindered our progress.</p><p>Given that Rocket.Chat is a large open-source codebase with the React Native repository currently having 131 contributors, it took new developers significant time to onboard and become familiar with the codebase, which also led to delays. Furthermore, because our resources only allowed for a single contracted developer working part-time (20 hours per week), always remotely, and sometimes in different time zones, it took substantial effort to receive deliverables on time.</p><p>To mitigate these challenges, we took a hybrid approach following the pilot study for subsequent development and maintenance of the REACHOUT app by hiring a vendor to handle the development of complicated and time-consuming tasks, which were of lower priority, and an in-house product manager with technical expertise to manage the execution of the product development and budgetary management, proper communication of requirements to the vendor, biweekly release of the app for internal testing, and continuous assessment of the work performed by the vendor to resolve issues promptly. We also had internal student developers with a background in computer science on the research team that worked on urgent features, minor improvements, bug fixes, and internal app testing. This approach ensured improved coordination, task prioritization, project management, efficient development and quality control, and better documentation, helping eliminate skill gaps. Though we acknowledge that there are vendors who offer quality service at a reasonable cost and other vendors who are expensive, but take care with proper coordination, communication, management, design, development, and testing to ensure a quality product is delivered to their customers, we found our hybrid approach to be sustainable and budget-friendly compared to fully internal or fully external development, allowing us to release a stable and reliable version of the app to our users in a reasonable timeline.</p></sec><sec id="s8" sec-type="discussion"><title>Discussion</title><sec id="s8-1"><title>Overview of Findings</title><p>In collaboration with adults from the T1D community in British Columbia, we designed and implemented REACHOUT, a mobile app for adults with T1D in British Columbia, which seeks to reduce diabetes distress (a core facet of diabetes-specific mental health). This project builds upon previous work establishing virtual peer support as a viable strategy for reducing diabetes distress [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. Six key user-defined features for the app were identified through focus groups and refined through co-design and a pilot deployment: peer supporter profiles, a peer supporter library, one-to-one messaging, group messaging, topic-specific discussion boards, and small group virtual sessions.</p><p>The REACHOUT app uniquely features a user-driven &#x201C;match-making&#x201D; process to access one-on-one peer support [<xref ref-type="bibr" rid="ref2">2</xref>]. Specifically, each user chooses their peer supporter based on the factors that matter most to them (eg, shared hobbies, lifestyle, insulin pump and/or continuous glucose monitor brand, location of residence) rather than the selection determined by the research team or those administering the app. An iterative co-design approach enabled early and comprehensive user engagement, identified app requirements, enabled prompt identification of pain points (eg, usability issues and bugs), and provided us with ongoing formative feedback from end users.</p></sec><sec id="s8-2"><title>Limitations</title><p>Our app development process had its limitations. First, no formal usability testing was undertaken because (1) the importance of such testing was not initially identified and (2) the tight timelines and constrained resources of our behavioral research study were challenging. Formal usability testing using standardized questionnaires, such as the System Usability Scale [<xref ref-type="bibr" rid="ref36">36</xref>], Questionnaire for User Interaction Satisfaction [<xref ref-type="bibr" rid="ref37">37</xref>], or Post-Study System Usability Questionnaire [<xref ref-type="bibr" rid="ref38">38</xref>], could have ensured that users were sufficiently able to use the app and contribute to our overall understanding of feasibility. While the lack of formal usability testing may have affected the app&#x2019;s quality, user feedback from focus groups was incorporated before the app was used in the RCT. Additionally, focus group participants were predominantly female and self-selected, which may not reflect the larger T1D community in British Columbia. Future work should ensure diverse voices are represented when establishing app requirements, for example, by increasing the number of male participants.</p></sec><sec id="s8-3"><title>Future Work</title><p>The app has been deployed and is being evaluated in the REACHOUT RCT (NCT05668507). A formal usability evaluation should be performed to examine the app&#x2019;s functionality and identify opportunities for additional features or device optimization. Features currently in development, based on further user feedback, include allowing peer supporters to limit the number of participants they connect with. When evaluating usability, participants&#x2019; usage practices, motivations, and intents should also be examined to understand ideal usage patterns. We are also codeveloping an adolescent-focused version of the app [<xref ref-type="bibr" rid="ref33">33</xref>], which considers adolescents&#x2019; unique support needs and will be evaluated in a future trial.</p></sec><sec id="s8-4"><title>Conclusions</title><p>The REACHOUT app was developed to reduce diabetes distress by providing peer-led mental health support to adults living with T1D in British Columbia. The app development process was described to guide others on similar projects. An iterative co-design process with end-to-end user engagement and continual user feedback was beneficial, enabling a thorough understanding of end user needs, preferences, and context, and ensuring the final app was impactful and relevant to end users. The REACHOUT app offers choice-based, just-in-time, and customizable support, making it the optimal peer support model for individuals of all socioeconomic backgrounds, geographic residences, and life circumstances [<xref ref-type="bibr" rid="ref2">2</xref>]. Its potential to reduce diabetes distress and improve diabetes-specific mental health outcomes is being evaluated in a large-scale province-wide RCT.</p></sec></sec></body><back><ack><p>The authors thank all participants for sharing their ideas and insights and providing constructive feedback to shape the T1D REACHOUT platform and Nicholas West for editorial assistance. This work was previously presented, in part, at the American Diabetes Association&#x2019;s Annual Scientific Sessions in June 2022 in New Orleans, Louisiana, and June 2023 in San Diego, CA. Generative artificial intelligence tools were not used in this manuscript's writing, editing, or development.</p></ack><notes><sec><title>Funding</title><p>This study was supported, in part, by research grants from the Breakthrough T1D (2-SRA-2020-986-S-B), Breakthrough T1D Canada and Brain Canada (2- SRA-2022-1183-S-N). TST is supported by a Michael Smith Health Research BC/Breakthrough T1D Canada Health Professional-Investigator Award (HPI2021-2359). MG was supported by a Michael Smith Health Research BC scholar award (SCH-2020-0494) for the duration of the study.</p></sec><sec><title>Data Availability</title><p>The authors cannot share data due to privacy considerations agreed to by the research ethics board.</p></sec></notes><fn-group><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">AWS</term><def><p>Amazon Web Services</p></def></def-item><def-item><term id="abb2">mHealth</term><def><p>mobile health</p></def></def-item><def-item><term id="abb3">RCT</term><def><p>randomized controlled trial</p></def></def-item><def-item><term id="abb4">T1D</term><def><p>type 1 diabetes</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ashrafi</surname><given-names>S</given-names> </name><name name-style="western"><surname>Taylor</surname><given-names>D</given-names> </name><name name-style="western"><surname>Tang</surname><given-names>TS</given-names> </name></person-group><article-title>Moving beyond &#x201C;don&#x2019;t ask, don&#x2019;t tell&#x201D;: mental health needs of adults with type 1 diabetes in rural and remote regions of British Columbia</article-title><source>Diabet Med</source><year>2021</year><month>05</month><volume>38</volume><issue>5</issue><fpage>e14534</fpage><pub-id pub-id-type="doi">10.1111/dme.14534</pub-id><pub-id pub-id-type="medline">33524209</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tang</surname><given-names>TS</given-names> </name><name name-style="western"><surname>Klein</surname><given-names>G</given-names> </name><name name-style="western"><surname>G&#x00F6;rges</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Evaluating a mental health support mobile app for adults with type 1 diabetes living in rural and remote communities: the REACHOUT pilot study</article-title><source>Diabet Med</source><year>2025</year><month>03</month><volume>42</volume><issue>3</issue><fpage>e15451</fpage><pub-id pub-id-type="doi">10.1111/dme.15451</pub-id><pub-id pub-id-type="medline">39538423</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chin-Jung</surname><given-names>L</given-names> </name><name name-style="western"><surname>Hsiao-Yean</surname><given-names>C</given-names> </name><name name-style="western"><surname>Yeu-Hui</surname><given-names>C</given-names> </name><name name-style="western"><surname>Kuan-Chia</surname><given-names>L</given-names> </name><name name-style="western"><surname>Hui-Chuan</surname><given-names>H</given-names> </name></person-group><article-title>Effects of mobile health interventions on improving glycemic stability and quality of life in patients with type 1 diabetes: a meta-analysis</article-title><source>Res Nurs Health</source><year>2021</year><month>02</month><volume>44</volume><issue>1</issue><fpage>187</fpage><lpage>200</lpage><pub-id pub-id-type="doi">10.1002/nur.22094</pub-id><pub-id pub-id-type="medline">33368403</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wang</surname><given-names>X</given-names> </name><name name-style="western"><surname>Shu</surname><given-names>W</given-names> </name><name name-style="western"><surname>Du</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Mobile health in the management of type 1 diabetes: a systematic review and meta-analysis</article-title><source>BMC Endocr Disord</source><year>2019</year><month>02</month><day>13</day><volume>19</volume><issue>1</issue><fpage>21</fpage><pub-id pub-id-type="doi">10.1186/s12902-019-0347-6</pub-id><pub-id pub-id-type="medline">30760280</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wu</surname><given-names>X</given-names> </name><name name-style="western"><surname>Guo</surname><given-names>X</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>Z</given-names> </name></person-group><article-title>The efficacy of mobile phone apps for lifestyle modification in diabetes: systematic review and meta-analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>01</month><day>15</day><volume>7</volume><issue>1</issue><fpage>e12297</fpage><pub-id pub-id-type="doi">10.2196/12297</pub-id><pub-id pub-id-type="medline">30664494</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sun</surname><given-names>C</given-names> </name><name name-style="western"><surname>Malcolm</surname><given-names>JC</given-names> </name><name name-style="western"><surname>Wong</surname><given-names>B</given-names> </name><name name-style="western"><surname>Shorr</surname><given-names>R</given-names> </name><name name-style="western"><surname>Doyle</surname><given-names>MA</given-names> </name></person-group><article-title>Improving glycemic control in adults and children with type 1 diabetes with the use of smartphone-based mobile applications: a systematic review</article-title><source>Can J Diabetes</source><year>2019</year><month>02</month><volume>43</volume><issue>1</issue><fpage>51</fpage><lpage>58</lpage><pub-id pub-id-type="doi">10.1016/j.jcjd.2018.03.010</pub-id><pub-id pub-id-type="medline">30026048</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Pi</surname><given-names>L</given-names> </name><name name-style="western"><surname>Shi</surname><given-names>X</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Zhou</surname><given-names>Z</given-names> </name></person-group><article-title>Effect of smartphone apps on glycemic control in young patients with type 1 diabetes: a meta-analysis</article-title><source>Front Public Health</source><year>2023</year><volume>11</volume><fpage>1074946</fpage><pub-id pub-id-type="doi">10.3389/fpubh.2023.1074946</pub-id><pub-id pub-id-type="medline">37064701</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Adu</surname><given-names>MD</given-names> </name><name name-style="western"><surname>Malabu</surname><given-names>UH</given-names> </name><name name-style="western"><surname>Malau-Aduli</surname><given-names>AEO</given-names> </name><name name-style="western"><surname>Malau-Aduli</surname><given-names>BS</given-names> </name></person-group><article-title>The development of My Care Hub mobile-phone app to support self-management in Australians with type 1 diabetes or type 2 diabetes</article-title><source>Sci Rep</source><year>2020</year><month>01</month><day>8</day><volume>10</volume><issue>1</issue><fpage>7</fpage><pub-id pub-id-type="doi">10.1038/s41598-019-56411-0</pub-id><pub-id pub-id-type="medline">31913296</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Castens&#x00F8;e-Seidenfaden</surname><given-names>P</given-names> </name><name name-style="western"><surname>Reventlov Husted</surname><given-names>G</given-names> </name><name name-style="western"><surname>Teilmann</surname><given-names>G</given-names> </name><name name-style="western"><surname>Hommel</surname><given-names>E</given-names> </name><name name-style="western"><surname>Olsen</surname><given-names>BS</given-names> </name><name name-style="western"><surname>Kensing</surname><given-names>F</given-names> </name></person-group><article-title>Designing a self-management app for young people with type 1 diabetes: methodological challenges, experiences, and recommendations</article-title><source>JMIR Mhealth Uhealth</source><year>2017</year><month>10</month><day>23</day><volume>5</volume><issue>10</issue><fpage>e124</fpage><pub-id pub-id-type="doi">10.2196/mhealth.8137</pub-id><pub-id pub-id-type="medline">29061552</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>de Jongh</surname><given-names>T</given-names> </name><name name-style="western"><surname>Gurol-Urganci</surname><given-names>I</given-names> </name><name name-style="western"><surname>Vodopivec-Jamsek</surname><given-names>V</given-names> </name><name name-style="western"><surname>Car</surname><given-names>J</given-names> </name><name name-style="western"><surname>Atun</surname><given-names>R</given-names> </name></person-group><article-title>Mobile phone messaging for facilitating self-management of long-term illnesses</article-title><source>Cochrane Database Syst Rev</source><year>2012</year><month>12</month><day>12</day><volume>12</volume><issue>12</issue><fpage>CD007459</fpage><pub-id pub-id-type="doi">10.1002/14651858.CD007459.pub2</pub-id><pub-id pub-id-type="medline">23235644</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bellei</surname><given-names>EA</given-names> </name><name name-style="western"><surname>Biduski</surname><given-names>D</given-names> </name><name name-style="western"><surname>Lisboa</surname><given-names>HRK</given-names> </name><name name-style="western"><surname>De Marchi</surname><given-names>ACB</given-names> </name></person-group><article-title>Development and assessment of a mobile health application for monitoring the linkage among treatment factors of type 1 diabetes mellitus</article-title><source>Telemed J E Health</source><year>2020</year><month>02</month><volume>26</volume><issue>2</issue><fpage>205</fpage><lpage>217</lpage><pub-id pub-id-type="doi">10.1089/tmj.2018.0329</pub-id><pub-id pub-id-type="medline">30724717</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tang</surname><given-names>TS</given-names> </name><name name-style="western"><surname>Yip</surname><given-names>AKW</given-names> </name><name name-style="western"><surname>Klein</surname><given-names>G</given-names> </name><etal/></person-group><article-title>Training peers to deliver mental health support to adults with type 1 diabetes using the REACHOUT mobile app</article-title><source>Diabet Med</source><year>2024</year><month>03</month><volume>41</volume><issue>3</issue><fpage>e15210</fpage><pub-id pub-id-type="doi">10.1111/dme.15210</pub-id><pub-id pub-id-type="medline">37634222</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tang</surname><given-names>TS</given-names> </name><name name-style="western"><surname>Seddigh</surname><given-names>S</given-names> </name><name name-style="western"><surname>Halbe</surname><given-names>E</given-names> </name><name name-style="western"><surname>Vesco</surname><given-names>AT</given-names> </name></person-group><article-title>Testing 3 digital health platforms to improve mental health outcomes in adults with type 1 diabetes: a pilot trial</article-title><source>Can J Diabetes</source><year>2024</year><month>02</month><volume>48</volume><issue>1</issue><fpage>18</fpage><lpage>25</lpage><pub-id pub-id-type="doi">10.1016/j.jcjd.2023.08.006</pub-id><pub-id pub-id-type="medline">37625504</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Muijs</surname><given-names>LT</given-names> </name><name name-style="western"><surname>de Wit</surname><given-names>M</given-names> </name><name name-style="western"><surname>Knoop</surname><given-names>H</given-names> </name><name name-style="western"><surname>Snoek</surname><given-names>FJ</given-names> </name></person-group><article-title>Feasibility and user experience of the unguided web-based self-help app &#x201C;MyDiaMate&#x201D; aimed to prevent and reduce psychological distress and fatigue in adults with diabetes</article-title><source>Internet Interv</source><year>2021</year><month>09</month><volume>25</volume><fpage>100414</fpage><pub-id pub-id-type="doi">10.1016/j.invent.2021.100414</pub-id><pub-id pub-id-type="medline">34401373</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Rondags</surname><given-names>SMPA</given-names> </name><name name-style="western"><surname>de Wit</surname><given-names>M</given-names> </name><name name-style="western"><surname>Twisk</surname><given-names>JW</given-names> </name><name name-style="western"><surname>Snoek</surname><given-names>FJ</given-names> </name></person-group><article-title>Effectiveness of HypoAware, a brief partly web-based psychoeducational intervention for adults with type 1 and insulin-treated type 2 diabetes and problematic hypoglycemia: a cluster randomized controlled trial</article-title><source>Diabetes Care</source><year>2016</year><month>12</month><volume>39</volume><issue>12</issue><fpage>2190</fpage><lpage>2196</lpage><pub-id pub-id-type="doi">10.2337/dc16-1614</pub-id><pub-id pub-id-type="medline">27797931</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yakubu</surname><given-names>TI</given-names> </name><name name-style="western"><surname>Pawer</surname><given-names>S</given-names> </name><name name-style="western"><surname>West</surname><given-names>NC</given-names> </name><name name-style="western"><surname>Tang</surname><given-names>TS</given-names> </name><name name-style="western"><surname>G&#x00F6;rges</surname><given-names>M</given-names> </name></person-group><article-title>Impact of digitally enabled peer support interventions on diabetes distress and depressive symptoms in people living with type 1 diabetes: a systematic review</article-title><source>Curr Diab Rep</source><year>2025</year><month>12</month><volume>25</volume><issue>1</issue><fpage>1</fpage><pub-id pub-id-type="doi">10.1007/s11892-024-01560-4</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tamhane</surname><given-names>S</given-names> </name><name name-style="western"><surname>Rodriguez-Gutierrez</surname><given-names>R</given-names> </name><name name-style="western"><surname>Hargraves</surname><given-names>I</given-names> </name><name name-style="western"><surname>Montori</surname><given-names>VM</given-names> </name></person-group><article-title>Shared decision-making in diabetes care</article-title><source>Curr Diab Rep</source><year>2015</year><month>12</month><volume>15</volume><issue>12</issue><fpage>112</fpage><pub-id pub-id-type="doi">10.1007/s11892-015-0688-0</pub-id><pub-id pub-id-type="medline">26458383</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bradway</surname><given-names>M</given-names> </name><name name-style="western"><surname>Morris</surname><given-names>RL</given-names> </name><name name-style="western"><surname>Giordanengo</surname><given-names>A</given-names> </name><name name-style="western"><surname>&#x00C5;rsand</surname><given-names>E</given-names> </name></person-group><article-title>How mHealth can facilitate collaboration in diabetes care: qualitative analysis of co-design workshops</article-title><source>BMC Health Serv Res</source><year>2020</year><month>11</month><day>30</day><volume>20</volume><issue>1</issue><fpage>1104</fpage><pub-id pub-id-type="doi">10.1186/s12913-020-05955-3</pub-id><pub-id pub-id-type="medline">33256732</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Moore</surname><given-names>A</given-names> </name><name name-style="western"><surname>Cepeda</surname><given-names>J</given-names> </name><name name-style="western"><surname>Franklin</surname><given-names>B</given-names> </name><name name-style="western"><surname>Abreu</surname><given-names>G</given-names> </name><name name-style="western"><surname>Dorth</surname><given-names>S</given-names> </name><name name-style="western"><surname>Barkley</surname><given-names>E</given-names> </name></person-group><article-title>Dominican adolescents&#x2019; preferences for content, design, and functionality of a mobile application for type 1 diabetes mellitus self-management</article-title><source>Can J Diabetes</source><year>2023</year><month>12</month><volume>47</volume><issue>8</issue><fpage>665</fpage><lpage>671</lpage><pub-id pub-id-type="doi">10.1016/j.jcjd.2023.07.006</pub-id><pub-id pub-id-type="medline">37481124</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wilson</surname><given-names>LM</given-names> </name><name name-style="western"><surname>Tyler</surname><given-names>N</given-names> </name><name name-style="western"><surname>Jacobs</surname><given-names>PG</given-names> </name><etal/></person-group><article-title>Patient input for design of a decision support smartphone application for type 1 diabetes</article-title><source>J Diabetes Sci Technol</source><year>2020</year><month>11</month><volume>14</volume><issue>6</issue><fpage>1081</fpage><lpage>1087</lpage><pub-id pub-id-type="doi">10.1177/1932296819870231</pub-id><pub-id pub-id-type="medline">31441336</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Holtz</surname><given-names>BE</given-names> </name><name name-style="western"><surname>Mitchell</surname><given-names>K</given-names> </name></person-group><article-title>Best practices for developing a diabetes mHealth app</article-title><source>J Diabetes Sci Technol</source><year>2024</year><month>01</month><volume>18</volume><issue>1</issue><fpage>39</fpage><lpage>45</lpage><pub-id pub-id-type="doi">10.1177/19322968231195849</pub-id><pub-id pub-id-type="medline">37644831</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Alfonsi</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Choi</surname><given-names>EEY</given-names> </name><name name-style="western"><surname>Arshad</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Carbohydrate counting app using image recognition for youth with type 1 diabetes: pilot randomized control trial</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>10</month><day>28</day><volume>8</volume><issue>10</issue><fpage>e22074</fpage><pub-id pub-id-type="doi">10.2196/22074</pub-id><pub-id pub-id-type="medline">33112249</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chatzakis</surname><given-names>C</given-names> </name><name name-style="western"><surname>Floros</surname><given-names>D</given-names> </name><name name-style="western"><surname>Papagianni</surname><given-names>M</given-names> </name><etal/></person-group><article-title>The beneficial effect of the mobile application Euglyca in children and adolescents with type 1 diabetes mellitus: a randomized controlled trial</article-title><source>Diabetes Technol Ther</source><year>2019</year><month>11</month><volume>21</volume><issue>11</issue><fpage>627</fpage><lpage>634</lpage><pub-id pub-id-type="doi">10.1089/dia.2019.0170</pub-id><pub-id pub-id-type="medline">31335204</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Blanchard</surname><given-names>J</given-names> </name><name name-style="western"><surname>Ahmed</surname><given-names>S</given-names> </name><name name-style="western"><surname>Clark</surname><given-names>B</given-names> </name><name name-style="western"><surname>Sanchez Cotto</surname><given-names>L</given-names> </name><name name-style="western"><surname>Rangasamy</surname><given-names>S</given-names> </name><name name-style="western"><surname>Thompson</surname><given-names>B</given-names> </name></person-group><article-title>Design and testing of a smartphone application for real-time tracking of CSII and CGM site rotation compliance in patients with type 1 diabetes</article-title><source>J Diabetes Sci Technol</source><year>2024</year><month>07</month><volume>18</volume><issue>4</issue><fpage>937</fpage><lpage>945</lpage><pub-id pub-id-type="doi">10.1177/19322968221145178</pub-id><pub-id pub-id-type="medline">36539997</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shetty</surname><given-names>VB</given-names> </name><name name-style="western"><surname>Fried</surname><given-names>L</given-names> </name><name name-style="western"><surname>Roby</surname><given-names>HC</given-names> </name><etal/></person-group><article-title>Development of a novel mobile health app to empower young people with type 1 diabetes to exercise safely: co-design approach</article-title><source>JMIR Diabetes</source><year>2024</year><month>07</month><day>30</day><volume>9</volume><fpage>e51491</fpage><pub-id pub-id-type="doi">10.2196/51491</pub-id><pub-id pub-id-type="medline">39078700</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ng</surname><given-names>JYY</given-names> </name><name name-style="western"><surname>Ntoumanis</surname><given-names>N</given-names> </name><name name-style="western"><surname>Th&#x00F8;gersen-Ntoumani</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Self-determination theory applied to health contexts: a meta-analysis</article-title><source>Perspect Psychol Sci</source><year>2012</year><month>07</month><volume>7</volume><issue>4</issue><fpage>325</fpage><lpage>340</lpage><pub-id pub-id-type="doi">10.1177/1745691612447309</pub-id><pub-id pub-id-type="medline">26168470</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="web"><source>Slack</source><access-date>2024-11-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://app.slack.com/plans/T078CK2H98S">https://app.slack.com/plans/T078CK2H98S</ext-link></comment></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="web"><article-title>Rocket.Chat pricing</article-title><source>Rocket.Chat</source><access-date>2024-11-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.rocket.chat/pricing">https://www.rocket.chat/pricing</ext-link></comment></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="web"><article-title>Mattermost pricing</article-title><source>Mattermost</source><access-date>2024-11-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://mattermost.com/pricing/">https://mattermost.com/pricing/</ext-link></comment></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jeminiwa</surname><given-names>RN</given-names> </name><name name-style="western"><surname>Hohmann</surname><given-names>NS</given-names> </name><name name-style="western"><surname>Fox</surname><given-names>BI</given-names> </name></person-group><article-title>Developing a theoretical framework for evaluating the quality of mHealth apps for adolescent users: a systematic review</article-title><source>J Pediatr Pharmacol Ther</source><year>2019</year><volume>24</volume><issue>4</issue><fpage>254</fpage><lpage>269</lpage><pub-id pub-id-type="doi">10.5863/1551-6776-24.4.254</pub-id><pub-id pub-id-type="medline">31337988</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lam</surname><given-names>D</given-names> </name><name name-style="western"><surname>Jhajj</surname><given-names>P</given-names> </name><name name-style="western"><surname>Sherifali</surname><given-names>D</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>FS</given-names> </name><name name-style="western"><surname>Tang</surname><given-names>TS</given-names> </name></person-group><article-title>Exploring the REACHOUT mental health support app for type 1 diabetes from the perspectives of recipients and providers of peer support: qualitative study</article-title><source>JMIR Diabetes</source><year>2026</year><month>01</month><day>21</day><volume>11</volume><fpage>e72779</fpage><pub-id pub-id-type="doi">10.2196/72779</pub-id><pub-id pub-id-type="medline">41564292</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Clegg</surname><given-names>D</given-names> </name><name name-style="western"><surname>Barker</surname><given-names>R</given-names> </name></person-group><source>Case Method Fast-Track: A Rad Approach</source><year>1994</year><access-date>2026-02-21</access-date><publisher-name>Addison-Wesley Publishing Company</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://books.google.co.in/books/about/CASE_Method_Fast_track.html?id=86ZfQgAACAAJ&#x0026;redir_esc=y">https://books.google.co.in/books/about/CASE_Method_Fast_track.html?id=86ZfQgAACAAJ&#x0026;redir_esc=y</ext-link></comment><pub-id pub-id-type="other">9780201624328</pub-id></nlm-citation></ref><ref id="ref33"><label>33</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yakubu</surname><given-names>TI</given-names> </name><name name-style="western"><surname>Jhajj</surname><given-names>P</given-names> </name><name name-style="western"><surname>Pawer</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Exploring the needs and preferences of users and parents to design a mobile app to deliver mental health peer support to adolescents with type 1 diabetes: qualitative study</article-title><source>JMIR Diabetes</source><year>2025</year><month>01</month><day>20</day><volume>10</volume><fpage>e64267</fpage><pub-id pub-id-type="doi">10.2196/64267</pub-id><pub-id pub-id-type="medline">39832366</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Hagberg</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Schult</surname><given-names>DA</given-names> </name><name name-style="western"><surname>Swart</surname><given-names>PJ</given-names> </name></person-group><article-title>Exploring network structure, dynamics, and function using NetworkX</article-title><conf-name>Python in Science Conference</conf-name><conf-date>Aug 19-24, 2008</conf-date><pub-id pub-id-type="doi">10.25080/TCWV9851</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Morita</surname><given-names>PP</given-names> </name><name name-style="western"><surname>Cafazzo</surname><given-names>JA</given-names> </name></person-group><article-title>Challenges and paradoxes of human factors in health technology design</article-title><source>JMIR Hum Factors</source><year>2016</year><month>03</month><day>1</day><volume>3</volume><issue>1</issue><fpage>e11</fpage><pub-id pub-id-type="doi">10.2196/humanfactors.4653</pub-id><pub-id pub-id-type="medline">27025862</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Brooke</surname><given-names>J</given-names> </name></person-group><article-title>SUS: a &#x201C;quick and dirty&#x201D; usability scale</article-title><source>Usability Evaluation in Industry</source><year>1996</year><access-date>2026-02-21</access-date><volume>189</volume><edition>1</edition><publisher-name>CRC Press</publisher-name><fpage>4</fpage><lpage>7</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://www.taylorfrancis.com/chapters/edit/10.1201/9781498710411-35/sus-quick-dirty-usability-scale-john-brooke">https://www.taylorfrancis.com/chapters/edit/10.1201/9781498710411-35/sus-quick-dirty-usability-scale-john-brooke</ext-link></comment></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Chin</surname><given-names>JP</given-names> </name><name name-style="western"><surname>Diehl</surname><given-names>VA</given-names> </name><name name-style="western"><surname>Norman</surname><given-names>LK</given-names> </name></person-group><article-title>Development of an instrument measuring user satisfaction of the human-computer interface</article-title><year>1988</year><conf-name>The SIGCHI Conference</conf-name><conf-date>May 1-5, 1988</conf-date><pub-id pub-id-type="doi">10.1145/57167.57203</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Sauro</surname><given-names>J</given-names> </name><name name-style="western"><surname>Lewis</surname><given-names>JR</given-names> </name></person-group><article-title>Standardized usability questionnaires</article-title><source>Quantifying the User Experience: Practical Statistics for User Research</source><year>2012</year><access-date>2026-02-21</access-date><publisher-name>Morgan Kaufmann</publisher-name><fpage>185</fpage><lpage>240</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://www.sciencedirect.com/book/monograph/9780123849687/quantifying-the-user-experience?utm_source=chatgpt.com">https://www.sciencedirect.com/book/monograph/9780123849687/quantifying-the-user-experience?utm_source=chatgpt.com</ext-link></comment><pub-id pub-id-type="doi">10.1016/B978-0-12-384968-7.00008-4</pub-id></nlm-citation></ref></ref-list></back></article>