<?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 Hum Factors</journal-id><journal-id journal-id-type="publisher-id">humanfactors</journal-id><journal-id journal-id-type="index">6</journal-id><journal-title>JMIR Human Factors</journal-title><abbrev-journal-title>JMIR Hum Factors</abbrev-journal-title><issn pub-type="epub">2292-9495</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">v12i1e73935</article-id><article-id pub-id-type="doi">10.2196/73935</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>A Messaging App Empowering Lifestyle Modification in Chronic Kidney Disease (LINE Official Account &#x201C;Kidney Lifestyle&#x201D;): Platform Development and Usability Study</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Ho</surname><given-names>Chun-Yi</given-names></name><degrees>MEd</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Siregar</surname><given-names>Deborah</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Yen</surname><given-names>Miaofen</given-names></name><degrees>PhD, RN</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Sung</surname><given-names>Junne-Ming</given-names></name><degrees>MD, Prof Dr Med</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Wang</surname><given-names>Ming-Cheng</given-names></name><degrees>MD, Prof Dr Med</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lin</surname><given-names>Wei-Hung</given-names></name><degrees>MD, Prof Dr Med, PhD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Nursing, College of Medicine, National Cheng Kung University</institution><addr-line>No. 1, Daxue Rd, East Dist</addr-line><addr-line>Tainan City</addr-line><country>Taiwan</country></aff><aff id="aff2"><institution>Division of Nephrology, Department of Internal Medicine, National Cheng Kung University Hospital, College of Medicine, National Cheng Kung University</institution><addr-line>Tainan City</addr-line><country>Taiwan</country></aff><aff id="aff3"><institution>Division of General Internal Medicine, Department of Internal Medicine, National Cheng Kung University Hospital, College of Medicine, National Cheng Kung University</institution><addr-line>Tainan City</addr-line><country>Taiwan</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Borycki</surname><given-names>Elizabeth</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Gasmi</surname><given-names>Maha</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Wiraguna</surname><given-names>Rayie</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Miaofen Yen, PhD, RN, Department of Nursing, College of Medicine, National Cheng Kung University, No. 1, Daxue Rd, East Dist, Tainan City, 701401, Taiwan, 886 6-235-3535 ext 5823; <email>miaofen@mail.ncku.edu.tw</email></corresp></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>26</day><month>11</month><year>2025</year></pub-date><volume>12</volume><elocation-id>e73935</elocation-id><history><date date-type="received"><day>08</day><month>05</month><year>2025</year></date><date date-type="accepted"><day>21</day><month>10</month><year>2025</year></date></history><copyright-statement>&#x00A9; Chun-Yi Ho, Deborah Siregar, Miaofen Yen, Junne-Ming Sung, Ming-Cheng Wang, Wei-Hung Lin. Originally published in JMIR Human Factors (<ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>), 26.11.2025. </copyright-statement><copyright-year>2025</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 Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.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://humanfactors.jmir.org/2025/1/e73935"/><abstract><sec><title>Background</title><p>Regular lifestyle modification is crucial for chronic kidney disease (CKD) management; yet, older patients often struggle to sustain behavior change and rely on support from their significant others such as family caregivers or partners. In such cases, both members of the dyad require accessible, jointly usable tools to maintain healthier behaviors over time. Given the ubiquity of instant messaging platforms, a digital intervention delivered via such a platform offers strong potential to empower CKD dyads in active lifestyle modification.</p></sec><sec><title>Objective</title><p>Guided by the Digital Dyadic Empowerment Framework, this study aimed to develop, optimize, and test the usability of a digital platform named &#x201C;Kidney Lifestyle,&#x201D; using the LINE Official Account (OA) and an integrated extended app to facilitate collaborative lifestyle modification among CKD dyads.</p></sec><sec sec-type="methods"><title>Methods</title><p>We adopted a three-phase Agile-based development cycle: (1) iterative development and trial use, (2) heuristic evaluation, and (3) usability testing. In phase 1, the platform prototype was codeveloped with health care professionals and trialed by CKD dyads who provided feedback on interface clarity, ease of use, acceptance, intention to continue usage, and overall satisfaction. In phase 2, multidisciplinary experts conducted heuristic evaluations, rating compliance with Nielsen&#x2019;s 10 usability principles and suggesting improvements. In phase 3, experienced CKD dyads from phase 1 performed 6 representative tasks using the platform. Task success rates, completion times, and operational errors were recorded, and usability perceptions were assessed using the After-Scenario Questionnaire (1&#x2010;7) and the System Usability Scale (0&#x2010;100).</p></sec><sec sec-type="results"><title>Results</title><p>In phase 1, 10 CKD dyads (19 individuals) reported high acceptance (mean overall satisfaction 4.1/5), valuing real-time interaction, convenient health data monitoring, and educational resources. In phase 2, 5 experts found high usability compliance (89%&#x2010;93%) but noted navigation complexity and the need for more interactive feedback. In phase 3, usability testing with 5 dyads showed high task success (60%&#x2010;100%) and short completion times (1&#x2010;5 minutes). Extended app tasks used for structured self-monitoring achieved higher satisfaction, reflecting simpler navigation than tasks within the LINE OA (mean After-Scenario Questionnaire 5.64 vs 3.87). Navigation difficulties within LINE OA were likely due to multilayered menus and limited customization. The average System Usability Scale was 67.5, indicating marginally acceptable usability.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>The LINE-based digital dyadic empowerment platform &#x201C;Kidney Lifestyle<italic>&#x201D;</italic> demonstrated promising usability and engagement. It has clinical potential to improve CKD control by extending health education, enabling continuous self-monitoring, and allowing clinicians to track patients&#x2019; daily living conditions. To enhance effectiveness, future work should include a larger-scale feasibility trial while pursuing ongoing platform optimization, specifically by simplifying navigation pathways, adding a return option, and improving interactive feedback. The platform is now publicly accessible via LINE ID search, as provided in phase 1 results.</p></sec></abstract><kwd-group><kwd>chronic kidney disease</kwd><kwd>dyadic empowerment</kwd><kwd>lifestyle modification</kwd><kwd>digital health</kwd><kwd>instant messaging</kwd><kwd>usability testing</kwd><kwd>LINE app</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><sec id="s1-1"><title>Background</title><p>Chronic kidney disease (CKD) poses a serious burden to global health, affecting approximately 9.1% of the population or around 700 million people worldwide [<xref ref-type="bibr" rid="ref1">1</xref>]. In Taiwan, the increasing prevalence of end-stage kidney disease has escalated health care costs, imposing substantial strain on the National Health Insurance system [<xref ref-type="bibr" rid="ref2">2</xref>]. Effective CKD management can delay disease progression to end-stage kidney disease, reduce the risk of complications, and enhance patients&#x2019; quality of life [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. However, significant barriers remain, including insufficient continuous monitoring, limited patient education, and restricted access to health care providers [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>].</p><p>CKD primarily affects older adults, especially those older than 60 years with lower educational levels, underscoring the need for tailored interventions for this group [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. Digital health interventions (DHIs) offer unique opportunities to maintain patient engagement and provide tailored health education, particularly for older adults to improve autonomy and overall well-being [<xref ref-type="bibr" rid="ref11">11</xref>]. With the widespread use of digital and mobile technologies, DHIs have become a key part of chronic care, supporting various health needs effectively [<xref ref-type="bibr" rid="ref12">12</xref>]. Previous studies have shown that DHIs can improve self-management among patients with CKD [<xref ref-type="bibr" rid="ref13">13</xref>]. This potential has led to the ongoing development of diverse tools&#x2014;ranging from smartphone apps to web-based platforms&#x2014;designed to support CKD and dialysis self-care [<xref ref-type="bibr" rid="ref14">14</xref>-<xref ref-type="bibr" rid="ref17">17</xref>].</p><p>Building on these advances, instant messaging platforms have emerged as promising tools for ubiquitous CKD management support. LINE, in particular, has gained significant popularity in Asia due to its user-friendly interface and broad demographic reach, effectively engaging users of all ages [<xref ref-type="bibr" rid="ref18">18</xref>]. In Taiwan, LINE dominates the instant messaging market with more than 90% market share, making it a highly suitable platform for health communication [<xref ref-type="bibr" rid="ref19">19</xref>]. The LINE app has already demonstrated potential in facilitating health education and self-management among middle-aged patients with CKD [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. However, a LINE-based platform promoting lifestyle modification for older (older than 60 years) patients with CKD and their caregivers remains scarce. The extensive user base of LINE presents a unique opportunity to deliver cost-effective DHIs supporting multifaceted CKD management for this older population through a LINE Official Account (LINE OA).</p></sec><sec id="s1-2"><title>Previous Work</title><p>In our previous work, we developed the Digital Dyadic Empowerment Framework (DDEF) as a conceptual and practical guide for designing DHIs that empower both patients with CKD and their significant others (SOs) (eg, spouses and children) to sustain lifestyle modification. The framework identifies 5 core domains of dyadic empowerment, including <italic>perceived control</italic>, <italic>understanding</italic>, <italic>adaptation</italic>, <italic>dyadic efficacy</italic>, and <italic>dyadic support</italic>. It further proposes 5 digital strategies: <italic>digital education</italic>, <italic>digital communication</italic>, <italic>digital monitoring</italic>, <italic>digital feedback</italic>, and <italic>digital analysis</italic>, through which DHIs can be designed to strengthen these dyadic empowerment domains. Together, these domains and strategies specify <italic>what</italic> to empower in the dyad and <italic>how</italic> to operationalize dyadic empowerment through concrete digital features, providing a structured pathway for designing and evaluating DHIs that support collaborative CKD self-management.</p></sec><sec id="s1-3"><title>Objectives</title><p>This study aimed to develop, evaluate, and optimize the usability of the LINE-based digital platform &#x201C;Kidney Lifestyle&#x201D; for CKD dyads. The platform was directly developed under the guidance of the DDEF, applying its 5 digital strategies to strengthen dyadic empowerment and promote sustainable lifestyle modification among CKD dyads. This research specifically investigates the platform&#x2019;s usability, user acceptance, and potential clinical application in CKD management.</p></sec></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design</title><p>Following the guidelines outlined by Kushniruk and Patel [<xref ref-type="bibr" rid="ref22">22</xref>], a 3-phase iterative system development cycle was used to develop and test our LINE-based digital dyadic empowerment platform. These phases included (1) iterative development and trial use, (2) heuristic evaluation, and (3) usability testing (<xref ref-type="fig" rid="figure1">Figure 1</xref>). An Agile project management methodology was applied throughout the development cycle to manage initial uncertainties and facilitate continuous stakeholder interaction [<xref ref-type="bibr" rid="ref23">23</xref>]. During each phase, participants identified usability issues, which guided subsequent refinements of the digital platform. The details of each phase are described in the following sections.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>A visualization of the 3-phase iterative system development cycle. Blue arrows denote the input provided by the participants from each phase. ASQ: After-Scenario Questionnaire; CKD: chronic kidney disease; SUS: System Usability Scale.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e73935_fig01.png"/></fig></sec><sec id="s2-2"><title>Phase 1: Iterative Development and Trial Use</title><p>Phase 1 focused on developing the platform, especially the functionalities and content. Summarizing retrospectively, the platform development process involved the following four iterative steps: (1) platform establishment, (2) technical partner collaboration, (3) extended platform development, and (4) all platform integration and intervention design.</p><sec id="s2-2-1"><title>Step 1: Platform Establishment</title><p>A regular LINE OA was first set up to explore its basic functionalities, applying two functions aligned with 3 DDEF digital strategies: (1) chat: &#x201C;Digital Feedback&#x201D; and &#x201C;Digital Communication,&#x201D; and (2) multimedia and multipage messages: &#x201C;Digital Education.&#x201D; For example, CKD-related information (eg, symptoms, staging, and risk factors) could be delivered through autoresponse messages triggered by specific keywords. However, such keyword-based use was inconvenient and insufficient for promoting lifestyle modification among CKD dyads, as prior medical applications of LINE OAs mainly focused on clinic operations (eg, appointment scheduling and reminders) rather than ongoing lifestyle support [<xref ref-type="bibr" rid="ref24">24</xref>]. These limitations highlighted the need for integration with third-party application programming interface (API) plug-ins to enable more advanced functionalities.</p></sec><sec id="s2-2-2"><title>Step 2: Technical Partner Collaboration</title><p>AlleyPin Interactive Ltd Co is a LINE-certified Gold-level technical partner in the health care industry, providing API technical resources to meet diverse needs. Their cloud-based doctor-patient interaction management system, &#x201C;DoctorConnect 1.Talk,&#x201D; when integrated with the team&#x2019;s LINE OA, can provide more advanced and user-friendly functionalities, including (1) service menu setup: it allows up to 8 buttons with multilayered structures for resource integration, beyond the 6-button limit of LINE OA; (2) enhanced multimedia and multipage messages: multiple buttons can be set within a single message, enabling users to access tailored health information via menu clicks without manual text input; and (3) case tracking system: it supports member management, scheduled &#x201C;Push&#x201D; messages, and interaction through AlleyPin&#x2019;s independent backend.</p><p>The service menu content and layout were designed not only by following the DDEF but also in consultation with a health education nurse from a university-affiliated hospital and 2 nephrologists, ensuring the platform met clinical needs. Through the integration of LINE OA and AlleyPin Interactive&#x2019;s API plug-in, our platform now effectively adopted 3 digital strategies&#x2014;&#x201C;Digital Education,&#x201D; &#x201C;Digital Feedback,&#x201D; and &#x201C;Digital Communication<italic>&#x201D;</italic>&#x2014;to support CKD dyads. To further apply the other 2 digital strategies&#x2014;&#x201C;Digital Monitoring&#x201D; and &#x201C;Digital Analysis,&#x201D; an extended app was developed and integrated with the LINE OA in the next step.</p></sec><sec id="s2-2-3"><title>Step 3: Extended App (AppSheet) Development</title><p>After exploring various options and evaluating alternative platforms, the team discovered that Google&#x2019;s AppSheet platform could effectively compensate for the current platform&#x2019;s shortcomings and integrate with LINE OA. AppSheet is a platform for developing mobile and web apps that do not require programming code and can integrate with cloud spreadsheets or databases such as Google Drive and Office 365 as data sources [<xref ref-type="bibr" rid="ref25">25</xref>]. The team immediately began developing the app prototype and conducted iterative testing.</p></sec><sec id="s2-2-4"><title>Step 4: Platform Integration and Intervention Design</title><p>As the digital platform was not selected during the development of DDEF, the team, after the platform selection and development process outlined in steps 1-3, reviewed the correspondence between the DDEF and the functions provided by this integrated digital platform. Based on this, interventions were designed to promote lifestyle modification for CKD dyads.</p></sec><sec id="s2-2-5"><title>Platform Trial Use</title><p>After establishing our digital platform prototype, the team invited 10 early-stage CKD (stages 1-3) dyads receiving regular treatment at a university hospital to use the platform in their daily lives. Besides assisting dyads in installing the digital platform on their smartphones, a user manual (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) was provided for each dyad to learn the operations at home. At the time of enrollment, operational instructions for various functions were provided by a research assistant (CYH) according to the manual.</p><p>A user feedback form (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>) was provided to be filled out by the dyads at least 1 month apart during their next clinic visit. For each of the 6 major functions, the form assessed the following five elements: (1) interface clarity, (2) ease of operation, (3) acceptability: like or not, (4) intention to continue usage, and (5) satisfaction rating from 1 to 5 (<xref ref-type="table" rid="table1">Table 1</xref>). A brief interview was conducted with each dyad to obtain further feedback. The platform was iteratively optimized based on both system usage data and user feedback.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Content of user feedback form for phase 1 dyadic trial use<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" colspan="3">Element (item number) and question</td><td align="left" valign="bottom">Type</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="4">Interface clarity (N-1)</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Are there any unclear elements on the screen?</td><td align="left" valign="top">Yes/No</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">If yes, please specify.</td><td align="left" valign="top">Short answer</td></tr><tr><td align="left" valign="top" colspan="4">Ease of operation (N-2)</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Is this function easy to use?</td><td align="left" valign="top">Yes/No</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">If not, please explain why.</td><td align="left" valign="top">Short answer</td></tr><tr><td align="left" valign="top" colspan="4">Acceptability (N-3)</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Do you like this function?</td><td align="left" valign="top">Yes/No</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Tell us what you like about this function?</td><td align="left" valign="top">Short answer</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">If you dislike this function, how can we improve?</td><td align="left" valign="top">Short answer</td></tr><tr><td align="left" valign="top" colspan="4">Intention to continue usage (N-4)</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Will you keep using this function?</td><td align="left" valign="top">Yes/No</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Why or why not?</td><td align="left" valign="top">Short answer</td></tr><tr><td align="left" valign="top" colspan="4">Satisfaction (N-5)</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Please rate your satisfaction with this function on a scale from 1 to 5.</td><td align="left" valign="top">5-Point Scale</td></tr><tr><td align="left" valign="top" colspan="4">Previous experience (7-1)</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Have you ever used any other apps or websites for managing chronic kidney disease?</td><td align="left" valign="top">Yes/No</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">If yes, what did you like or dislike about them?</td><td align="left" valign="top">Short answer</td></tr><tr><td align="left" valign="top" colspan="4">General platform satisfaction (7-2)</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">What is your overall satisfaction rating with our platform?</td><td align="left" valign="top">5-Point Scale</td></tr><tr><td align="left" valign="top" colspan="2"/><td align="left" valign="top">Will you continue to use our platform for chronic kidney disease management?</td><td align="left" valign="top">Yes/No</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Items N-1 to N-5 are inquired repeatedly for each of the 6 functions of the platform, resulting in a total of 30 questions. Items 7&#x2010;1 and 7&#x2010;2 are general questions asked once, adding 2 more questions. Therefore, the total number of questions in this form is 32.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s2-3"><title>Phase 2: Heuristic Evaluation</title><p>To further examine whether our digital platform is user-friendly in its design, a heuristic evaluation involving 5 evaluators with backgrounds in health care or information engineering was conducted. Evaluators tried out the digital platform and assessed how well each of the 6 major functions in the interface design complies with Nielsen&#x2019;s 10 usability principles (10 usability heuristics) [<xref ref-type="bibr" rid="ref26">26</xref>].</p><p>The team referred to Moran and Gordon&#x2019;s [<xref ref-type="bibr" rid="ref27">27</xref>] suggested heuristic evaluation steps and designed an evaluation form based on their published <italic>Heuristic Evaluation Handbook</italic>. Considering that the digital platform&#x2019;s access is not limited by time or space and acknowledging the need for evaluators to independently conduct the evaluation, the team opted for evaluators to fill out Google Forms for remote participation.</p><p>The form begins by inviting evaluators to join our digital platform on LINE and set up the initial settings. Evaluators were then asked to use the platform for 3 days. Specifically, they explored the buttons&#x2019; functionalities and information on the LINE OA service menu and the extended app, similar to the real-use scenarios in phase 1 dyadic trial use. Before starting the evaluation, evaluators are invited to visit relevant websites to familiarize themselves with the content of Nielsen&#x2019;s 10 usability heuristics [<xref ref-type="bibr" rid="ref28">28</xref>]. The explanations and the assessment questions for each principle are shown in <xref ref-type="table" rid="table2">Table 2</xref>.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Explanation of 10 usability heuristics and assessment questions<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup>.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Heuristic</td><td align="left" valign="bottom">Explanation</td><td align="left" valign="bottom">Assessment questions</td></tr></thead><tbody><tr><td align="left" valign="top">Principle 1:<break/>Visibility of System Status</td><td align="left" valign="top">The design should always keep users informed about what is going on through appropriate feedback within a reasonable amount of time.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Does the design clearly communicate its state?</p></list-item><list-item><p>Is feedback presented quickly after user actions?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 2:<break/>Match Between System and the Real World</td><td align="left" valign="top">The design should speak the users&#x2019; language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Will the user be familiar with the terminology used in the design?</p></list-item><list-item><p>Do the design&#x2019;s controls follow real-world conventions?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 3:<break/>User Control and Freedom</td><td align="left" valign="top">Users often perform actions by mistake. They need a clearly marked &#x201C;emergency exit&#x201D; to leave the unwanted action without having to go through an extended process.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Does the design allow users to go back a step in the process?</p></list-item><list-item><p>Are exit links easily discoverable?</p></list-item><list-item><p>Can users easily cancel an action?</p></list-item><list-item><p>Is <italic>Undo</italic> and <italic>Redo</italic> supported?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 4:<break/>Consistency and Standards</td><td align="left" valign="top">Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Does the design follow industry conventions?</p></list-item><list-item><p>Are visual treatments used consistently throughout the design?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 5:<break/>Error Prevention</td><td align="left" valign="top">Good error messages are important, but the best designs carefully prevent problems from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Does the design prevent slips by using helpful constraints?</p></list-item><list-item><p>Does the design warn users before they perform risky actions?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 6:<break/>Recognition Rather Than Recall</td><td align="left" valign="top">Minimize the user&#x2019;s memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (eg, field labels<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup> or menu items) should be visible or easily retrievable when needed.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Does the design keep important information visible, so that users do not have to memorize it?</p></list-item><list-item><p>Does the design offer help in context?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 7:<break/>Flexibility and Efficiency of Use</td><td align="left" valign="top">Shortcuts&#x2014;hidden from novice users&#x2014;may speed up the interaction for the expert user such that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Does the design provide accelerators such as keyboard shortcuts and touch gestures?</p></list-item><list-item><p>Is content and functionality personalized or customized for individual users?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 8:<break/>Esthetic and Minimalist Design</td><td align="left" valign="top">Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Is the visual design and content focused on the essentials?</p></list-item><list-item><p>Have all distracting, unnecessary elements been removed?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 9:<break/>Help Users Recognize, Diagnose, and Recover From Errors</td><td align="left" valign="top">Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Does the design use traditional error message visuals, such as bold, red text?</p></list-item><list-item><p>Does the design offer a solution that solves the error immediately?</p></list-item></list></td></tr><tr><td align="left" valign="top">Principle 10:<break/>Help and Documentation</td><td align="left" valign="top">It is best if the system does not need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Is help documentation easy to search?</p></list-item><list-item><p>Is help provided in context right at the moment when the user requires it?</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>Adapted from the &#x201C;<italic>Heuristic Evaluation Workbook</italic>,&#x201D; by K. Moran &#x0026; K. Gordon, 2023, Nielsen Norman Group.</p></fn><fn id="table2fn2"><p><sup>b</sup>Field labels are commonly used in forms to provide context for information input.</p></fn></table-wrap-foot></table-wrap><p>Consistent with Donald et al [<xref ref-type="bibr" rid="ref29">29</xref>], the evaluators assessed the degree to which each of the 6 major functions from our digital platform complies with the 10 usability principles. They gave ratings of &#x201C;&#x2212;1 (does not comply),&#x201D; &#x201C;0 (partially complies),&#x201D; or &#x201C;1 (complies).&#x201D; If an item scores &#x201C;does not comply&#x201D; or &#x201C;partially complies&#x201D; with a principle, the evaluator will be asked to note specific issues in not adhering to that principle and provide suggestions for fixing these problems. If the evaluator finds that the assessed principle does not apply to a specific function, they can select &#x201C;N/A (not applicable).&#x201D;</p></sec><sec id="s2-4"><title>Phase 3: Usability Testing</title><p>Usability testing involves observing how users interact with the platform to fulfill their needs; understanding their behaviors, preferences, operational strategies, and paths; and collecting feedback to identify existing interface problems and possibilities for improvement.</p><p>We designed a task for each of the 6 major functions of our digital platform, which a realistic user would typically use in their daily lives. Five dyads who participated in phase 1, with at least 1 month of experience using the platform, were invited to perform the designed tasks. As the DDEF emphasizes helping relationships, tasks were performed jointly by the dyads, with each assisting the other throughout the process. Researchers provided instructions on task execution and responded to participant queries but refrained from providing guidance to avoid influencing their behavior. Task design and testing followed usability testing guidelines from Moran [<xref ref-type="bibr" rid="ref30">30</xref>] and Nielsen [<xref ref-type="bibr" rid="ref31">31</xref>]. Task success, time spent, and the number of operational errors during execution were recorded for each task.</p><p>Upon completion of each task, whether successful or not, participants filled out a postscenario questionnaire (After-Scenario Questionnaire [ASQ]) consisting of three questions to assess the perceived (1) ease of the task, (2) time required, and (3) support received during execution (help from the manual) on a scale from 1 to 7 [<xref ref-type="bibr" rid="ref32">32</xref>]. A higher average ASQ score indicates greater user satisfaction and perceived usability. After completing all tasks, participants also filled out the System Usability Scale (SUS), a 10-item questionnaire designed to evaluate the overall usability and learnability of the digital platform [<xref ref-type="bibr" rid="ref33">33</xref>]. A SUS score ranges from 0 to 100, with 68 indicating marginally acceptable perceived usability by the user and suggesting the existence of areas for improvement [<xref ref-type="bibr" rid="ref34">34</xref>]. See <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> for the full usability testing instrument. The task scenario and instruction for each of the 6 functions are shown in <xref ref-type="table" rid="table3">Table 3</xref>.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Usability testing task scenarios and instructions for tested functions.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Task scenario</td><td align="left" valign="bottom">Instruction</td><td align="left" valign="bottom">Tested function</td></tr></thead><tbody><tr><td align="left" valign="top">Task 1: Here are the values of your blood pressure and blood test results from today&#x2019;s visit: systolic blood pressure 125, diastolic blood pressure 78, heart rate 65, and creatinine (CREA) 1.4 mg/dL.</td><td align="left" valign="top">Please attempt to log the above values into our digital platform.</td><td align="left" valign="top">Record Values</td></tr><tr><td align="left" valign="top">Task 2: You want to know which stage of chronic kidney disease you are currently in. However, you found that your recent blood test report does not provide your &#x201C;estimated glomerular filtration rate (eGFR)&#x201D; value. You need to calculate your eGFR using &#x201C;Creatinine (CREA)&#x201D; (1.4 mg/dL), combined with your &#x201C;gender&#x201D; and &#x201C;age.&#x201D;</td><td align="left" valign="top">Please try to explore our digital platform and calculate your eGFR.</td><td align="left" valign="top">Health Education Information</td></tr><tr><td align="left" valign="top">Task 3: Here is the date and time of your next appointment: December 28, 2023, afternoon clinic; suggested check-in time 14:10.</td><td align="left" valign="top">Please update the above information on our digital platform and notify the researchers through the platform.</td><td align="left" valign="top">Reminder Settings</td></tr><tr><td align="left" valign="top">Task 4: You want to learn about the symptoms of &#x201C;hypoglycemia.&#x201D;</td><td align="left" valign="top">Please try to explore our digital platform and find the 7 possible symptoms of hypoglycemia.</td><td align="left" valign="top">Inquiry &#x0026; Consultation</td></tr><tr><td align="left" valign="top">Task 5: Here is the content of your most recent meal: Half a bowl of white rice, 2 servings of bok choy, and 1 serving of chicken thigh.</td><td align="left" valign="top">Please record the above dietary information on our digital platform via photo or text note.</td><td align="left" valign="top">Kidney Health Mission</td></tr><tr><td align="left" valign="top">Task 6: Your partner (family member) has been trying hard to adjust their lifestyle recently. You want to know some ways to support their change.</td><td align="left" valign="top">Please try to explore our digital platform and write out support strategies corresponding to the following specific behaviors.</td><td align="left" valign="top">Kidney Support Teammate</td></tr></tbody></table></table-wrap></sec><sec id="s2-5"><title>Data Analysis</title><p>Data were compiled and analyzed using Google Sheets. Categorical variables (eg, user responses in feedback forms) were summarized as frequencies and percentages. Continuous variables, such as ASQ and SUS scores, were reported using means and ranges. Task success rates, completion times, and error frequencies were recorded and descriptively summarized for each usability task. No inferential statistical analyses were conducted, as the study primarily aimed to assess usability outcomes through descriptive measures.</p></sec><sec id="s2-6"><title>Ethical Considerations</title><p>This study received approval from the institutional review board of National Cheng Kung University Hospital, Tainan, Taiwan (institutional review board no. B-ER-110-110). All participants were fully informed about the study&#x2019;s purpose, procedures, their rights, and data protection measures. Participation was voluntary, and participants could withdraw at any time without consequence. Paper source data were collected and stored in locked cabinets on site at the institution. Deidentified research data were stored on the institution&#x2019;s cloud servers and on password-protected personal computers, with access restricted to authorized study personnel only. All data will be retained until 2029 and then securely destroyed. Each participant received a signed copy of the informed consent form. Participants received a gift voucher of NT $200 (approximately US $6) as compensation each time they completed a study task.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Phase 1: Iterative Development and Trial Use</title><p>After collaborating with health care providers and technical partners for 3 months to develop our digital platform for intervention, we officially launched the prototype on July 25, 2023. Our LINE OA, named &#x201C;Kidney Lifestyle,&#x201D; can be accessed by searching for LINE ID: @509kgajt. In addition, the extended app, named &#x201C;Kidney Lifestyle App,&#x201D; is currently available through a dedicated link.</p><sec id="s3-1-1"><title>LINE OA &#x201C;Kidney Lifestyle&#x201D; With API Plug-Ins</title><p>Our LINE OA acts as the main hub for real-time interaction with users via text or voice chat. Moreover, by clicking buttons from the service menu (<xref ref-type="fig" rid="figure2">Figure 2A</xref>), users can access various resources for CKD management, retrieved or adapted from the official websites of <italic>Taiwan Society of Nephrology</italic> and <italic>Taiwan Kidney Foundation</italic>. The eight buttons featured on the service menu were introduced: (1) Health Education Information: providing basic kidney disease knowledge, evaluating kidney function, dietary and exercise guidelines, and so on (<xref ref-type="fig" rid="figure2">Figure 2B</xref>). (2) Kidney Support Teammate: multipage messages providing support resources for caregivers (SOs) (<xref ref-type="fig" rid="figure2">Figure 2C</xref>). (3) Frailty Section: providing health education information about frailty prevention and intervention. (4) Latest News: linking to the LINE OA&#x2019;s post area, forwarding information about relevant hospital events. (5) Record Values: users can log self-measured physiological values, and the system records and generates reports for feedback. (6) Reminder Settings: users can log their next appointment dates, and reminders are scheduled through the AlleyPin Interactive backend. (7) Kidney Health Mission: encouraging daily completion of &#x201C;Record Values&#x201D; and &#x201C;Kidney Health Diary&#x201D; (recording daily diet, medication, and physical activity). (8) Inquiry &#x0026; Consultation: providing answers to frequently asked questions for CKD management; a consultation channel is provided for further queries (<xref ref-type="fig" rid="figure2">Figure 2D</xref>).</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Interfaces of the LINE Official Account &#x201C;Kidney Lifestyle&#x201D; with a demonstration of user making inquiry about CKD management via automatic reply messages. The QR code provides access to &#x201C;Kidney Lifestyle.&#x201D; (A) Basic Interface, (B) Health Education Information, (C) Kidney Support Teammate, and (D) Inquiry &#x0026; Consultation. CKD: chronic kidney disease; FAQs: frequently asked questions; SO: significant other.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e73935_fig02.png"/></fig></sec><sec id="s3-1-2"><title>The Extended App &#x201C;Kidney Lifestyle App&#x201D; (AppSheet)</title><p>Our extended app mainly interconnects with the functions of &#x201C;Record Values,&#x201D; &#x201C;Reminder Settings,&#x201D; and &#x201C;Kidney Health Mission&#x201D; provided by our LINE OA with API plug-ins. Users can directly access the corresponding pages of the extended app by clicking on LINE OA service menu buttons, with the specific paths as follows: (1) Clicking &#x201C;Record Values&#x201D; on LINE OA service menu jumps to the &#x201C;New Entry&#x201D; page of the extended app, where users can log blood pressure, heart rate, and weight, and optionally enter blood sugar or blood test report data (<xref ref-type="fig" rid="figure3">Figure 3A</xref>). (2) Clicking &#x201C;Reminder Settings&#x201D; &#x2192; &#x201C;Go to Reminder Setting Page&#x201D; on LINE OA service menu jumps to the extended app to view the next appointment date and time, which users can update manually (<xref ref-type="fig" rid="figure3">Figure 3B</xref>). (3) Clicking &#x201C;Kidney Health Mission&#x201D; on LINE OA service menu allows users to perform 2 &#x201C;Daily Tasks,&#x201D; jump to the extended app to log physiological values or write a kidney health diary (recording daily diet, medication, and physical activity) (<xref ref-type="fig" rid="figure3">Figure 3C1</xref>). Alternatively, they can click &#x201C;Challenge Missions&#x201D; &#x2192; &#x201C;View Title Challenge Progress&#x201D; on the extended app to confirm task execution status (<xref ref-type="fig" rid="figure3">Figure 3C2</xref>).</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Interfaces of the extended app &#x201C;Kidney Lifestyle App&#x201D; and their connections with the LINE Official Account &#x201C;Kidney Lifestyle&#x201D; service menu. (A) The entry form of &#x201C;Recording Values&#x201D; and the chart viewing for self-measured physiological values, (B)&#x201C;Reminder Settings&#x201D; interface, and (C)&#x201C;Kidney Health Mission,&#x201D; directing to (C1) Kidney Health Diary, records of daily diet, medication, and physical activity, and to (C2) Usage Report, presenting daily tasks execution status and progress.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e73935_fig03.png"/></fig><p>In addition to the functionality accessible via LINE, the extended app interface also has a bottom-placed menu with five buttons (<xref ref-type="fig" rid="figure3">Figure 3</xref>), each briefly described as follows: (1) My Entries: viewing the &#x201C;Usage Report&#x201D; (the page redirected after clicking &#x201C;View Title Challenge Progress&#x201D; on LINE), &#x201C;Physiological Value View,&#x201D; and &#x201C;Blood Test Record&#x201D; to check entered values. (2) Chart View: visualizing self-entered physiological values in graphical form. (3) New Entry: same as clicking &#x201C;Record Values&#x201D; on LINE OA. (4) Kidney Health Diary: adding, viewing, or editing written kidney health diaries. (5) Reminder Settings: same as clicking &#x201C;Go to Reminder Setting Page&#x201D; on LINE OA.</p><p>The data entered by users on various pages of the extended app were synchronized with their device IDs and sent back to the corresponding Google Sheets worksheets. Through these worksheets, the team can view all user-entered data and identify them based on the device ID and a custom user identification code. Subsequently, security filters were set up, distinguishing by device ID, enabling individual users on the front end (ie, extended app interfaces) to access only their entered data.</p><p>With the completion of the extended app&#x2019;s development and integration with the LINE OA, it can now fully use the &#x201C;Digital Monitoring&#x201D; strategy to allow both the research team and the users to track physiological values, daily diet, medication, and physical activity. For the application of the &#x201C;Digital Analysis&#x201D; strategy, we calculate user metrics such as accumulated entry counts, entry activity rates (EARs), and consecutive entry days. These serve as reference indicators for users&#x2019; lifestyle modification progress, enabling personalized interventions through the LINE OA.</p></sec><sec id="s3-1-3"><title>Interventions to Promote Platform Use</title><p>Referring to the DDEF, interventions delivered through our integrated digital platform were designed and finalized through the following three processes:</p><list list-type="order"><list-item><p>Defined 4 specific lifestyle modification behaviors: physiological values monitoring, healthy diet, adequate physical activity, and proper medication.</p></list-item><list-item><p>Designed 2 daily tasks on the digital platform to execute these four specific behaviors:</p><list list-type="bullet"><list-item><p>Record Physiological Values: measure physiological values and log them through &#x201C;Record Values&#x201D; (multiple times allowed).</p></list-item><list-item><p>Write Kidney Health Diary: record daily diet (photographs or textual notes); check whether medication was taken correctly and, if not, select a reason; and check whether physical activity for more than 30 minutes was done and record the number of steps taken.</p></list-item></list></list-item></list><p>After consulting health care providers and observing practical scenarios, we confirmed the benefits of regular execution of the 2 daily tasks for both patients and health care providers. Recording physiological values generates easily readable reports, facilitating quick understanding of trends in physiological value changes. Writing a kidney health diary allows health care providers to confirm whether the patient&#x2019;s meals align with the principles of a CKD diet, and it serves as a reminder for the patient to engage in physical activity and take medication correctly. Inappropriate medication check items reference the Chronic Kidney Disease Self-Care Scale [<xref ref-type="bibr" rid="ref35">35</xref>] and the Elderly Medication Adherence Assessment [<xref ref-type="bibr" rid="ref36">36</xref>], consolidated into 4 items: &#x201C;missed medication,&#x201D; &#x201C;not taking medication on time,&#x201D; &#x201C;self-adjusted medication or dosage changes,&#x201D; and &#x201C;using nonprescribed medication.&#x201D;</p><list list-type="order" prefix-word="3"><list-item><p>Designed strategies to promote the execution of daily tasks based on the principles of behavior change and processes of change listed in the DDEF, including:</p><list list-type="bullet"><list-item><p>Gamification Mode for Behavior Shaping: Different &#x201C;Kidney Health Titles&#x201D; are granted upon completing 2 daily tasks consecutively for 3 (<italic>novice</italic>), 7 (<italic>intermediate</italic>), 14 (<italic>veteran</italic>), 30 (<italic>master</italic>), and 60 (<italic>grandmaster</italic>) days. Users can view title challenge progress (in percentage) through the &#x201C;Usage Report&#x201D; page on the extended app.</p></list-item></list></list-item></list><p>To implement the gamification strategy, the team needed to calculate the number of consecutive days a user completed daily tasks from today backward. With the assistance of generative artificial intelligence, ChatGPT, for syntax writing, we used Google Apps Script to execute custom functions to solve this issue. Furthermore, the team further simulated data using RStudio (Posit Software, PBC) and attempted to interpret it using Item Response Theory to link the 2 indicators, &#x201C;consecutive days&#x201D; and &#x201C;entry activity rate.&#x201D; The calculation method for the EAR is as follows:</p><disp-formula id="equWL1"><mml:math id="eqn1"><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mtext>Entry activity rate</mml:mtext><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mrow><mml:mi mathvariant="normal">D</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">a</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">s</mml:mi></mml:mrow><mml:mrow><mml:mtext>&#x00A0;</mml:mtext></mml:mrow><mml:mrow><mml:mi mathvariant="normal">p</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">e</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">r</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">f</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">o</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">r</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">m</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">n</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">g</mml:mi></mml:mrow><mml:mrow><mml:mtext>&#x00A0;</mml:mtext></mml:mrow><mml:mrow><mml:mi mathvariant="normal">d</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">a</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">l</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow><mml:mrow><mml:mtext>&#x00A0;</mml:mtext></mml:mrow><mml:mrow><mml:mi mathvariant="normal">t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">a</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">s</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">k</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">s</mml:mi></mml:mrow></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">T</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">o</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">a</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">l</mml:mi></mml:mrow><mml:mrow><mml:mtext>&#x00A0;</mml:mtext></mml:mrow><mml:mrow><mml:mi mathvariant="normal">o</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">b</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">s</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">e</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">r</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">v</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">a</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">o</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">n</mml:mi></mml:mrow><mml:mrow><mml:mtext>&#x00A0;</mml:mtext></mml:mrow><mml:mrow><mml:mi mathvariant="normal">d</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">a</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">s</mml:mi></mml:mrow></mml:mrow></mml:mfrac><mml:mo>&#x00D7;</mml:mo><mml:mn>100</mml:mn><mml:mrow><mml:mi mathvariant="normal">%</mml:mi></mml:mrow></mml:mstyle></mml:mrow></mml:mstyle></mml:math></disp-formula><p>The EAR can be viewed as an &#x201C;ability&#x201D; indicator for users performing daily tasks. A higher EAR indicates a more regular execution of daily tasks. The team simulated different levels of EARs (from 0% to 100%, at intervals of 5%) for 180 observation days, with or without task execution, a total of 10,000 times. The frequency of achieving various Kidney Health Titles was calculated among these 10,000 simulations (<xref ref-type="table" rid="table4">Table 4</xref>).</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Occurrences of achieving different titles within 180 days based on various entry activity rates (simulation counts=10,000)<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup><sup>,</sup><sup><xref ref-type="table-fn" rid="table4fn2">b</xref></sup>.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">EAR<sup><xref ref-type="table-fn" rid="table4fn3">c</xref></sup>, %</td><td align="left" valign="bottom">Novice<break/>achieving counts</td><td align="left" valign="bottom">Intermediate<break/>achieving counts</td><td align="left" valign="bottom">Veteran<break/>achieving counts</td><td align="left" valign="bottom">Master<break/>achieving counts</td><td align="left" valign="bottom">Grandmaster<break/>achieving counts</td></tr></thead><tbody><tr><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">211</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">10</td><td align="left" valign="top">1507</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">15</td><td align="left" valign="top">4040</td><td align="left" valign="top">1</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">20</td><td align="left" valign="top">6839</td><td align="left" valign="top">13</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">25</td><td align="left" valign="top">8873</td><td align="left" valign="top">64</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">30</td><td align="left" valign="top">9723</td><td align="left" valign="top">248</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">35</td><td align="left" valign="top">9954</td><td align="left" valign="top">698</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">40</td><td align="left" valign="top">9996</td><td align="left" valign="top">1590</td><td align="left" valign="top">2</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">45</td><td align="left" valign="top">10,000</td><td align="left" valign="top">2999</td><td align="left" valign="top">13</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">50</td><td align="left" valign="top">10,000</td><td align="left" valign="top">5003</td><td align="left" valign="top">48</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">55</td><td align="left" valign="top">10,000</td><td align="left" valign="top">7191</td><td align="left" valign="top">192</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">60</td><td align="left" valign="top">10,000</td><td align="left" valign="top">8852</td><td align="left" valign="top">502</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">65</td><td align="left" valign="top">10,000</td><td align="left" valign="top">9712</td><td align="left" valign="top">1275</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">70</td><td align="left" valign="top">10,000</td><td align="left" valign="top">9964</td><td align="left" valign="top">3001</td><td align="left" valign="top">17</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">75</td><td align="left" valign="top">10,000</td><td align="left" valign="top">9999</td><td align="left" valign="top">5629</td><td align="left" valign="top">82</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">80</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td><td align="left" valign="top">8179</td><td align="left" valign="top">355</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top">85</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td><td align="left" valign="top">9746</td><td align="left" valign="top">1699</td><td align="left" valign="top">12</td></tr><tr><td align="left" valign="top">90</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td><td align="left" valign="top">9994</td><td align="left" valign="top">5394</td><td align="left" valign="top">250</td></tr><tr><td align="left" valign="top">95</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td><td align="left" valign="top">9541</td><td align="left" valign="top">3119</td></tr><tr><td align="left" valign="top">100</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td><td align="left" valign="top">10,000</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>EAR= (Number of days executing daily tasks/Total observation days) &#x00D7;100%.</p></fn><fn id="table4fn2"><p><sup>b</sup>Continuous execution days for each title: Kidney Health Novice&#x2014;3 days; Kidney Health Intermediate&#x2014;7 days; Kidney Health Veteran&#x2014;14 days; Kidney Health Master&#x2014;30 days; and Kidney Health Grandmaster&#x2014;60 days.</p></fn><fn id="table4fn3"><p><sup>c</sup>EAR: entry activity rate.</p></fn></table-wrap-foot></table-wrap><p>The simulation results provided item characteristic curve for each Kidney Health Title (<xref ref-type="fig" rid="figure4">Figure 4</xref>). These curves suggested that higher ability to perform daily tasks (indicated by a higher EAR) leads to a higher chance of achieving specific titles (indicated by more achievement instances). Using 5000 times of achievement as a baseline, its corresponding EAR on the item characteristic curve represents the difficulty level in achieving that specific Kidney Health Title. These results provide adequate rationality for the gamification strategy: assuming users in different stages of change have different EARs, this strategy sets appropriate challenges accordingly, aligning with our aim of providing corresponding interventions based on CKD dyads&#x2019; different motivational states.</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Item characteristic curves (ICCs) of achieving various kidney health titles within 180 days (simulation counts=10,000). According to Item Response Theory, with an achievement rate of 50% (ie, achieving 5000 times out of 10,000), the entry activity rate (EAR) corresponding to the ICC indicates the difficulty level to achieve that title. This simulation demonstrated the relationship between consecutively completing daily tasks for N days and its corresponding ability level, indicated by EAR. EAR = (Number of days executing daily tasks/Total observation days) &#x00D7; 100%. Continuous execution days for each title: Kidney Health Novice&#x2014;3 days; Kidney Health Intermediate&#x2014;7 days; Kidney Health Veteran&#x2014;14 days; Kidney Health Master&#x2014;30 days; and Kidney Health Grandmaster&#x2014;60 days.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e73935_fig04.png"/></fig><list list-type="bullet" prefix-word="2"><list-item><p>Reinforcement management: Upon completing 2 daily tasks, users receive encouragement messages through the LINE OA; when obtaining a Kidney Health Title, the team sends encouragement messages and title certificates via LINE and informs their SOs. It also informs the patient&#x2019;s physician to provide face-to-face encouragement during the next visit (providing social reinforcement).</p></list-item><list-item><p>Nudging through helping relationships: If a patient cannot complete tasks independently, the SO assists in recording. For patients in the early stages of change (eg, EAR below 50%) or those who have not performed tasks for more than 2 days, the system schedules LINE reminders via AlleyPin Interactive&#x2019;s case tracking system or notifies SOs to assist in reminders. References are drawn from the resources in &#x201C;Kidney Support Teammate,&#x201D; providing assistance based on the patient&#x2019;s lifestyle context.</p></list-item></list></sec><sec id="s3-1-4"><title>Platform Trial Use to Optimize the Platform</title><p>After the initial prototype of our digital platform went live, 10 CKD dyads visiting nephrology clinics regularly at a university hospital were invited to participate in the trial use from August to October 2023. One of the SOs (no. 003S) was invited by the patient but did not decide to participate in the end, resulting in a total of 19 participants. All dyads completed the user feedback form and returned it during the next visit. <xref ref-type="table" rid="table5">Table 5</xref> shows the basic demographics of the participants. The following sections separately analyzed (1) the LINE message activity, (2) usage of the extended app, and (3) dyadic feedback content.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Basic information of participants in phase 1 platform trial use (n=19).</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">ID<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup></td><td align="left" valign="bottom">Sex</td><td align="left" valign="bottom">Age (years)</td><td align="left" valign="bottom">Education</td><td align="left" valign="bottom">Relations</td><td align="left" valign="bottom">Stage of change</td><td align="left" valign="bottom">Primary user<sup><xref ref-type="table-fn" rid="table5fn2">b</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top" colspan="4">001P and 001S</td><td align="left" valign="top">Spouse</td><td align="left" valign="top">Maintenance</td><td align="left" valign="top">P</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>001P</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">67</td><td align="left" valign="top">College</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>001S</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">59</td><td align="left" valign="top">Junior college</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">002P and 002S</td><td align="left" valign="top">Spouse</td><td align="left" valign="top">Maintenance</td><td align="left" valign="top">P</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>002P</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">63</td><td align="left" valign="top">College</td><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content></td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>002S</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">62</td><td align="left" valign="top">Senior high</td><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content></td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">003P and 003S</td><td align="left" valign="top">N/A</td><td align="left" valign="top">Preparation</td><td align="left" valign="top">P</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>003P</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">64</td><td align="left" valign="top">College</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>003S<sup><xref ref-type="table-fn" rid="table5fn3">c</xref></sup></td><td align="left" valign="top">N/A<sup><xref ref-type="table-fn" rid="table5fn4">d</xref></sup></td><td align="left" valign="top">N/A</td><td align="left" valign="top">N/A</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">004P and 004S</td><td align="left" valign="top">Mother-son</td><td align="left" valign="top">Maintenance</td><td align="left" valign="top">S</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>004P</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">81</td><td align="left" valign="top">Elementary</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>004S</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">53</td><td align="left" valign="top">College</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">005P and 005S</td><td align="left" valign="top">Father-son</td><td align="left" valign="top">Maintenance</td><td align="left" valign="top">S</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>005P</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">82</td><td align="left" valign="top">Illiterate</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>005S</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">56</td><td align="left" valign="top">Junior college</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">006P and 006S</td><td align="left" valign="top">Mother-daughter</td><td align="left" valign="top">Preparation</td><td align="left" valign="top">P</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>006P</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">37</td><td align="left" valign="top">College</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>006S</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">73</td><td align="left" valign="top">Junior college</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">007P and 007S</td><td align="left" valign="top">Spouse</td><td align="left" valign="top">Maintenance</td><td align="left" valign="top">P</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>007P</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">64</td><td align="left" valign="top">Junior high</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>007S</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">59</td><td align="left" valign="top">Elementary</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">008P and 008S</td><td align="left" valign="top">Spouse</td><td align="left" valign="top">Contemplation</td><td align="left" valign="top">P</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>008P</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">67</td><td align="left" valign="top">Junior college</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>008S</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">68</td><td align="left" valign="top">Junior high</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">009P and 009S</td><td align="left" valign="top">Spouse</td><td align="left" valign="top">Action</td><td align="left" valign="top">P</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>009P</td><td align="left" valign="top">Male</td><td align="char" char="." valign="top">52</td><td align="left" valign="top">College</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>009S</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">51</td><td align="left" valign="top">College</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top" colspan="4">010P and 010S</td><td align="left" valign="top">Mother-daughter</td><td align="left" valign="top">Maintenance</td><td align="left" valign="top">P</td></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>010P</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">70</td><td align="left" valign="top">Senior high</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="char" char="." valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>010S</td><td align="left" valign="top">Female</td><td align="char" char="." valign="top">42</td><td align="left" valign="top">Junior college</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>ID marked with P denotes patients; S denotes significant others.</p></fn><fn id="table5fn2"><p><sup>b</sup>Primary user refers to the one using the app for daily tasks, primarily patients.</p></fn><fn id="table5fn3"><p><sup>c</sup>003S was invited by 003P to participate in the study but eventually chose not to.</p></fn><fn id="table5fn4"><p><sup>d</sup>N/A: not applicable.</p></fn></table-wrap-foot></table-wrap><sec id="s3-1-4-1"><title>LINE Message Activity</title><p>Based on data from the LINE OA backend, a total of 849 messages were sent during the initial 28 days (October 30 to November 26, 2023) after participant recruitment completion (as shown in <xref ref-type="table" rid="table6">Table 6</xref>), averaging approximately 30 messages per day. This indicates continuous interaction and usage.</p><table-wrap id="t6" position="float"><label>Table 6.</label><caption><p>Number of messages sent via LINE Official Account and application programming interface module in the initial 28 days after participant recruitment completion<sup><xref ref-type="table-fn" rid="table6fn1">a</xref></sup>.</p></caption><table id="table6" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" rowspan="2">Date</td><td align="left" valign="bottom" colspan="3">LINE Official Account</td><td align="left" valign="bottom" colspan="2">API<sup><xref ref-type="table-fn" rid="table6fn2">b</xref></sup> module</td><td align="left" valign="bottom" rowspan="2">Daily total</td></tr><tr><td align="left" valign="bottom">Auto Response</td><td align="left" valign="bottom">Welcome</td><td align="left" valign="bottom">Manual Chat</td><td align="left" valign="bottom">Push<sup><xref ref-type="table-fn" rid="table6fn3">c</xref></sup></td><td align="left" valign="bottom">Reply<sup><xref ref-type="table-fn" rid="table6fn4">d</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">10/30</td><td align="left" valign="top">1</td><td align="left" valign="top">5</td><td align="left" valign="top">2</td><td align="left" valign="top">12</td><td align="left" valign="top">55</td><td align="left" valign="top">75</td></tr><tr><td align="left" valign="top">10/31</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">4</td><td align="left" valign="top">20</td><td align="left" valign="top">24</td></tr><tr><td align="left" valign="top">11/1</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">0</td><td align="left" valign="top">15</td><td align="left" valign="top">22</td><td align="left" valign="top">38</td></tr><tr><td align="left" valign="top">11/2</td><td align="left" valign="top">0</td><td align="left" valign="top">3</td><td align="left" valign="top">6</td><td align="left" valign="top">17</td><td align="left" valign="top">46</td><td align="left" valign="top">72</td></tr><tr><td align="left" valign="top">11/3</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">7</td><td align="left" valign="top">13</td><td align="left" valign="top">17</td><td align="left" valign="top">37</td></tr><tr><td align="left" valign="top">11/4</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">4</td><td align="left" valign="top">11</td><td align="left" valign="top">6</td><td align="left" valign="top">21</td></tr><tr><td align="left" valign="top">11/5</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">0</td><td align="left" valign="top">9</td><td align="left" valign="top">11</td><td align="left" valign="top">21</td></tr><tr><td align="left" valign="top">11/6</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">12</td><td align="left" valign="top">22</td><td align="left" valign="top">34</td></tr><tr><td align="left" valign="top">11/7</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">11</td><td align="left" valign="top">2</td><td align="left" valign="top">14</td></tr><tr><td align="left" valign="top">11/8</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">1</td><td align="left" valign="top">18</td><td align="left" valign="top">11</td><td align="left" valign="top">31</td></tr><tr><td align="left" valign="top">11/9</td><td align="left" valign="top">0</td><td align="left" valign="top">2</td><td align="left" valign="top">2</td><td align="left" valign="top">15</td><td align="left" valign="top">13</td><td align="left" valign="top">32</td></tr><tr><td align="left" valign="top">11/10</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">2</td><td align="left" valign="top">11</td><td align="left" valign="top">13</td><td align="left" valign="top">26</td></tr><tr><td align="left" valign="top">11/11</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">9</td><td align="left" valign="top">14</td><td align="left" valign="top">23</td></tr><tr><td align="left" valign="top">11/12</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">11</td><td align="left" valign="top">17</td><td align="left" valign="top">29</td></tr><tr><td align="left" valign="top">11/13</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">9</td><td align="left" valign="top">8</td><td align="left" valign="top">18</td></tr><tr><td align="left" valign="top">11/14</td><td align="left" valign="top">0</td><td align="left" valign="top">2</td><td align="left" valign="top">3</td><td align="left" valign="top">18</td><td align="left" valign="top">16</td><td align="left" valign="top">39</td></tr><tr><td align="left" valign="top">11/15</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">1</td><td align="left" valign="top">15</td><td align="left" valign="top">9</td><td align="left" valign="top">26</td></tr><tr><td align="left" valign="top">11/16</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">3</td><td align="left" valign="top">15</td><td align="left" valign="top">21</td><td align="left" valign="top">40</td></tr><tr><td align="left" valign="top">11/17</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">3</td><td align="left" valign="top">11</td><td align="left" valign="top">19</td><td align="left" valign="top">33</td></tr><tr><td align="left" valign="top">11/18</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">2</td><td align="left" valign="top">11</td><td align="left" valign="top">6</td><td align="left" valign="top">19</td></tr><tr><td align="left" valign="top">11/19</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">9</td><td align="left" valign="top">3</td><td align="left" valign="top">13</td></tr><tr><td align="left" valign="top">11/20</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">2</td><td align="left" valign="top">15</td><td align="left" valign="top">12</td><td align="left" valign="top">29</td></tr><tr><td align="left" valign="top">11/21</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">3</td><td align="left" valign="top">11</td><td align="left" valign="top">12</td><td align="left" valign="top">27</td></tr><tr><td align="left" valign="top">11/22</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">3</td><td align="left" valign="top">18</td><td align="left" valign="top">45</td><td align="left" valign="top">67</td></tr><tr><td align="left" valign="top">11/23</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">10</td><td align="left" valign="top">5</td><td align="left" valign="top">16</td></tr><tr><td align="left" valign="top">11/24</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">1</td><td align="left" valign="top">11</td><td align="left" valign="top">2</td><td align="left" valign="top">15</td></tr><tr><td align="left" valign="top">11/25</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">2</td><td align="left" valign="top">9</td><td align="left" valign="top">5</td><td align="left" valign="top">16</td></tr><tr><td align="left" valign="top">11/26</td><td align="left" valign="top">0</td><td align="left" valign="top">0</td><td align="left" valign="top">1</td><td align="left" valign="top">12</td><td align="left" valign="top">1</td><td align="left" valign="top">14</td></tr><tr><td align="left" valign="top">Total</td><td align="left" valign="top">1</td><td align="left" valign="top">20</td><td align="left" valign="top">53</td><td align="left" valign="top">342</td><td align="left" valign="top">433</td><td align="left" valign="top">849</td></tr></tbody></table><table-wrap-foot><fn id="table6fn1"><p><sup>a</sup>Data obtained from LINE Official Account Manager.</p></fn><fn id="table6fn2"><p><sup>b</sup>API: application programming interface.</p></fn><fn id="table6fn3"><p><sup>c</sup>Push messages sent to remind users of follow-up visits and daily tasks execution.</p></fn><fn id="table6fn4"><p><sup>d</sup>Messages returned when clicking service menu layers or push message buttons.</p></fn></table-wrap-foot></table-wrap><p>Notably, the proportion of messages sent through API plug-in modules is extremely high: there were 342 Push messages, accounting for approximately 40% (342/849) of all messages, used for reminders on returning for checkups or daily task reminders and regular automatic care. There were also 433 Reply messages, constituting around 51% (433/849) of all messages, automatically sent by the system when users clicked buttons in the service menu or Push message prompts. In comparison, manually sent messages amounted to only 53, which is around 6% (53/849) of the total, primarily aimed at assisting users with operational issues or scheduling research-related appointments. These data demonstrate that our LINE OA with API plug-in modules shows a high degree of automation and convenience, allowing remote and real-time intervention, significantly reducing manpower costs, and reserving resources for handling more complex and specific user queries.</p></sec><sec id="s3-1-4-2"><title>Usage of the Extended App</title><p>Upon observing the data on daily task execution by the primary users among the 10 dyads on the extended app (as shown in <xref ref-type="table" rid="table7">Table 7</xref>), since the start of enrollment on August 29, 2023, until 2:30 PM on April 29, 2024, a total of 2402 sets of physiological values have been logged, and 1079 kidney health diaries have been uploaded. Notably, it was found that the average EAR for logging physiological values (63.70%) was higher than that for writing kidney health diaries (50.74%). This difference might be due to the ease of recording physiological values and the immediate feedback obtained through trend chart viewing.</p><table-wrap id="t7" position="float"><label>Table 7.</label><caption><p>Phase 1 primary users&#x2019; usage of extended app for daily tasks (n=10)<sup><xref ref-type="table-fn" rid="table7fn1">a</xref></sup>.</p></caption><table id="table7" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" rowspan="2">ID</td><td align="left" valign="bottom" rowspan="2">Enrollment date<break/>(YY/M/D)</td><td align="left" valign="bottom" rowspan="2">Days</td><td align="left" valign="bottom" colspan="2">Physiological values</td><td align="left" valign="bottom" colspan="2">Kidney health diary</td><td align="left" valign="bottom" rowspan="2">Highest kidney health title<sup><xref ref-type="table-fn" rid="table7fn4">d</xref></sup></td></tr><tr><td align="left" valign="bottom">Counts</td><td align="left" valign="bottom">Activity rate, %<sup><xref ref-type="table-fn" rid="table7fn2">b</xref></sup></td><td align="left" valign="bottom">Counts</td><td align="left" valign="bottom">Activity rate, %<sup><xref ref-type="table-fn" rid="table7fn3">c</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">001P</td><td align="left" valign="top">23/8/29</td><td align="left" valign="top">245</td><td align="left" valign="top">530</td><td align="left" valign="top">95.92</td><td align="left" valign="top">232</td><td align="left" valign="top">94.69</td><td align="left" valign="top">Master</td></tr><tr><td align="left" valign="top">002P</td><td align="left" valign="top">23/9/18</td><td align="left" valign="top">225</td><td align="left" valign="top">438</td><td align="left" valign="top">100.00</td><td align="left" valign="top">209</td><td align="left" valign="top">92.89</td><td align="left" valign="top">Master</td></tr><tr><td align="left" valign="top">003P</td><td align="left" valign="top">23/9/21</td><td align="left" valign="top">222</td><td align="left" valign="top">164</td><td align="left" valign="top">62.61</td><td align="left" valign="top">133</td><td align="left" valign="top">59.91</td><td align="left" valign="top">Intermediate</td></tr><tr><td align="left" valign="top">004S</td><td align="left" valign="top">23/10/2</td><td align="left" valign="top">211</td><td align="left" valign="top">2</td><td align="left" valign="top">0.95</td><td align="left" valign="top">0</td><td align="left" valign="top">0.00</td><td align="left" valign="top">None</td></tr><tr><td align="left" valign="top">005S</td><td align="left" valign="top">23/10/3</td><td align="left" valign="top">210</td><td align="left" valign="top">579</td><td align="left" valign="top">89.52</td><td align="left" valign="top">168</td><td align="left" valign="top">80.00</td><td align="left" valign="top">Master</td></tr><tr><td align="left" valign="top">006P</td><td align="left" valign="top">23/10/17</td><td align="left" valign="top">196</td><td align="left" valign="top">100</td><td align="left" valign="top">51.02</td><td align="left" valign="top">7</td><td align="left" valign="top">3.57</td><td align="left" valign="top">Novice</td></tr><tr><td align="left" valign="top">007P</td><td align="left" valign="top">23/10/19</td><td align="left" valign="top">194</td><td align="left" valign="top">125</td><td align="left" valign="top">63.92</td><td align="left" valign="top">25</td><td align="left" valign="top">12.89</td><td align="left" valign="top">Intermediate</td></tr><tr><td align="left" valign="top">008P</td><td align="left" valign="top">23/10/23</td><td align="left" valign="top">190</td><td align="left" valign="top">0</td><td align="left" valign="top">0.00</td><td align="left" valign="top">0</td><td align="left" valign="top">0.00</td><td align="left" valign="top">None</td></tr><tr><td align="left" valign="top">009P</td><td align="left" valign="top">23/10/23</td><td align="left" valign="top">190</td><td align="left" valign="top">307</td><td align="left" valign="top">90.53</td><td align="left" valign="top">161</td><td align="left" valign="top">84.74</td><td align="left" valign="top">Master</td></tr><tr><td align="left" valign="top">010P</td><td align="left" valign="top">23/10/30</td><td align="left" valign="top">183</td><td align="left" valign="top">157</td><td align="left" valign="top">82.51</td><td align="left" valign="top">144</td><td align="left" valign="top">78.69</td><td align="left" valign="top">Master</td></tr><tr><td align="left" valign="top" colspan="2">Total (Average)</td><td align="left" valign="top">206.6</td><td align="left" valign="top">2402</td><td align="left" valign="top">63.70</td><td align="left" valign="top">1079</td><td align="left" valign="top">50.74</td><td align="left" valign="top">N/A<sup><xref ref-type="table-fn" rid="table7fn5">e</xref></sup></td></tr></tbody></table><table-wrap-foot><fn id="table7fn1"><p><sup>a</sup>This table is updated until April 29, 2024, at 2:30 PM.</p></fn><fn id="table7fn2"><p><sup>b</sup>Activity rate for physiological values = (Days logged/Days enrolled) &#x00D7; 100%.</p></fn><fn id="table7fn3"><p><sup>c</sup>Activity rate for kidney health diary = (Days written/Days enrolled) &#x00D7; 100%.</p></fn><fn id="table7fn4"><p><sup>d</sup>Continuous execution days for each Kidney Health Title: novice&#x2014;3 days; intermediate&#x2014;7 days; veteran&#x2014;14 days; and master&#x2014;30 days.</p></fn><fn id="table7fn5"><p><sup>e</sup>N/A: not applicable.</p></fn></table-wrap-foot></table-wrap><p>Eight users had an activity rate higher than 50% for logging physiological values, and among them, 6 also had an activity rate higher than 50% for writing kidney health diaries, indicating these users have a moderate to high level of acceptance and capability in performing daily tasks on the extended app. Regarding the challenges for Kidney Health Titles: 8 out of 10 users achieved consecutive logging of physiological values and writing kidney health diaries for at least 3 days (granted the &#x201C;Kidney Novice&#x201D; title) during the observation period; among the previously mentioned highly active 6 users, they achieved challenges of logging physiological values and writing kidney health diaries consecutively for 7 days (<italic>intermediate</italic>) or even 30 days (<italic>master</italic>). This demonstrates that higher activity levels correlate with a higher chance of long-term adoption of a healthy lifestyle, aligning well with the conclusions drawn from the simulation study.</p></sec><sec id="s3-1-4-3"><title>Dyadic Feedback Content</title><p><xref ref-type="table" rid="table8">Table 8</xref> summarized the average ratings for each of the 6 major functions of our integrated platform, as provided by the 10 dyads in their user feedback forms. Generally, more than 80% of the dyads (more than 8) perceived each function to have a clear interface and to be easy to use. Similarly, most of the dyads (more than 80%) found each function acceptable and expressed their intention to continue usage. The average satisfaction rating for each function ranged from 3.5 to 4.3, with an overall rating of 4.1 for the platform as a whole.</p><table-wrap id="t8" position="float"><label>Table 8.</label><caption><p>Phase 1 dyadic trial use feedback form rating summary (N=10)<sup><xref ref-type="table-fn" rid="table8fn1">a</xref></sup>.</p></caption><table id="table8" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" rowspan="2">Functions of the digital platform</td><td align="left" valign="bottom" colspan="5">Assessed elements</td></tr><tr><td align="left" valign="bottom">#N-1: Interface clarity</td><td align="left" valign="bottom">#N-2: Ease of operation</td><td align="left" valign="bottom">#N-3: Acceptability</td><td align="left" valign="bottom">#N-4, 7&#x2010;2: Intention to continue usage</td><td align="left" valign="bottom">#N-5, 7&#x2010;2: Satisfaction rating (from 1 to 5)</td></tr></thead><tbody><tr><td align="left" valign="top">Health Education Information</td><td align="left" valign="top">90%</td><td align="left" valign="top">90%</td><td align="left" valign="top">90%</td><td align="left" valign="top">90%</td><td align="left" valign="top">3.9</td></tr><tr><td align="left" valign="top">Kidney Support Teammate</td><td align="left" valign="top">90%</td><td align="left" valign="top">100%</td><td align="left" valign="top">90%</td><td align="left" valign="top">90%</td><td align="left" valign="top">3.5</td></tr><tr><td align="left" valign="top">Record Values</td><td align="left" valign="top">90%</td><td align="left" valign="top">80%</td><td align="left" valign="top">90%</td><td align="left" valign="top">80%</td><td align="left" valign="top">4.3</td></tr><tr><td align="left" valign="top">Reminder Settings</td><td align="left" valign="top">100%</td><td align="left" valign="top">90%</td><td align="left" valign="top">90%</td><td align="left" valign="top">90%</td><td align="left" valign="top">4.1</td></tr><tr><td align="left" valign="top">Kidney Health Mission</td><td align="left" valign="top">80%</td><td align="left" valign="top">90%</td><td align="left" valign="top">80%</td><td align="left" valign="top">80%</td><td align="left" valign="top">3.8</td></tr><tr><td align="left" valign="top">Inquiry &#x0026; Consultation</td><td align="left" valign="top">100%</td><td align="left" valign="top">90%</td><td align="left" valign="top">80%</td><td align="left" valign="top">90%</td><td align="left" valign="top">3.7</td></tr><tr><td align="left" valign="top">Average</td><td align="left" valign="top">91.67%</td><td align="left" valign="top">90%</td><td align="left" valign="top">86.67%</td><td align="left" valign="top">86.67%</td><td align="left" valign="top">3.9</td></tr><tr><td align="left" valign="top">Overall platform evaluation</td><td align="left" valign="top">N/A<sup><xref ref-type="table-fn" rid="table8fn2">b</xref></sup></td><td align="left" valign="top">N/A</td><td align="left" valign="top">N/A</td><td align="left" valign="top">90%</td><td align="left" valign="top">4.1</td></tr></tbody></table><table-wrap-foot><fn id="table8fn1"><p><sup>a</sup>The percentages in this table reflect the proportion of participant dyads who answered &#x201C;Yes&#x201D; to the corresponding Yes/No questions in the user feedback form.</p></fn><fn id="table8fn2"><p><sup>b</sup>N/A: not applicable.</p></fn></table-wrap-foot></table-wrap><p>Qualitative feedback on each function, gathered through user feedback forms and brief interviews, is organized according to its positive and negative aspects:</p><list list-type="order"><list-item><p>Health Education Information (LINE): Dyads generally appreciated this function for its simplicity, clarity, and informative nature, noting that &#x201C;it provided access to various, accurate CKD-related information at any time&#x201D; (no. 005). However, one dyad (no. 010) suggested that &#x201C;the font size should be enlarged, and the navigation of this function needs simplification to avoid getting lost.<italic>&#x201D;</italic></p></list-item><list-item><p>Kidney Support Teammate (LINE): The majority of dyads found this function to be beneficial, appreciating its provision of &#x201C;mutual support, encouragement, reminders, and detailed knowledge&#x201D; (nos. 001 and 002). However, 2 dyads expressed concerns regarding its usage, with one noting &#x201C;not using this function&#x201D; (no. 005) and the other mentioning that &#x201C;the colors are too vibrant, making it difficult to grasp key points, and navigating within the function could lead to getting lost&#x201D; (no. 007).</p></list-item><list-item><p>Record Values (LINE+ App extension): Overall, dyads expressed satisfaction with this function, noting its advantages in &#x201C;replacing traditional paper records, convenience, ease of use, and the ability to track data&#x201D; (nos. 001, 002, and 009). Specifically, 1 dyad (no. 005) appreciated the support for chart view upon logging in data, facilitating easy tracking. However, 1 dyad (no. 010) mentioned dissatisfaction with the small font size and confusion regarding certain actions due to unclear wording.</p></list-item><list-item><p>Reminder Settings (LINE+ App extension): Dyads expressed overall satisfaction with this function, particularly highlighting its capability to provide advance notifications for upcoming clinical appointments. This function was deemed convenient and provided peace of mind by several dyads (no. 001, 005, and 009), eliminating the need to remember appointment dates. No negative feedback was received about this function.</p></list-item><list-item><p>Kidney Health Mission (LINE+ App extension): Overall, dyads who appreciated this function found its operation to be straightforward. Some dyads specifically noted its convenience for recording daily diet by uploading a photograph (no. 005) and its provision of daily data for tracking (no. 002). Conversely, 1 dyad found this function &#x201C;troublesome, causing psychological pressure,&#x201D; and despite its good intent, felt &#x201C;it lacked feedback from healthcare providers&#x201D; (no. 001). Another dyad expressed inconvenience due to the small font size and difficulties logging in data (no. 010).</p></list-item><list-item><p>Inquiry &#x0026; Consultation (LINE): Dyads provided positive feedback regarding the helpfulness of this function, particularly emphasizing its ability to provide answers to various relevant questions (nos. 002, 005, and 009). One dyad noted that &#x201C;for new CKD patients, this function could serve as a substitute for in-person health education; however, for experienced patients, this function may seem unnecessary as they are already familiar with the answers&#x201D; (no. 001). Another dyad commented on the potential for getting lost while navigating through the content of this function (no. 007).</p></list-item></list><p>Regarding the overall evaluation of the digital platform, neither dyad had previously used other apps or websites for managing CKD. Almost all of the dyads (90%) expressed willingness to continue using it to aid in managing their CKD. Upon further in-depth interviews with researchers about dyadic feedback, all agreed that the digital platform&#x2019;s functions were comprehensive, with no suggestions for additional functions. The first patient (no. 001P) mentioned that using the platform provided a &#x201C;routine&#x201D; after retirement. His SO (no. 001S) also mentioned the lack of diverse social activities after retirement for the patient and expressed interest in participating in hospital support groups to share their experiences with other CKD dyads.</p></sec></sec></sec><sec id="s3-2"><title>Phase 2: Heuristic Evaluation</title><p>By early November 2023, the team collected responses from 5 evaluators who participated in the heuristic evaluation. The evaluators&#x2019; basic information is shown in <xref ref-type="table" rid="table9">Table 9</xref>.</p><table-wrap id="t9" position="float"><label>Table 9.</label><caption><p>Basic information of phase 2 heuristic evaluation participants (N=5).</p></caption><table id="table9" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">No.</td><td align="left" valign="bottom">Sex</td><td align="left" valign="bottom">Age (years)</td><td align="left" valign="bottom">Education</td><td align="left" valign="bottom">Background</td><td align="left" valign="bottom">Current occupation</td></tr></thead><tbody><tr><td align="left" valign="top">1</td><td align="left" valign="top">Female</td><td align="left" valign="top">55</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Nursing</td><td align="left" valign="top">Professor</td></tr><tr><td align="left" valign="top">2</td><td align="left" valign="top">Female</td><td align="left" valign="top">42</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Health care science</td><td align="left" valign="top">Associate professor</td></tr><tr><td align="left" valign="top">3</td><td align="left" valign="top">Female</td><td align="left" valign="top">45</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Nursing</td><td align="left" valign="top">Assistant professor</td></tr><tr><td align="left" valign="top">4</td><td align="left" valign="top">Female</td><td align="left" valign="top">54</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Nursing</td><td align="left" valign="top">Assistant professor</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">Male</td><td align="left" valign="top">28</td><td align="left" valign="top">Master&#x2019;s degree</td><td align="left" valign="top">Electrical engineering</td><td align="left" valign="top">Engineer</td></tr></tbody></table></table-wrap><sec id="s3-2-1"><title>General Compliance Rating</title><p>Their scores regarding the compliance of various functions with usability principles were tallied, averaged, and summarized in <xref ref-type="table" rid="table10">Table 10</xref>. On average, the compliance scores for each principle ranged between 0 (<italic>partially complies</italic>) and 1 (<italic>complies</italic>). The functions&#x2019; average compliance with the 10 usability principles ranged from 89% to 93%. This suggests that the evaluators generally perceived that the digital platform&#x2019;s various functions mostly complied with the usability principles.</p><table-wrap id="t10" position="float"><label>Table 10.</label><caption><p>Phase 2 heuristic evaluation compliance rating summary (N=5)<sup><xref ref-type="table-fn" rid="table10fn1">a</xref></sup>.</p></caption><table id="table10" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" rowspan="2">Degree of compliance with each usability principle</td><td align="left" valign="bottom" colspan="6">Functions of the digital platform</td></tr><tr><td align="left" valign="bottom">Health Education Information, %</td><td align="left" valign="bottom">Kidney Support Teammate, %</td><td align="left" valign="bottom">Record Values, %</td><td align="left" valign="bottom">Reminder Settings, %</td><td align="left" valign="bottom">Kidney Health Mission, %</td><td align="left" valign="bottom">Inquiry &#x0026; Consultation, %</td></tr></thead><tbody><tr><td align="left" valign="top">Principle 1</td><td align="left" valign="top">60</td><td align="left" valign="top">80</td><td align="left" valign="top">100</td><td align="left" valign="top">80</td><td align="left" valign="top">80</td><td align="left" valign="top">100</td></tr><tr><td align="left" valign="top">Principle 2</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">80</td><td align="left" valign="top">100</td></tr><tr><td align="left" valign="top">Principle 3</td><td align="left" valign="top">100</td><td align="left" valign="top">80</td><td align="left" valign="top">80</td><td align="left" valign="top">60</td><td align="left" valign="top">100</td><td align="left" valign="top">75</td></tr><tr><td align="left" valign="top">Principle 4</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td></tr><tr><td align="left" valign="top">Principle 5</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td></tr><tr><td align="left" valign="top">Principle 6</td><td align="left" valign="top">80</td><td align="left" valign="top">80</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">75</td></tr><tr><td align="left" valign="top">Principle 7</td><td align="left" valign="top">80</td><td align="left" valign="top">80</td><td align="left" valign="top">100</td><td align="left" valign="top">60</td><td align="left" valign="top">100</td><td align="left" valign="top">80</td></tr><tr><td align="left" valign="top">Principle 8</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td></tr><tr><td align="left" valign="top">Principle 9</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">33.33</td><td align="left" valign="top">100</td><td align="left" valign="top">33.33</td><td align="left" valign="top">100</td></tr><tr><td align="left" valign="top">Principle 10</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td><td align="left" valign="top">100</td></tr><tr><td align="left" valign="top">Overall result</td><td align="left" valign="top">92</td><td align="left" valign="top">92</td><td align="left" valign="top">91.33</td><td align="left" valign="top">90</td><td align="left" valign="top">89.33</td><td align="left" valign="top">93</td></tr></tbody></table><table-wrap-foot><fn id="table10fn1"><p><sup>a</sup>Compliance percentages represent the sum of evaluator ratings (<italic>&#x2212;</italic>1, 0, or 1) for each function&#x2019;s compliance with each usability principle, divided by the number of valid responses (ie, excluding &#x201C;N/A [not applicable]&#x201D; selections), and then multiplied by 100%.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2-2"><title>Recommendations for Improvement</title><p>The breakdown of issues raised by evaluators about each function&#x2019;s incompliance with certain principles and their recommendations is as follows:</p><p>1. Health Education Information</p><list list-type="bullet"><list-item><p>Principle 1 (60% compliance): Evaluator 1 found that &#x201C;clicking into the five stages of CKD and lab test reports didn&#x2019;t lead to corresponding content.&#x201D; Evaluator 5 suggested &#x201C;transforming health education information into daily articles and actively pushing them to users with thematic context.&#x201D;</p></list-item><list-item><p>Principle 6 (80% compliance): Evaluator 2 felt that the design here might cause information loss or be easily forgotten after closing the linked web page and suggested implementing a memory function for highly clicked queries.</p></list-item><list-item><p>Principle 7 (80% compliance): Evaluator 2 believed that this function lacked personal flexibility and suggested establishing personalized zones based on click rates to access or push commonly used information.</p></list-item></list><p>2. Kidney Support Teammate</p><list list-type="bullet"><list-item><p>Principle 1 (80% compliance): Evaluator 5 felt that while the information was comprehensive, the incentive for users to actively read this information was slightly weak and suggested recommending correct concepts based on user records.</p></list-item><list-item><p>Principle 3 (80% compliance): Evaluator 2 noticed that once clicked, the buttons for some information, returning to the previous message is not supported, requiring scrolling or clicking on the service menu again, recommending immediate display of original options after dialogue box content appears.</p></list-item><list-item><p>Principle 6 (80% compliance): Same as evaluator 2&#x2019;s feedback in (1) &#x201C;principle 6 (80% compliance).&#x201D;</p></list-item><list-item><p>Principle 7 (80% compliance): Same as evaluator 2&#x2019;s feedback in (1) &#x201C;principle 7 (80% compliance).&#x201D;</p></list-item></list><p>3. Record Values</p><list list-type="bullet"><list-item><p>Principle 3 (80% compliance): Evaluator 1 noted that after entering values, the entire app needed closing to return to the main screen and suggested adjusting this.</p></list-item><list-item><p>Principle 9 (33% compliance): Evaluator 5 noticed that there were no notifications for abnormal physiological values and suggested providing automatic or manual messages based on professional or objective facts for abnormal values.</p></list-item></list><p>4. Reminder Settings</p><list list-type="bullet"><list-item><p>Principle 1 (80% compliance): No specific issues or suggestions were mentioned by the evaluator.</p></list-item><list-item><p>Principle 3 (60% compliance): Evaluator 5 discovered that alterations in the reminder function required notification to researchers and suggested allowing users to freely set daily or appointment reminders, similar to setting alarms on a phone.</p></list-item><list-item><p>Principle 7 (60% compliance): Same as evaluator 5&#x2019;s feedback in (4) &#x201C;principle 3 (60% compliance).&#x201D;</p></list-item></list><p>5. Kidney Health Mission</p><list list-type="bullet"><list-item><p>Principle 1 (80% compliance): Evaluator 5 felt that the current daily diet recording was based on self-assessment without professional guidance and suggested having professionals review information and provide guidance.</p></list-item><list-item><p>Principle 2 (80% compliance): Same as evaluator 5&#x2019;s feedback in (5) &#x201C;principle 1 (80% compliance).&#x201D;</p></list-item><list-item><p>Principle 9 (33% compliance): Same as evaluator 5&#x2019;s feedback in (3) &#x201C;principle 9 (33% compliance).&#x201D;</p></list-item></list><p>6. Inquiry &#x0026; Consultation</p><list list-type="bullet"><list-item><p>Principle 3 (75% compliance): Same as Evaluator 2&#x2019;s feedback in (2) &#x201C;principle 3 (80% compliance).&#x201D;</p></list-item><list-item><p>Principle 6 (75% compliance): Same as evaluator 2&#x2019;s feedback in (1) &#x201C;principle 6 (80% compliance).&#x201D;</p></list-item><list-item><p>Principle 7 (80% compliance): Same as evaluator 2&#x2019;s feedback in (1) &#x201C;principle 7 (80% compliance).&#x201D;</p></list-item></list><p>Overall, based on the evaluation scores and feedback from evaluators on each function of the digital platform concerning various principles, this phase successfully acquired specific recommendations for improving the platform&#x2019;s usability. These suggestions can generally be categorized into three aspects: (1) enhancing user operation convenience, such as adding a return option in Health Education Information, Kidney Support Teammate, and Inquiry &#x0026; Consultation, reducing repetitive operation hassles; (2) pushing more relevant and engaging information, for instance, pushing corresponding educational content based on user records; and (3) enhancing interactivity and feedback of functions, such as providing personalized memory functions for highly clicked content, warning after inputting abnormal physiological values, or providing feedback from professionals. Results of the heuristic evaluation have guided the modification of the digital platform for the next iteration to enhance user experience.</p></sec></sec><sec id="s3-3"><title>Phase 3: Usability Testing</title><p>Following the design of tasks, the selection of participants for phase 3 involved convenience sampling by inviting 5 dyads who participated in phase 1 trial use during their next clinic visits. Eventually, dyad numbers 001, 002, 005, 007, and 009 agreed to take part in the testing. The results of their average performance on our designed tasks and their average ASQ ratings are summarized in <xref ref-type="table" rid="table11">Table 11</xref>.</p><table-wrap id="t11" position="float"><label>Table 11.</label><caption><p>Phase 3 usability testing task performance and rating summary (N=5).</p></caption><table id="table11" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" rowspan="2"/><td align="left" valign="bottom" colspan="6">Functions of the digital platform</td></tr><tr><td align="left" valign="bottom">Health Education Information</td><td align="left" valign="bottom">Kidney Support Teammate</td><td align="left" valign="bottom">Record Values</td><td align="left" valign="bottom">Reminder Settings</td><td align="left" valign="bottom">Kidney Health Mission</td><td align="left" valign="bottom">Inquiry &#x0026; Consultation</td></tr></thead><tbody><tr><td align="left" valign="top">Task success<sup><xref ref-type="table-fn" rid="table11fn1">a</xref></sup></td><td align="left" valign="top">60%</td><td align="left" valign="top">80%</td><td align="left" valign="top">100%</td><td align="left" valign="top">100%</td><td align="left" valign="top">100%</td><td align="left" valign="top">80%</td></tr><tr><td align="left" valign="top">Task time (mm:ss)</td><td align="left" valign="top">04:23</td><td align="left" valign="top">05:16</td><td align="left" valign="top">01:06</td><td align="left" valign="top">01:52</td><td align="left" valign="top">01:04</td><td align="left" valign="top">02:55</td></tr><tr><td align="left" valign="top">Average error times (range)</td><td align="left" valign="top">1 (0&#x2010;2)</td><td align="left" valign="top">1.4 (1-2)</td><td align="left" valign="top">0.2 (0&#x2010;1)</td><td align="left" valign="top">0.8 (0&#x2010;1)</td><td align="left" valign="top">0</td><td align="left" valign="top">1.2 (0&#x2010;2)</td></tr><tr><td align="left" valign="top">ASQ: ease of use<sup><xref ref-type="table-fn" rid="table11fn2">b</xref></sup></td><td align="left" valign="top">3.6</td><td align="left" valign="top">4</td><td align="left" valign="top">6.2</td><td align="left" valign="top">5.4</td><td align="left" valign="top">6</td><td align="left" valign="top">4.2</td></tr><tr><td align="left" valign="top">ASQ: time required</td><td align="left" valign="top">3.4</td><td align="left" valign="top">4.2</td><td align="left" valign="top">6.4</td><td align="left" valign="top">5.2</td><td align="left" valign="top">6.2</td><td align="left" valign="top">4.2</td></tr><tr><td align="left" valign="top">ASQ: help received</td><td align="left" valign="top">3.8</td><td align="left" valign="top">3.8</td><td align="left" valign="top">6</td><td align="left" valign="top">4.2</td><td align="left" valign="top">5.2</td><td align="left" valign="top">3.6</td></tr><tr><td align="left" valign="top">Average ASQ score</td><td align="left" valign="top">3.6</td><td align="left" valign="top">4</td><td align="left" valign="top">6.2</td><td align="left" valign="top">4.9</td><td align="left" valign="top">5.8</td><td align="left" valign="top">4</td></tr></tbody></table><table-wrap-foot><fn id="table11fn1"><p><sup>a</sup>Task success = (Number of dyads successfully completed the task/N) &#x00D7; 100%.</p></fn><fn id="table11fn2"><p><sup>b</sup>ASQ: After-Scenario Questionnaire. The score of ASQ ranges from 1 to 7, with higher score indicating higher level of satisfaction.</p></fn></table-wrap-foot></table-wrap><sec id="s3-3-1"><title>Task Performance and ASQ</title><p>This section describes the designed task scenario for each function and summarizes participants&#x2019; general task performance as well as their ASQ ratings:</p><p>1. Health Education Information: The task scenario reflected the need for patients with CKD to calculate their estimated glomerular filtration rate (eGFR) independently. To accomplish this task, users can navigate through the Health Education Information section in our LINE OA to find a link to a web page with an eGFR calculator. Results indicated that 3 out of 5 dyads completed this task successfully (success rate 60%), with an average completion time of approximately 4.5 minutes. Operational errors were observed with numbers 002, 005, and 009, who navigated to the wrong sections, causing them additional time to locate the eGFR calculator. Another error occurred when number 007 could not find the box to enter the value of creatinine (CREA), as the enlarged font size setting obscured a clear presentation of the calculator elements on the smartphone. The average ASQ score for this task is 3.6, which is the lowest score among all tasks, indicating that dyads were the least satisfied with the ease and the time required for this task. They also perceived minimal help from the user manual.</p><p>2. Kidney Support Teammate: The task scenario involved an SO finding effective ways to support a patient who is attempting lifestyle modification. The Kidney Support Teammate in our LINE OA provides such information for SOs to implement supportive strategies. The task success rate is 80%, with only 1 dyad failing to complete this task. The average completion time exceeded 5 minutes, which is the longest among all tasks. All dyads took time to navigate different sections before they located the target information for this task. Dyads numbers 005 and 009 experienced uncertainty as they browsed through the correct section but did not recognize the target information. The average ASQ score is 4, indicating a moderate but relatively low level of user satisfaction compared with the other tasks.</p><p>3. Record Values: The task scenario reflects the need for patients with CKD to monitor their own physiological data. Completing this task requires the user to click &#x201C;Record Values&#x201D; on the service menu of our LINE OA or click &#x201C;New Entry&#x201D; on the extended app and input the numbers. The task success rate is 100%, with an average completion time of only 1 minute. Dyad number 007 encountered initial difficulty when trying to input the CREA value. The average ASQ score is 6.2, which is the highest among all tasks. These results suggested that this function is user-friendly and intuitive, leading to high user satisfaction.</p><p>4. Reminder Settings: The task scenario arises when patients with CKD wish to set a reminder for their upcoming clinical appointment. Dyads will need to input the date and time of their next appointment using the extended app and notify the research team via LINE OA to set an automatic message reminder. The task success rate is 100%, with an average completion time of around 2 minutes. Dyads numbers 002 and 007 seemed unfamiliar with this function as they clicked &#x201C;New Entry&#x201D; on the extended app, which redirected them to the wrong page. The average ASQ score is 4.9, indicating a moderate satisfaction level with this function.</p><p>5. Kidney Health Mission: The task scenario revolves around the essential practice of tracking daily diet, a key aspect of managing CKD. Users can access this task by clicking &#x201C;Kidney Health Mission&#x201D; on the service menu of our LINE OA or selecting &#x201C;Kidney Health Diary&#x201D; on the extended app to upload a photograph or text note regarding their diet. The task success rate is 100%, with an average completion time of just 1 minute. All dyads completed the task without encountering any operational errors, indicating that the design of this function is sufficiently intuitive. The average ASQ score is 5.8, demonstrating a relatively high level of satisfaction compared with the other tasks.</p><p>6. Inquiry &#x0026; Consultation: This task scenario arises when patients with CKD encounter health-related inquiries at home without access to a health care professional. Users can explore the frequently asked question section in our LINE OA to seek answers to their questions. For instance, this task involves users wanting to learn about the symptoms of hypoglycemia (low blood sugar) using our platform. The task success rate is 80%, with dyad number 002 failing to complete the task. On average, it takes around 3 minutes to complete the task, as all dyads navigate through different sections of our LINE OA to find the desired information. Errors occurred when all dyads, except number 001, attempted to locate the answer in the Health Education Information section. The average ASQ score is 4, indicating a moderate but relatively low level of user satisfaction, highlighting areas for usability improvement.</p></sec><sec id="s3-3-2"><title>Overall Platform Usability</title><p>The SUS scores provided by the 5 dyads range from 57.5 to 87.5, with an average score of 67.5, just below the industry standard threshold of 68. This indicates that users found the platform to be marginally acceptable in terms of usability, indicating areas for improvement. In combination with the performance and ASQ ratings of the 6 tasks, it was observed that the 3 tasks involving operations on the extended app (ie, Record Values, Reminder Settings, and Kidney Health Mission) all achieved a 100% success rate, with shorter completion times, fewer operational errors, and higher satisfaction (mean average ASQ score: 5.64 vs 3.87 for the other 3 tasks). Conversely, tasks with lower performance and ASQ scores (ie, Health Education Information, Kidney Support Teammate, and Inquiry &#x0026; Consultation) all involved finding information within LINE OA, suggesting that underlying significant usability issues in this area may have contributed to the low overall platform SUS score.</p></sec></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Results</title><p>In this study, we demonstrated that through an instant messaging app, our digital platform aimed at empowering lifestyle modification for CKD dyads holds promise for its cost-effectiveness, high user engagement, and potential clinical practicality. Key insights emerged from the 3-phase development cycle are as follows.</p><p>First, the application of Agile methods facilitated a flexible and efficient process in developing our digital platform. Notably, the platform design and deployment were accomplished within a remarkably short time frame of 3 months, with the ability to accommodate modifications, typically within a week. Such adaptability of our platform ensured responsiveness to user needs throughout the development cycle.</p><p>Second, guided by the DDEF, this study introduced 2 quantifiable daily self-management tasks&#x2014;logging physiological values and maintaining a kidney health diary&#x2014;to address the multifaceted nature of CKD management. These tasks, coupled with behavior change techniques, aimed to promote sustained user engagement. The EAR of these tasks emerged as a simple, innovative, and promising indicator of users&#x2019; lifestyle modification abilities, which could facilitate more precise tailored interventions based on different user activity levels.</p><p>Third, comprehensive evaluation across 3 phases revealed high user acceptance and satisfaction with our digital platform. However, usability challenges, particularly concerning information layout within the LINE OA, were identified. The absence of CKD dyad involvement during the initial prototype development hindered the alignment of the content of LINE OA service menu with varying user mental models, potentially causing users to struggle with navigation [<xref ref-type="bibr" rid="ref37">37</xref>]. This finding underscores the importance of considering user expectations early in the development cycle to ensure optimal usability.</p></sec><sec id="s4-2"><title>Comparison With Prior Work</title><p>Previous DHIs for CKD management have adopted various approaches, including a mobile app [<xref ref-type="bibr" rid="ref15">15</xref>], a web-based platform [<xref ref-type="bibr" rid="ref17">17</xref>], a chatbot [<xref ref-type="bibr" rid="ref21">21</xref>], and the combination of a mobile app and wearable devices with instant messaging support [<xref ref-type="bibr" rid="ref20">20</xref>]. These interventions have demonstrated potential in supporting CKD health education and self-management. However, challenges were faced such as limited evidence of sustained use&#x2014;many reported low [<xref ref-type="bibr" rid="ref15">15</xref>] or unclear usage rates [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]&#x2014;and participant samples skewed toward younger, tech-savvy patients (mean age around 50 years), due to the necessity of internet access and smartphone proficiency. Moreover, prior systems typically focused on a single aspect of care (education or tracking) and rarely involved patients&#x2019; family members, potentially excluding older patients who require caregiver support. In contrast, our LINE-based digital dyadic empowerment platform addresses these gaps through the following strengths mentioned in the subsections.</p><sec id="s4-2-1"><title>Diverse Participant Backgrounds</title><p>Our study encompassed participants with diverse backgrounds, ranging from health care providers (including nephrologists and nurses) within the institution involved in phase 1 system development, to patients with CKD and SOs engaged in both phase 1 platform trial use and phase 3 usability testing. Health care and electrical engineering experts from external institutions were involved in phase 2 heuristic evaluation. Of these participants, 41.7% (10/24) were male, spanning ages from 28 to 82 years, and educational attainment ranging from elementary school to doctoral degrees. Such diversity maximized the input from all potential stakeholders who could use or benefit from our digital platform. We ensured that various perspectives were considered throughout the development cycle, thereby optimizing platform usability while accommodating user differences.</p><p>Notably, the design of including SOs with patients with CKD in our study was pivotal. It not only enriched the diversity of perspectives but also prevented the exclusion of patients who might face challenges participating independently, such as those from older age groups or with lower educational levels, potentially constituting digitally disadvantaged groups. This inclusive approach, exemplified by dyads numbers 004 and 005 (<xref ref-type="table" rid="table5">Table 5</xref>), served to mitigate selection bias and promote health equity at the digital resource level.</p></sec><sec id="s4-2-2"><title>A Scalable and Practical Digital Platform</title><p>In a 2023 internet survey conducted in Taiwan, it was found that 98.51% of internet users use instant messaging tools, with LINE holding a dominant market share of 91.61% [<xref ref-type="bibr" rid="ref38">38</xref>]. Our digital platform operates within Taiwan&#x2019;s most prevalent instant messaging app, significantly improving its accessibility and ubiquity. This integration closely aligns CKD self-management with the most frequent daily use of digital technology. Data extracted from the backend of the LINE OA further revealed consistent user engagement with our digital platform, with more than 90% of interactions being automatic Push or Reply messages (<xref ref-type="table" rid="table6">Table 6</xref>). This underscores the high automation and low-cost model of our digital platform, demonstrating its potential for scalable application in medical settings.</p><p><xref ref-type="fig" rid="figure5">Figure 5</xref> further illustrates the interactive relationship between CKD dyads, the research team, and health care providers, elucidating how our digital platform can enhance CKD care in medical settings. The green arrow at the bottom represents patients with CKD and their SOs seeking routine care at the hospital. Blue arrows depict CKD dyads using LINE OA, either through encouragement or voluntary interaction, to stay connected with the research team (<italic>communication</italic> strategy); or using the extended app to log home-based health records, including blood pressure, diet, medication, and physical activity (<italic>monitoring</italic> strategy). Red arrows signify the fully automated services offered by our digital platform, such as providing health education information through LINE OA Push or Reply messages (<italic>education</italic> strategy); or accessing physiological trend charts and usage reports via the extended app (<italic>feedback</italic> strategy). Orange arrows indicate the interventions that the research team can deliver through the digital platform, such as maintaining contact with CKD dyads (<italic>communication</italic> strategy); or answering CKD dyads&#x2019; queries and sending encouraging messages (<italic>feedback</italic> strategy) via LINE OA. Finally, the research team can further analyze and aggregate home-based self-monitoring records logged by CKD dyads through the extended app (<italic>analysis</italic> strategy) and provide reports to health care providers. This additional information will furnish health care providers with supplementary insights during CKD dyads&#x2019; visits, aiding in treatment recommendations to enhance the quality of CKD care.</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>The schematic diagram of the LINE Official Account &#x201C;Kidney Lifestyle&#x201D; and the extended app in enhancing CKD care. The arrows marked with an asterisk (*) represent the practical application of the 5 digital strategies mentioned in the Digital Dyadic Empowerment Framework. Blue arrows represent the active engagement from CKD dyads. Orange arrows denote service flows involving human support, while red arrows denote service flows with full automation. BP: blood pressure; CKD: chronic kidney disease; PA: physical activity.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e73935_fig05.png"/></fig></sec><sec id="s4-2-3"><title>Empirical Evidence for Sustained User Engagement</title><p>This study provides empirical evidence of high user acceptance and satisfaction with our digital platform, as indicated by self-reported satisfaction ratings and intentions to continue usage during phase 1 trial use, as well as by the ASQ scores obtained from phase 3 usability testing. While self-reported ratings could potentially be inflated by demand characteristics [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>], the robustness of these findings is further supported by users&#x2019; consistent execution of the 2 daily self-management tasks. As depicted in <xref ref-type="table" rid="table7">Table 7</xref>, more than half of the 10 trial users maintained an EAR from 50% to 100% for the 2 daily tasks for more than 6 months. Notably, 5 users had a record of executing the 2 daily tasks consecutively for 30 days or more, demonstrating their ability to sustain regular usage. These findings imply their persistent commitment to using our digital platform for managing CKD, even after they completed the study. Such ongoing engagement serves as compelling evidence of our digital platform&#x2019;s potential as a highly acceptable digital health solution, empowering CKD dyads in the process of lifestyle modification.</p></sec></sec><sec id="s4-3"><title>Limitations</title><sec id="s4-3-1"><title>Potential Selection Bias Induced by Digital Divides</title><p>Despite the wide availability of our digital platform on LINE OA and the inclusive dyadic design, this study might still have suffered from selection bias due to digital divides between those with access to our platform and those without [<xref ref-type="bibr" rid="ref41">41</xref>]. During phase 1 participant recruitment, we encountered instances where some CKD dyads, particularly spouses, reported lacking access to smartphones or the internet. Conversely, some dyads had smartphones with internet access but lacked diverse digital skills or did not have LINE installed on their phones. All these factors could impede the implementation of our study and raise concerns over health inequity. Although the extent of these digital divides was not thoroughly investigated within the scope of this study, their existence warrants careful consideration in our future work to prevent selection bias favoring participants with higher digital proficiency.</p><p>For participants facing difficulties in using our platform, personalized assistance will be provided through interactive learning sessions and the user manual, reducing the likelihood of their attrition from the study. Furthermore, future research could investigate the prevalence and characteristics of digitally disadvantaged groups within the CKD population. Assessing the severity and underlying causes of digital divides may help mitigate their impact on the implementation of our DHI. Alternatively, programs empowering lifestyle modification tailored to CKD dyads who are not internet or smartphone users could be developed.</p></sec><sec id="s4-3-2"><title>Usability Issues With LINE OA Navigation</title><p>Despite continuous optimization, the SUS scores obtained from phase 3 usability testing indicate that the usability of our digital platform remains marginally acceptable. Particularly, significant usability issues were identified within the information layout of the service menu on LINE OA. During phase 1 trial use, dyads reported difficulties navigating sections including Health Education Information, Kidney Support Teammate, and Inquiry &#x0026; Consultation, often getting lost. Similarly, task performance and user satisfaction related to these sections were relatively low in phase 3 usability testing. However, tracking individual user interactions with specific sections in LINE OA is challenging due to its backend limitations, as only aggregate user activity data are available. This impedes the establishment of personalized sections, as suggested by the heuristic evaluators in phase 2.</p><p>Analysis of phase 3 error records further revealed 2 major sources of confusion (<xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>). First, users were often unsure whether to seek answers in Health Education Information or Inquiry &#x0026; Consultation, as both sections were perceived to serve a similar purpose of obtaining CKD-related knowledge. This mismatch between users&#x2019; mental models and the platform&#x2019;s menu structure frequently led them to attempt tasks in the wrong section, causing navigation failures. Second, the design of LINE OA as an instant messaging interface posed inherent challenges: the service menu occupies nearly one-third of the small mobile screen, while new messages push earlier information upward, forcing users to scroll back or reselect menu buttons to revisit prior content. When combined with multilayered menu depth, these constraints increased cognitive load and disorientation, further compounding the likelihood of users getting lost.</p><p>To overcome these challenges, several measures have been introduced and others are planned. In response to phase 2 feedback, we incorporated a &#x201C;return to previous level&#x201D; option within the Kidney Support Teammate and Inquiry &#x0026; Consultation sections (<xref ref-type="fig" rid="figure2">Figure 2D</xref>), providing a route back when disoriented. Future platform refinements could also consolidate Health Education Information and Inquiry &#x0026; Consultation into a single section, for instance, by embedding Inquiry &#x0026; Consultation under Health Education Information to reduce functional overlap and user confusion. Moreover, involving CKD dyads in early stages of prototype development remains essential. Interviews on information needs and common questions could align menu structures more closely with users&#x2019; mental models. Finally, harnessing the instant messaging nature of LINE OA, the inclusion of a chatbot could provide more efficient and context-sensitive access to disease-related information through automated dialogue interactions, thereby enhancing overall usability [<xref ref-type="bibr" rid="ref21">21</xref>].</p></sec><sec id="s4-3-3"><title>Concerns for Low EARs</title><p>Despite our efforts to simplify the design of our digital platform, reducing hierarchies and operational paths, along with manual support and relevant skill teachings, some users, as shown in <xref ref-type="table" rid="table7">Table 7</xref>, have an activity rate below 50% for logging physiological values (2 users) or writing kidney diaries (4 users). We identified 3 potential reasons for these low EARs, indicating the need for more comprehensive interventions as mentioned in the following sections.</p><sec id="s4-3-3-1"><title>Dyads in the Preaction Stages of Change</title><p>Observations from <xref ref-type="table" rid="table5">Tables 5</xref> and <xref ref-type="table" rid="table7">7</xref> revealed a positive relationship between dyads&#x2019; self-reported readiness for lifestyle modification (ie, stages of change) and their execution of daily tasks. The 5 most active dyads, with EARs exceeding 75% for both tasks and having achieved the <italic>Master</italic> kidney health title, were all in the late stages of change (<italic>action</italic> or <italic>maintenance</italic>), while of the other 5 dyads, 3 were in the preaction stages (<italic>contemplation</italic> or <italic>preparation</italic>). Despite daily task reminders, there was no observed increase in activity rates among lower-activity users. Future interventions may focus on leveraging helping relationships with SOs and providing proactive caring phone calls to enhance their motivation for change.</p></sec><sec id="s4-3-3-2"><title>Dyads Perceive No Need for Use</title><p>Among the previously mentioned 5 dyads with lower activity rates, 2 self-reported being in the late stage of change (<italic>maintenance</italic>). These dyads might have already engaged in regular lifestyle modifications but perceive minimal help from our digital platform and hence feel no necessity in using it. To address this, future implementation could focus on highlighting the platform&#x2019;s strengths and collaborating with health care providers to promote the platform&#x2019;s benefits to patients and their caregivers.</p></sec><sec id="s4-3-3-3"><title>Dyads Face Usage Obstacles and Perceive High Execution Difficulty</title><p>Another possible cause of low EARs is shortcomings in the digital platform&#x2019;s design and user manual, leading dyads to perceive high cognitive load and execution difficulty. To address this, helping relationships from SOs and providing assistance are crucial. Regular caring and reminder messages, platform design optimization, and personalized teaching during return visits can help address usage obstacles and enhance usability.</p><p>Another promising future direction is to assess the feasibility of organizing support groups for CKD dyads, based on our dyadic feedback in phase 1. Support groups may facilitate the process of social liberation, exposing dyads to a supportive social environment for behavior change [<xref ref-type="bibr" rid="ref42">42</xref>]. Dyads in the preaction stages might find positive support from the group, enhancing their motivation for change. Support groups can also promote community participation through connections and information exchange and allow their efforts to gain recognition and reinforcement from the group. For dyads perceiving minimal help from the digital platform or finding it too challenging to use, they can observe and learn from other dyads in the support groups, enhancing their confidence and skills in usage.</p></sec></sec></sec><sec id="s4-4"><title>Lack of Feedback From Health Care Providers</title><p>In phase 1 dyad trial use and phase 2 heuristic evaluation, participants highlighted the need for health care provider feedback on user self-monitoring records. However, our digital platform currently lacks feedback mechanisms beyond system-generated physiological trend charts and platform usage reports from the extended app (<xref ref-type="fig" rid="figure3">Figures 3A and 3C</xref>). Specifically, feedback from health care providers on dietary, medication, and exercise content in the kidney health diary is absent. As observed in <xref ref-type="fig" rid="figure5">Figure 5</xref>, health care providers currently do not interact with CKD dyads through our digital platform and are thus unable to provide feedback on the content of the kidney health diary. This gap may contribute to lower activity rates for the kidney health diary compared with physiological values (<xref ref-type="table" rid="table7">Table 7</xref>). Workflow integration challenges are common in the development and application of new digital health tools, as they might potentially burden health care providers with additional tasks or even necessitate practice reorganization [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref43">43</xref>].</p><p>Recognizing the temporary difficulty in overcoming this challenge, an alternative approach involves compiling CKD dyads&#x2019; self-monitoring records into paper-based reports for health care providers. These reports are provided to health care providers on CKD dyads&#x2019; follow-up visit days for reference. During consultations, health care providers can then access the extended app with CKD dyads to review the kidney health diary content as needed. While conducting trials to assess the effect of our digital platform on CKD management is imperative, our future work should also tackle workflow integration issues through close collaboration with health care system personnel to promote platform adoption.</p></sec><sec id="s4-5"><title>Conclusions</title><p>Guided by DDEF and using Agile methods, this study successfully developed, evaluated, and optimized an instant messaging&#x2013;based digital platform tailored for CKD care across a 3-phase development cycle. The resulting product, the LINE OA &#x201C;Kidney Lifestyle&#x201D; and its associated extended app, aims to empower lifestyle modification for CKD dyads. Our investigation uncovered robustly high user acceptance and satisfaction with the platform, evidenced by both self-report ratings and ongoing engagement beyond the study period, lasting over 6 months. The platform&#x2019;s wide availability, high automation, and cost-effective operational model underscore its potential for scalable application in practical health care settings. While our digital solution shows considerable promise, a feasibility study is the logical next step to evaluate implementation factors and potential impacts on CKD management outcomes. Meanwhile, our future works should also bridge digital divides, enhance usability, foster support groups, and integrate our platform into current health care workflow to maximize its effectiveness and scalability. In sum, this study contributes significantly to the growing field of digital health for CKD management by showcasing the potential of an innovative platform integrated with the LINE instant messaging app.</p></sec></sec></body><back><ack><p>The authors would like to thank all participants who took part in this study. The authors are especially grateful to the <italic>Taiwan Kidney Foundation</italic> for authorizing the use of their official educational resources within the platform developed in this study. The authors also extend their sincere thanks to Ms Yu-Chen Kuo, health education nurse at the Health Education Center of National Cheng Kung University Hospital, and to their technical development partner, AlleyPin Interactive Co, LTD, for their valuable suggestions and support throughout the platform development process. The authors additionally thank 2 research assistants, Jung-Jung Liang and Wei-Tung Kao, for their assistance in participant enrollment and data processing. During intervention development, OpenAI&#x2019;s ChatGPT was used to assist in the creation of Google Apps Script functions for backend automation, such as calculating daily task patterns and simulating gamification logic. It was also used to improve language clarity and structure in the manuscript. All outputs were reviewed and edited by the authors, who assume full responsibility for the final content.</p></ack><notes><sec><title>Funding</title><p>This study was supported by the National Health Research Institutes, Taiwan, through the Integrated Research Grants in Health and Medical Sciences (Innovative Research Grant, grant no. NHRI-EX112-11106PI). The funding agency had no role in the design and conduct of the study; collection, management, analysis, and interpretation of data; or preparation, review, and approval of the manuscript.</p></sec><sec><title>Data Availability</title><p>The complete dataset generated during this study&#x2014;including raw item-level feedback from phase 1 dyads, heuristic evaluation scores and qualitative comments from phase 2 experts, and individual-level task performance metrics and questionnaire responses from phase 3 usability testing&#x2014;is available in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>. <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref> also contains summary tables that correspond to the results reported in <xref ref-type="table" rid="table8">Tables 8</xref>, <xref ref-type="table" rid="table10">10</xref>, and <xref ref-type="table" rid="table11">11</xref> of the manuscript.</p></sec></notes><fn-group><fn fn-type="con"><p>MY conceived the study idea, developed the initial study design, secured research funding, and supervised the overall implementation of the study. CYH optimized the study design based on practical considerations, led the development and integration of the digital platform, and was responsible for participant recruitment, data collection, analysis, interpretation, and manuscript preparation. DS contributed to the initial drafting of the "Introduction" section. JMS, MCW, and WHL provided suggestions on platform design and assisted with participant referral. All authors critically reviewed and revised the manuscript for intellectual content and approved the final version for publication.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">API</term><def><p>application programming interface</p></def></def-item><def-item><term id="abb2">ASQ</term><def><p>After-Scenario Questionnaire</p></def></def-item><def-item><term id="abb3">CKD</term><def><p>chronic kidney disease</p></def></def-item><def-item><term id="abb4">CREA</term><def><p>creatinine</p></def></def-item><def-item><term id="abb5">DDEF</term><def><p>Digital Dyadic Empowerment Framework</p></def></def-item><def-item><term id="abb6">DHI</term><def><p>digital health intervention</p></def></def-item><def-item><term id="abb7">EAR</term><def><p>entry activity rate</p></def></def-item><def-item><term id="abb8">eGFR</term><def><p>estimated glomerular filtration rate</p></def></def-item><def-item><term id="abb9">OA</term><def><p>LINE Official Account</p></def></def-item><def-item><term id="abb10">SO</term><def><p>significant other</p></def></def-item><def-item><term id="abb11">SUS</term><def><p>System Usability Scale</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>Bikbov</surname><given-names>B</given-names> </name><name name-style="western"><surname>Purcell</surname><given-names>CA</given-names> </name><name name-style="western"><surname>Levey</surname><given-names>AS</given-names> </name></person-group><article-title>Global, regional, and national burden of chronic kidney disease, 1990-2017: a systematic analysis for the Global Burden of Disease Study 2017</article-title><source>Lancet</source><year>2020</year><month>02</month><day>29</day><volume>395</volume><issue>10225</issue><fpage>709</fpage><lpage>733</lpage><pub-id pub-id-type="doi">10.1016/S0140-6736(20)30045-3</pub-id><pub-id pub-id-type="medline">32061315</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>Lee</surname><given-names>CC</given-names> </name><name name-style="western"><surname>Hsu</surname><given-names>CC</given-names> </name><name name-style="western"><surname>Lin</surname><given-names>MH</given-names> </name><name name-style="western"><surname>Sung</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Kuo</surname><given-names>TH</given-names> </name></person-group><article-title>Healthcare utilization and expenditure among individuals with end-stage kidney disease in Taiwan</article-title><source>J Formos Med Assoc</source><year>2022</year><month>02</month><volume>121 (Suppl 1)</volume><fpage>S47</fpage><lpage>S55</lpage><pub-id pub-id-type="doi">10.1016/j.jfma.2021.12.010</pub-id><pub-id pub-id-type="medline">34980549</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>Megari</surname><given-names>K</given-names> </name></person-group><article-title>Quality of life in chronic disease patients</article-title><source>Health Psychol Res</source><year>2013</year><month>09</month><day>24</day><volume>1</volume><issue>3</issue><fpage>e27</fpage><pub-id pub-id-type="doi">10.4081/hpr.2013.e27</pub-id><pub-id pub-id-type="medline">26973912</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>Neale</surname><given-names>EP</given-names> </name><name name-style="western"><surname>Rosario</surname><given-names>VD</given-names> </name><name name-style="western"><surname>Probst</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Beck</surname><given-names>E</given-names> </name><name name-style="western"><surname>Tran</surname><given-names>TB</given-names> </name><name name-style="western"><surname>Lambert</surname><given-names>K</given-names> </name></person-group><article-title>Lifestyle interventions, kidney disease progression, and quality of life: a systematic review and meta-analysis</article-title><source>Kidney Med</source><year>2023</year><month>06</month><volume>5</volume><issue>6</issue><fpage>100643</fpage><pub-id pub-id-type="doi">10.1016/j.xkme.2023.100643</pub-id><pub-id pub-id-type="medline">37235039</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>Chen</surname><given-names>J</given-names> </name><name name-style="western"><surname>Fowler</surname><given-names>KJ</given-names> </name><name name-style="western"><surname>Grams</surname><given-names>ME</given-names> </name></person-group><article-title>Knowledge is power: patient education as a tool for patient activation</article-title><source>Am J Kidney Dis</source><year>2020</year><month>08</month><volume>76</volume><issue>2</issue><fpage>163</fpage><lpage>165</lpage><pub-id pub-id-type="doi">10.1053/j.ajkd.2020.03.012</pub-id><pub-id pub-id-type="medline">32560974</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>Hirsch</surname><given-names>JS</given-names> </name><name name-style="western"><surname>Danna</surname><given-names>SC</given-names> </name><name name-style="western"><surname>Desai</surname><given-names>N</given-names> </name><etal/></person-group><article-title>Optimizing care delivery in patients with chronic kidney disease in the United States: proceedings of a multidisciplinary roundtable discussion and literature review</article-title><source>J Clin Med</source><year>2024</year><month>02</month><day>20</day><volume>13</volume><issue>5</issue><fpage>1206</fpage><pub-id pub-id-type="doi">10.3390/jcm13051206</pub-id><pub-id pub-id-type="medline">38592013</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>Wen</surname><given-names>CP</given-names> </name><name name-style="western"><surname>Cheng</surname><given-names>TYD</given-names> </name><name name-style="western"><surname>Tsai</surname><given-names>MK</given-names> </name><etal/></person-group><article-title>All-cause mortality attributable to chronic kidney disease: a prospective cohort study based on 462 293 adults in Taiwan</article-title><source>Lancet</source><year>2008</year><month>06</month><day>28</day><volume>371</volume><issue>9631</issue><fpage>2173</fpage><lpage>2182</lpage><pub-id pub-id-type="doi">10.1016/S0140-6736(08)60952-6</pub-id><pub-id pub-id-type="medline">18586172</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>Chao</surname><given-names>S</given-names> </name><name name-style="western"><surname>Yen</surname><given-names>M</given-names> </name><name name-style="western"><surname>Lin</surname><given-names>TC</given-names> </name><name name-style="western"><surname>Sung</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>MC</given-names> </name><name name-style="western"><surname>Hung</surname><given-names>SY</given-names> </name></person-group><article-title>Psychometric Properties of the Kidney Disease Quality of Life-36 Questionnaire (KDQOL-36</article-title><source>West J Nurs Res</source><year>2016</year><month>08</month><volume>38</volume><issue>8</issue><fpage>1067</fpage><lpage>1082</lpage><pub-id pub-id-type="doi">10.1177/0193945916640765</pub-id><pub-id pub-id-type="medline">27026384</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>Chen</surname><given-names>TK</given-names> </name><name name-style="western"><surname>Knicely</surname><given-names>DH</given-names> </name><name name-style="western"><surname>Grams</surname><given-names>ME</given-names> </name></person-group><article-title>Chronic kidney disease diagnosis and management: a review</article-title><source>JAMA</source><year>2019</year><month>10</month><day>1</day><volume>322</volume><issue>13</issue><fpage>1294</fpage><lpage>1304</lpage><pub-id pub-id-type="doi">10.1001/jama.2019.14745</pub-id><pub-id pub-id-type="medline">31573641</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>Krishnamurthy</surname><given-names>S</given-names> </name><name name-style="western"><surname>Ks</surname><given-names>K</given-names> </name><name name-style="western"><surname>Dovgan</surname><given-names>E</given-names> </name><etal/></person-group><article-title>Machine learning prediction models for chronic kidney disease using national health insurance claim data in Taiwan</article-title><source>Healthcare (Basel)</source><year>2021</year><month>05</month><day>7</day><volume>9</volume><issue>5</issue><fpage>546</fpage><pub-id pub-id-type="doi">10.3390/healthcare9050546</pub-id><pub-id pub-id-type="medline">34067129</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>Daniels</surname><given-names>K</given-names> </name><name name-style="western"><surname>Bonnech&#x00E8;re</surname><given-names>B</given-names> </name></person-group><article-title>Harnessing digital health interventions to bridge the gap in prevention for older adults</article-title><source>Front Public Health</source><year>2023</year><volume>11</volume><fpage>1281923</fpage><pub-id pub-id-type="doi">10.3389/fpubh.2023.1281923</pub-id><pub-id pub-id-type="medline">38259780</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="web"><article-title>Classification of digital health interventions v10: a shared language to describe the uses of digital technology for health</article-title><source>World Health Organization</source><year>2018</year><access-date>2025-11-12</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.who.int/publications/i/item/WHO-RHR-18.06">https://www.who.int/publications/i/item/WHO-RHR-18.06</ext-link></comment></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>Jeddi</surname><given-names>FR</given-names> </name><name name-style="western"><surname>Nabovati</surname><given-names>E</given-names> </name><name name-style="western"><surname>Amirazodi</surname><given-names>S</given-names> </name></person-group><article-title>Features and effects of information technology-based interventions to improve self-management in chronic kidney disease patients: a systematic review of the literature</article-title><source>J Med Syst</source><year>2017</year><month>09</month><day>18</day><volume>41</volume><issue>11</issue><fpage>170</fpage><pub-id pub-id-type="doi">10.1007/s10916-017-0820-6</pub-id><pub-id pub-id-type="medline">28920174</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>Ren</surname><given-names>Q</given-names> </name><name name-style="western"><surname>Lian</surname><given-names>M</given-names> </name><name name-style="western"><surname>Liu</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Thomas-Hawkins</surname><given-names>C</given-names> </name><name name-style="western"><surname>Zhu</surname><given-names>L</given-names> </name><name name-style="western"><surname>Shen</surname><given-names>Q</given-names> </name></person-group><article-title>Effects of a transtheoretical model-based WeChat health education programme on self-management among haemodialysis patients: a longitudinal experimental intervention study</article-title><source>J Adv Nurs</source><year>2019</year><month>12</month><volume>75</volume><issue>12</issue><fpage>3554</fpage><lpage>3565</lpage><pub-id pub-id-type="doi">10.1111/jan.14182</pub-id><pub-id pub-id-type="medline">31441525</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>Hsiao</surname><given-names>PN</given-names> </name><name name-style="western"><surname>Hsu</surname><given-names>P</given-names> </name><name name-style="western"><surname>Hsiao</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>TH</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>CL</given-names> </name></person-group><article-title>Project to increase the usage rate of iCKD application mobile healthcare on chronic kidney disease patients</article-title><source>Hu Li Za Zhi</source><year>2019</year><month>02</month><volume>66</volume><issue>1</issue><fpage>84</fpage><lpage>92</lpage><pub-id pub-id-type="doi">10.6224/JN.201902_66(1).10</pub-id><pub-id pub-id-type="medline">30648248</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>Yang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>H</given-names> </name><name name-style="western"><surname>Qazi</surname><given-names>H</given-names> </name><name name-style="western"><surname>Morita</surname><given-names>PP</given-names> </name></person-group><article-title>Intervention and evaluation of mobile health technologies in management of patients undergoing chronic dialysis: scoping review</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>04</month><day>3</day><volume>8</volume><issue>4</issue><fpage>e15549</fpage><pub-id pub-id-type="doi">10.2196/15549</pub-id><pub-id pub-id-type="medline">32242823</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>Donald</surname><given-names>M</given-names> </name><name name-style="western"><surname>Beanlands</surname><given-names>H</given-names> </name><name name-style="western"><surname>Straus</surname><given-names>S</given-names> </name><etal/></person-group><article-title>An eHealth self-management intervention for adults with chronic kidney disease, My Kidneys My Health: a mixed-methods study</article-title><source>CMAJ Open</source><year>2022</year><volume>10</volume><issue>3</issue><fpage>E746</fpage><lpage>E754</lpage><pub-id pub-id-type="doi">10.9778/cmajo.20210332</pub-id><pub-id pub-id-type="medline">35973709</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="web"><article-title>LINE Business Guide (Summary) v11</article-title><source>LY Corporation</source><year>2024</year><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.linebiz.com/sites/default/files/media/jp-en/download/EN_LINE%20Business%20Guide_202304-09_summary.pdf">https://www.linebiz.com/sites/default/files/media/jp-en/download/EN_LINE%20Business%20Guide_202304-09_summary.pdf</ext-link></comment></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="web"><article-title>2022 Taiwan Internet Report</article-title><source>Taiwan Network Information Center</source><year>2022</year><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://report.twnic.tw/2022">https://report.twnic.tw/2022</ext-link></comment></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>Li</surname><given-names>WY</given-names> </name><name name-style="western"><surname>Chiu</surname><given-names>FC</given-names> </name><name name-style="western"><surname>Zeng</surname><given-names>JK</given-names> </name><etal/></person-group><article-title>Mobile health app with social media to support self-management for patients with chronic kidney disease: prospective randomized controlled study</article-title><source>J Med Internet Res</source><year>2020</year><month>12</month><day>15</day><volume>22</volume><issue>12</issue><fpage>e19452</fpage><pub-id pub-id-type="doi">10.2196/19452</pub-id><pub-id pub-id-type="medline">33320101</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>Chen</surname><given-names>NJ</given-names> </name><name name-style="western"><surname>Huang</surname><given-names>CM</given-names> </name><name name-style="western"><surname>Fan</surname><given-names>CC</given-names> </name><etal/></person-group><article-title>User evaluation of a chat-based instant messaging support health education program for patients with chronic kidney disease: preliminary findings of a formative study</article-title><source>JMIR Form Res</source><year>2023</year><month>09</month><day>19</day><volume>7</volume><fpage>e45484</fpage><pub-id pub-id-type="doi">10.2196/45484</pub-id><pub-id pub-id-type="medline">37725429</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>Kushniruk</surname><given-names>AW</given-names> </name><name name-style="western"><surname>Patel</surname><given-names>VL</given-names> </name></person-group><article-title>Cognitive and usability engineering methods for the evaluation of clinical information systems</article-title><source>J Biomed Inform</source><year>2004</year><month>02</month><volume>37</volume><issue>1</issue><fpage>56</fpage><lpage>76</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2004.01.003</pub-id><pub-id pub-id-type="medline">15016386</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>Serrador</surname><given-names>P</given-names> </name><name name-style="western"><surname>Pinto</surname><given-names>JK</given-names> </name></person-group><article-title>Does Agile work? A quantitative analysis of agile project success</article-title><source>Int J Proj Manag</source><year>2015</year><month>07</month><volume>33</volume><issue>5</issue><fpage>1040</fpage><lpage>1051</lpage><pub-id pub-id-type="doi">10.1016/j.ijproman.2015.01.006</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="web"><article-title>&#x7528;LINE&#x5B98;&#x65B9;&#x5E33;&#x865F;&#x505A;&#x5230;&#x7D04;&#x8A3A;&#x63D0;&#x9192;-&#x91AB;&#x7642;&#x696D; [Using LINE Official Account for appointment reminders&#x2014;medical industry]</article-title><source>LY Corporation</source><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://tw.linebiz.com/smb/industry-application/medical/">https://tw.linebiz.com/smb/industry-application/medical/</ext-link></comment></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="web"><article-title>AppSheet: the fastest way to build apps and automate work</article-title><source>Google</source><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://about.appsheet.com/home/">https://about.appsheet.com/home/</ext-link></comment></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Nielsen</surname><given-names>J</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Nielsen</surname><given-names>J</given-names> </name><name name-style="western"><surname>Mack</surname><given-names>RL</given-names> </name></person-group><article-title>Heuristic evaluation</article-title><source>Usability Inspection Methods</source><year>1994</year><publisher-name>John Wiley &#x0026; Sons</publisher-name><fpage>25</fpage><lpage>62</lpage><pub-id pub-id-type="other">978-0471018773</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Moran</surname><given-names>K</given-names> </name><name name-style="western"><surname>Gordon</surname><given-names>K</given-names> </name></person-group><article-title>How to conduct a heuristic evaluation</article-title><source>Nielsen Norman Group</source><year>2023</year><month>06</month><day>25</day><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/">https://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/</ext-link></comment></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Nielsen</surname><given-names>J</given-names> </name></person-group><article-title>10 usability heuristics for user interface design</article-title><source>Nielsen Norman Group</source><year>1994</year><month>04</month><day>24</day><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/ten-usability-heuristics/">https://www.nngroup.com/articles/ten-usability-heuristics/</ext-link></comment></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Donald</surname><given-names>M</given-names> </name><name name-style="western"><surname>Beanlands</surname><given-names>H</given-names> </name><name name-style="western"><surname>Straus</surname><given-names>SE</given-names> </name><etal/></person-group><article-title>A web-based self-management support prototype for adults with chronic kidney disease (My Kidneys My Health): co-design and usability testing</article-title><source>JMIR Form Res</source><year>2021</year><month>02</month><day>9</day><volume>5</volume><issue>2</issue><fpage>e22220</fpage><pub-id pub-id-type="doi">10.2196/22220</pub-id><pub-id pub-id-type="medline">33560245</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Moran</surname><given-names>K</given-names> </name></person-group><article-title>Usability testing 101</article-title><source>Nielsen Norman Group</source><year>2019</year><month>12</month><day>1</day><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/usability-testing-101/">https://www.nngroup.com/articles/usability-testing-101/</ext-link></comment></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Nielsen</surname><given-names>J</given-names> </name></person-group><article-title>Why you only need to test with 5 users</article-title><source>Nielsen Norman Group</source><year>2000</year><month>03</month><day>18</day><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/</ext-link></comment></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lewis</surname><given-names>JR</given-names> </name></person-group><article-title>IBM computer usability satisfaction questionnaires: psychometric evaluation and instructions for use</article-title><source>Int J Hum Comput Interact</source><year>1995</year><month>01</month><volume>7</volume><issue>1</issue><fpage>57</fpage><lpage>78</lpage><pub-id pub-id-type="doi">10.1080/10447319509526110</pub-id></nlm-citation></ref><ref id="ref33"><label>33</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><person-group person-group-type="editor"><name name-style="western"><surname>Jordan</surname><given-names>PW</given-names> </name></person-group><article-title>SUS&#x2014;a quick and dirty usability scale</article-title><source>Usability Evaluation in Industry</source><year>1996</year><publisher-name>Taylor &#x0026; Francis</publisher-name><fpage>189</fpage><lpage>194</lpage><pub-id pub-id-type="other">978-0748404605</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Sauro</surname><given-names>J</given-names> </name></person-group><article-title>Measuring usability with the System Usability Scale (SUS)</article-title><source>Measuring U</source><year>2011</year><month>02</month><day>3</day><access-date>2024-04-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://measuringu.com/sus/">https://measuringu.com/sus/</ext-link></comment></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>Wang</surname><given-names>SL</given-names> </name><name name-style="western"><surname>Kung</surname><given-names>LF</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>TH</given-names> </name><name name-style="western"><surname>Hsiao</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Hsiao</surname><given-names>PN</given-names> </name><name name-style="western"><surname>Chiou</surname><given-names>CJ</given-names> </name></person-group><article-title>Construction and validation of a chronic kidney disease self-care scale</article-title><source>Hu Li Za Zhi</source><year>2016</year><month>08</month><volume>63</volume><issue>4</issue><fpage>90</fpage><lpage>99</lpage><pub-id pub-id-type="doi">10.6224/JN.63.4.90</pub-id><pub-id pub-id-type="medline">27492299</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lin</surname><given-names>CY</given-names> </name><name name-style="western"><surname>Chang</surname><given-names>JH</given-names> </name><name name-style="western"><surname>Shih</surname><given-names>CD</given-names> </name></person-group><article-title>Assessment of medication adherence in elderly residents in Pingtung City</article-title><source>J Taiwan Pharm</source><year>2019</year><access-date>2025-04-15</access-date><volume>35</volume><issue>1</issue><comment><ext-link ext-link-type="uri" xlink:href="https://jtp.taiwan-pharma.org.tw/138/021.html">https://jtp.taiwan-pharma.org.tw/138/021.html</ext-link></comment></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Norman</surname><given-names>D</given-names> </name></person-group><article-title>The psychopathology of everyday things</article-title><source>The Design of Everyday Things: Revised and Expanded</source><year>2013</year><publisher-name>Basic Books</publisher-name><fpage>1</fpage><lpage>34</lpage><pub-id pub-id-type="other">978-0465050659</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="web"><article-title>Taiwan internet report</article-title><source>Taiwan Network Information Center</source><year>2023</year><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://report.twnic.tw/2023">https://report.twnic.tw/2023</ext-link></comment></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="web"><article-title>Demand characteristics</article-title><source>Interaction Design Foundation</source><year>2015</year><month>07</month><day>5</day><access-date>2025-04-15</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.interaction-design.org/literature/book/the-glossary-of-human-computer-interaction/demand-characteristics">https://www.interaction-design.org/literature/book/the-glossary-of-human-computer-interaction/demand-characteristics</ext-link></comment></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Orne</surname><given-names>MT</given-names> </name><name name-style="western"><surname>Whitehouse</surname><given-names>WG</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Kazdin</surname><given-names>AE</given-names> </name></person-group><article-title>Demand characteristics</article-title><source>Encyclopedia of Psychology</source><year>2000</year><publisher-name>American Psychological Association and Oxford University Press</publisher-name><fpage>469</fpage><lpage>470</lpage><pub-id pub-id-type="doi">10.1037/10517-173</pub-id></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="book"><person-group person-group-type="editor"><name name-style="western"><surname>Ragnedda</surname><given-names>M</given-names> </name><name name-style="western"><surname>Muschert</surname><given-names>GW</given-names> </name></person-group><source>The Digital Divide: The Internet and Social Inequality in International Perspective</source><year>2013</year><edition>1</edition><publisher-name>Routledge</publisher-name><pub-id pub-id-type="doi">10.4324/9780203069769</pub-id><pub-id pub-id-type="other">978-0203069769</pub-id></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Banbury</surname><given-names>A</given-names> </name><name name-style="western"><surname>Nancarrow</surname><given-names>S</given-names> </name><name name-style="western"><surname>Dart</surname><given-names>J</given-names> </name><name name-style="western"><surname>Gray</surname><given-names>L</given-names> </name><name name-style="western"><surname>Parkinson</surname><given-names>L</given-names> </name></person-group><article-title>Telehealth interventions delivering home-based support group videoconferencing: systematic review</article-title><source>J Med Internet Res</source><year>2018</year><month>02</month><day>2</day><volume>20</volume><issue>2</issue><fpage>e25</fpage><pub-id pub-id-type="doi">10.2196/jmir.8090</pub-id><pub-id pub-id-type="medline">29396387</pub-id></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Steele Gray</surname><given-names>C</given-names> </name><name name-style="western"><surname>Gill</surname><given-names>A</given-names> </name><name name-style="western"><surname>Khan</surname><given-names>AI</given-names> </name><name name-style="western"><surname>Hans</surname><given-names>PK</given-names> </name><name name-style="western"><surname>Kuluski</surname><given-names>K</given-names> </name><name name-style="western"><surname>Cott</surname><given-names>C</given-names> </name></person-group><article-title>The electronic patient reported outcome tool: testing usability and feasibility of a mobile app and portal to support care for patients with complex chronic disease and disability in primary care settings</article-title><source>JMIR Mhealth Uhealth</source><year>2016</year><month>06</month><day>2</day><volume>4</volume><issue>2</issue><fpage>e58</fpage><pub-id pub-id-type="doi">10.2196/mhealth.5331</pub-id><pub-id pub-id-type="medline">27256035</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>User manual.</p><media xlink:href="humanfactors_v12i1e73935_app1.pdf" xlink:title="PDF File, 2359 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Phase 1 user feedback form.</p><media xlink:href="humanfactors_v12i1e73935_app2.pdf" xlink:title="PDF File, 232 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Phase 3 usability testing instrument.</p><media xlink:href="humanfactors_v12i1e73935_app3.pdf" xlink:title="PDF File, 268 KB"/></supplementary-material><supplementary-material id="app4"><label>Multimedia Appendix 4</label><p>Complete dataset and summary tables.</p><media xlink:href="humanfactors_v12i1e73935_app4.xlsx" xlink:title="XLSX File, 39 KB"/></supplementary-material></app-group></back></article>