<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</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">v11i1e57033</article-id>
      <article-id pub-id-type="pmid">39259964</article-id>
      <article-id pub-id-type="doi">10.2196/57033</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>User Experience of a Large-Scale Smartphone-Based Observational Study in Multiple Sclerosis: Global, Open-Access, Digital-Only Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Adapa</surname>
            <given-names>Karthik</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Figueredo</surname>
            <given-names>Grazziela</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Ochoa-Zezzatti</surname>
            <given-names>Carlos</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Galati</surname>
            <given-names>Adriano</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>F Hoffmann-La Roche Ltd</institution>
            <addr-line>Grenzacherstrasse 124</addr-line>
            <addr-line>Basel, 4070</addr-line>
            <country>Switzerland</country>
            <phone>41 61 682 25 79</phone>
            <email>adriano.galati@roche.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0006-9661-899X</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Kriara</surname>
            <given-names>Lito</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9159-0469</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Lindemann</surname>
            <given-names>Michael</given-names>
          </name>
          <degrees>MBA, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1010-3890</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Lehner</surname>
            <given-names>Rea</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6497-2875</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Jones</surname>
            <given-names>JB</given-names>
          </name>
          <degrees>MBA, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8752-877X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>F Hoffmann-La Roche Ltd</institution>
        <addr-line>Basel</addr-line>
        <country>Switzerland</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Sutter Health Center for Health Systems Research</institution>
        <addr-line>Walnut Creek, CA</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Adriano Galati <email>adriano.galati@roche.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>11</day>
        <month>9</month>
        <year>2024</year>
      </pub-date>
      <volume>11</volume>
      <elocation-id>e57033</elocation-id>
      <history>
        <date date-type="received">
          <day>8</day>
          <month>2</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>29</day>
          <month>4</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>17</day>
          <month>6</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>2</day>
          <month>7</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Adriano Galati, Lito Kriara, Michael Lindemann, Rea Lehner, JB Jones. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 11.09.2024.</copyright-statement>
      <copyright-year>2024</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 (https://creativecommons.org/licenses/by/4.0/), 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 https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2024/1/e57033" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The Floodlight Open app is a digital health technology tool (DHTT) that comprises remote, smartphone sensor–based tests (<italic>daily activities</italic>) for assessing symptoms of multiple sclerosis (MS). User acquisition, engagement, and retention remain a barrier to successfully deploying such tools.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to quantitatively and qualitatively investigate key user experience (UX) factors associated with the Floodlight Open app.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Floodlight Open is a global, open-access, digital-only study designed to understand the drivers and barriers in deploying a DHTT in a naturalistic setting without supervision and onboarding by a clinician. Daily activities included tests assessing cognition (Information Processing Speed and Information Processing Speed Digit–Digit), hand-motor function (Pinching Test and Draw a Shape Test), and postural stability and gait (Static Balance Test, U-Turn Test, and Two-Minute Walk Test [2MWT]). All daily activities except the 2MWT were taken in a fixed sequence. Qualitative UX was studied through semistructured interviews in a substudy of US participants with MS. The quantitative UX analysis investigated the impact of new UX design features on user engagement and retention in US participants for 3 separate test series: all daily activities included in the fixed sequence (DA), all daily activities included in the fixed sequence except the Static Balance Test and U-Turn Test (DA<sub>x</sub>), and the 2MWT.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The qualitative UX substudy (N=22) revealed the need for 2 new UX design features: a more seamless user journey during the activation process that eliminates the requirement of switching back and forth between the app and the email that the participants received upon registration, and configurable reminders and push notifications to help plan and remind the participants to complete their daily activities. Both UX design features were assessed in the quantitative UX analysis. Introducing the more seamless user journey (original user journey: n=608; more seamless user journey: n=481) improved the conversion rate of participants who enrolled in the study and proceeded to successfully activate the app from 53.9% (328/608) to 74.6% (359/481). Introducing reminders and push notifications (with reminders and notifications: n=350; without reminders and notifications: n=172) improved continuous usage time (proportion of participants with ≥3 consecutive days of usage: DA and DA<sub>x</sub>: ~30% vs ~12%; 2MWT: ~30% vs ~20%); test completion rates (maximum number of test series completed: DA: 279 vs 64; DA<sub>x</sub>: 283 vs 126; 2MWT: 302 vs 76); and user retention rates (at day 30: DA: 53/172, 30.8% vs 34/350, 9.7%; DA<sub>x</sub>: 53/172, 30.8% vs 60/350, 17.1%; 2MWT: 39/172, 22.6% vs 22/350, 6.2%). Inactivity times remained comparable.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The remote assessment of MS with DHTTs is a relatively nascent but growing field of research. The continued assessment and improvement of UX design features can play a crucial role in the successful long-term adoption of new DHTTs.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>smartphone</kwd>
        <kwd>multiple sclerosis</kwd>
        <kwd>user experience</kwd>
        <kwd>retention</kwd>
        <kwd>digital health</kwd>
        <kwd>digital health technology</kwd>
        <kwd>mobile phone</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Traditionally, multiple sclerosis (MS) has been categorized as having a relapsing-remitting or progressive course. However, recent work shed light on an underlying insidious progression, or a progression that is independent of relapses, even in patients previously thought to have a relapsing-remitting disease [<xref ref-type="bibr" rid="ref1">1</xref>]. Therefore, minimizing or even eliminating progression is one of the goals of MS disease management. To achieve this goal, sensitive measures of MS-related functional ability are needed that can be frequently administered with minimal burden to the patient [<xref ref-type="bibr" rid="ref2">2</xref>]. Here, digital health technology tools (DHTTs) such as smartphone sensor–based tests offer a new, promising strategy [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. By taking advantage of the large variety of embedded sensors, smartphones enable the remote assessment of several functional domains affected by MS without supervision by a clinician [<xref ref-type="bibr" rid="ref3">3</xref>]. However, user retention remains a barrier to the successful deployment of such DHTTs [<xref ref-type="bibr" rid="ref6">6</xref>].</p>
        <p>Assessments of user experience (UX) should, therefore, be considered when designing DHTTs [<xref ref-type="bibr" rid="ref7">7</xref>]. They have attracted increasing attention, as they provide important insights to enhance usability, engagement, perception, and satisfaction [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. With different UX designs available, it is important to keep in mind that their effectiveness depends on both the intended users and the environment in which they are being used. Hence, a comprehensive assessment of UX should include the study of both qualitative and quantitative UX in different environments for an extended period. The primary focus of qualitative UX assessments is to characterize the individual user’s experiences with the DHHT and to elucidate fine-grained aspects of why and how users engage with it [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. Quantitative UX assessments, by comparison, provide strong indicators of the duration and frequency of user engagement and retention and are typically conducted in larger cohorts.</p>
      </sec>
      <sec>
        <title>Aims</title>
        <p>Here, we present a qualitative and quantitative UX analysis of the Floodlight Open app (<xref rid="figure1" ref-type="fig">Figure 1</xref>). The app comprises patient-reported outcomes and smartphone sensor–based tests that assess mood, cognition, hand-motor function, postural stability and gait, and mobility levels [<xref ref-type="bibr" rid="ref15">15</xref>]. It was deployed in Floodlight Open, a global, open-access, digital-only study that was designed to understand the drivers and barriers in the deployment of the app in a naturalistic setting without supervision and onboarding by a clinician, in a broad, multinational study cohort [<xref ref-type="bibr" rid="ref15">15</xref>]. The UX analyses presented here allow us to gain a better understanding of the participants’ behavior with the Floodlight Open app. This will help make informed UX design decisions to improve engagement with the Floodlight technology. Qualitative UX is assessed through semistructured interviews conducted with a subset of US participants with MS [<xref ref-type="bibr" rid="ref16">16</xref>] to identify important elements that could improve UX and user engagement. In addition, quantitative UX is assessed by evaluating the impact of UX design changes, which were motivated by the learnings from the qualitative UX analysis, on user engagement and retention using data collected from Floodlight Open.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Learnings from the quantitative user experience (UX) analysis led to the implementation of new UX design features, such as a more seamless user journey from registration through the activation of the Floodlight Open app, configurable reminders, and push notifications. The impact of these new UX design features was assessed in the quantitative UX analysis.</p>
          </caption>
          <graphic xlink:href="humanfactors_v11i1e57033_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Participants and Study Design</title>
        <p>Floodlight Open’s full study design and inclusion and exclusion criteria have been previously reported [<xref ref-type="bibr" rid="ref15">15</xref>]. Adults with or without MS who owned a suitable iOS (Apple Inc) or Android (Google LLC) smartphone and resided in 1 of the 17 participating countries were permitted to take part. The MS status was self-declared by the participants. To join Floodlight Open, participants first registered on the Floodlight Open web portal and completed the informed e-consent process. After successfully completing these 2 steps, each participant received their personal Floodlight Open unique identifier (FLO ID) and an activation code (ie, an activation token [<xref ref-type="bibr" rid="ref15">15</xref>]) via email. Both were required to activate the Floodlight Open app on the participant’s personal smartphone device. The email also provided a link to the Floodlight Open web portal, where participants could request a new activation code (the activation code was valid for 48 hours, after which it expired), access their account to update their profile, view their results, or withdraw from the study.</p>
        <p>After the activation of the Floodlight Open app, several tests, or assessments, were made available to the participants. These included a patient-reported outcome assessing the participants’ mood (Daily Mood Questionnaire [DMQ] [<xref ref-type="bibr" rid="ref15">15</xref>]) and a series of smartphone sensor–based active tests (ie, tests that require active input from the user) measuring cognition (Information Processing Speed [IPS] [<xref ref-type="bibr" rid="ref15">15</xref>] and IPS Digit–Digit [<xref ref-type="bibr" rid="ref15">15</xref>]); hand-motor function (Pinching Test [PT] [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref17">17</xref>] and Draw a Shape Test [DaS] [<xref ref-type="bibr" rid="ref15">15</xref>]); and postural stability and gait (Static Balance Test [SBT] [<xref ref-type="bibr" rid="ref15">15</xref>], U-Turn Test [UTT] [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref18">18</xref>], and Two-Minute Walk Test [2MWT] [<xref ref-type="bibr" rid="ref15">15</xref>]; <xref rid="figure2" ref-type="fig">Figure 2</xref>).</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Screenshots from the Floodlight Open app. The dashboard (A) enables participants to set reminders by tapping the bell-shaped reminder icon in the bottom right corner. Participants can self-administer smartphone–based tests to assess cognition (Information Processing Speed [IPS; B] and IPS Digit–Digit), hand-motor function (Pinching Test and Draw a Shape Test [DaS; C]), and gait and postural stability (Static Balance Test, U-Turn Test, and 2-Minute Walk Test [2MWT; D]). The results of these tests are provided on the results screen (E).</p>
          </caption>
          <graphic xlink:href="humanfactors_v11i1e57033_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>In addition, data on mobility level were passively collected without requiring input from the user (<italic>passive monitoring</italic>) through life-space measurement [<xref ref-type="bibr" rid="ref15">15</xref>], which measured the distance between the 2 farthest GPS coordinates detected during the day that were at least 500 m apart, resulting in 1 measurement per day. Since this passive monitoring does not require any active input from the user, it is not included in our UX analyses.</p>
        <p>The DMQ and all active tests except the 2MWT were administered in a predefined, fixed sequence comprising the daily activities. The DMQ was administered first, followed by the IPS, IPS Digit–Digit, PT, DaS, SBT, and UTT. The 2MWT was administered separately from these daily activities, as this test required the participant to walk in a straight line for 2 minutes, which may not always be possible at the time of taking the other active tests. The tests could be taken up to once a week (IPS) or once a day (all other tests), but the actual test frequency was not systematically enforced. For example, the UTT, SBT, and 2MWT could be skipped if participants determined that the conditions for safe execution, including environmental and physical factors, could not be met that day.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>Data collected with the Floodlight Open app were encrypted and electronically stored on 2 specific, secure cloud databases, which were made publicly available for the duration of the study and maintained by the study initiator. To ensure confidentiality, all participant information was pseudonymized through association with the personal FLO ID. Furthermore, no personal identifiable information was collected while the participants executed the Floodlight Open tests. This meant that GPS coordinates were obfuscated and excluded from the public data set to protect participants’ privacy.</p>
        <p>The protocol, informed e-consent forms, and relevant supporting information were reviewed and approved by the appointed central institutional review boards or ethics committees before the study was initiated in each participating country, as applicable, in accordance with each country’s regulatory requirements [<xref ref-type="bibr" rid="ref15">15</xref>]. The institutional review board for the United States was the Western Institutional Review Board in Puyallup, Washington (approval: 20180617).</p>
      </sec>
      <sec>
        <title>Qualitative UX Analysis</title>
        <p>The qualitative UX substudy was conducted by a health care delivery network (Sutter Health) in a subset of US participants with MS who took part in Floodlight Open and agreed to download the app and use it daily for 30 days [<xref ref-type="bibr" rid="ref16">16</xref>]. This substudy aimed at elucidating finer-grained aspects of why and how users engage with the Floodlight Open app in a particular manner and at providing information on UX design features that could improve UX and user engagement. Individual, semistructured interviews were conducted to gain insights into the participants’ experiences with the Floodlight Open app and the perceived benefits thereof (<xref ref-type="table" rid="table1">Table 1</xref>). The use of individual interviews offered privacy and enabled the exploration of each participant’s interaction with the app. A multifaceted recruitment strategy was applied to involve participants of a broad age range to combine the experiences of the tech-savvy younger generation with that of the older generation. Most participants were using their smartphone and their computer daily. No preferential sampling of participants with either negative or positive experiences was applied. Any duration of use of the Floodlight Open app was of value because discontinued use and negative experiences can provide valuable insights and complement data from persistent participants.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Interview guide for the qualitative UX<sup>a</sup> analysis.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="490"/>
            <col width="0"/>
            <col width="480"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Question</td>
                <td>Elaboration questions</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4">
                  <bold>Technology acceptance</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Were you able to download the app to your phone and get it working?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>How was that process?</p>
                    </list-item>
                    <list-item>
                      <p>Was there anything you found particularly easy, or hard or confusing about the process?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>We asked people taking part in the study to use the app for 30 days. For about how many days did you use the app?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>0, 1-7, 8-14, 14-21, 22-29, 30+, or don’t remember</p>
                    </list-item>
                    <list-item>
                      <p>If answer is “0” or “30+,” skip the next question.</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                </td>
                <td>What made you decide to either not use it or stop using it after less than 30 days?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Probe to identify root cause and any efforts made to overcome:</p>
                      <list list-type="bullet">
                        <list-item>
                          <p>App related (technical problems, overall demand in terms of time or frequency, or understandability)</p>
                        </list-item>
                        <list-item>
                          <p>Phone related (data, service, or access)</p>
                        </list-item>
                        <list-item>
                          <p>User related (general willingness, utility, or physical or emotional ability)</p>
                        </list-item>
                      </list>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                </td>
                <td>Before you started using the app, did you feel like you had a good idea about what it was designed to do?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Did you have any questions or concerns?</p>
                    </list-item>
                    <list-item>
                      <p>What were they?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Experience of use</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>How well could you see the information on the screen?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Was there anything that was hard for you to see?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>How easy was it to understand the information and prompts?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Was there anything that was hard to understand?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>How well did using the app fit into your life, such as the timing and frequency of prompts, and time it took to respond?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Not applicable</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Perception</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Did tracking information about MS<sup>b</sup> on a regular basis using this app teach you anything new about your health or give you a better sense of how you’re doing?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Why or why not?</p>
                    </list-item>
                    <list-item>
                      <p>Did you do/think/feel anything different based on what you learned?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Do you think this is an application you can use on daily basis?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Why or why not?</p>
                    </list-item>
                    <list-item>
                      <p>If not daily, what do you think is the optimal frequency of use?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>How would you feel about being prompted by the app on a daily basis to do tasks or answer questions related to MS?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>If not daily, what do you think is the optimal frequency of reminders and notification?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Did you share the information from the app (either directly or what you learned) with anyone else?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Do you mind telling me what you shared?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Of the information collected by the app, what would you want to share with your doctor?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>What is valuable about this information?</p>
                    </list-item>
                    <list-item>
                      <p>How would sharing it impact your appointment in terms of your discussions, care or treatment?</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Is there anything else you would like to add about your experience tracking MS on a daily basis using your phone?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Not applicable</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>General health questions: disease severity and duration</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Before we end our interview I have a few general questions about your health and computer use. What year were you diagnosed with MS?</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Not applicable</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>What type of MS do you have at this time?</td>
                <td colspan="2">
                  <list list-type="order">
                    <list-item>
                      <p>Relapsing-Remitting MS (RRMS)</p>
                    </list-item>
                    <list-item>
                      <p>Secondary-Progressive MS (SPMS)</p>
                    </list-item>
                    <list-item>
                      <p>Primary-Progressive MS (PPMS)</p>
                    </list-item>
                    <list-item>
                      <p>Progressive-Relapsing MS (PRMS)</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Technology literacy</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Last question. I’ll give you the question and then I’ll read a list of options for your response. How often do you use a computer?</td>
                <td colspan="2">
                  <list list-type="order">
                    <list-item>
                      <p>Everyday</p>
                    </list-item>
                    <list-item>
                      <p>At least once a week but not everyday</p>
                    </list-item>
                    <list-item>
                      <p>Less than once a week but more than once a month</p>
                    </list-item>
                    <list-item>
                      <p>Less than once a month</p>
                    </list-item>
                    <list-item>
                      <p>Never</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>UX: user experience.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>MS: multiple sclerosis.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Semistructured interviews were conducted via phone by a trained interviewer, with 2 attempts made to reach each participant. The interviews lasted between 15 and 20 minutes and were audiotaped and fully transcribed for further analysis. A reductionist approach was applied to deconstruct implicit and explicit responses into manageable variables. The qualitative paradigm was crucial to appreciating, observing, and deducing participants’ experiences [<xref ref-type="bibr" rid="ref19">19</xref>]. Through an inductive analysis of the data collected, the common needs of the participants were identified, which should be considered to improve the UX and to develop preliminary conclusions on the need for specific UX features.</p>
      </sec>
      <sec>
        <title>Quantitative UX Analysis</title>
        <sec>
          <title>Participants</title>
          <p>The quantitative UX analysis was conducted in all US participants who enrolled in Floodlight Open [<xref ref-type="bibr" rid="ref15">15</xref>]. The analysis was restricted to US participants for several reasons. First, information on user acquisition, including the date and time of activation of the FLO ID, was collected only in the United States. Second, the release dates of the iOS and Android versions of the Floodlight Open app differed for each country [<xref ref-type="bibr" rid="ref15">15</xref>]. Due to these different release dates, only the United States offered a sufficiently long period during which the app’s use without the new UX design features could be studied. Finally, limiting the analysis to US participants allowed us to keep the quantitative UX analysis as consistent as possible with the qualitative UX analysis, which was conducted in a subset of the US participants, thus reducing the impact of differences in demographics and user behavior between the 2 analyses.</p>
        </sec>
        <sec>
          <title>Implementation of New UX Design Features</title>
          <p>The quantitative UX analysis was conducted to investigate the impact of the new UX design features identified in the qualitative UX analysis on user engagement and retention. One of the new UX design features identified in the qualitative UX analysis was a more seamless user journey, which guides users from registration to the activation of the Floodlight Open app (<xref rid="figure3" ref-type="fig">Figure 3</xref>). The original user journey involved registering on the Floodlight Open web portal; downloading the Floodlight Open app from the local app store; and activating the app by entering the FLO ID and activation code, which the participants received in a notification email. This last step required participants to switch multiple times between the notification email and the Floodlight Open app to manually enter their FLO ID and activation code (original user journey in <xref rid="figure3" ref-type="fig">Figure 3</xref>). These complex interactions with multiple user interfaces may frustrate participants, who may eventually abandon the activation process. Therefore, to minimize nuisance factors and reduce user loss, a more seamless user registration and app activation journey was implemented by deep linking the notification email with the Floodlight Open app. This allowed participants to launch the Floodlight Open app directly from the notification email, if already installed on their phone, or to download it from their local app store, with the fields for the FLO ID and activation code already filled out (ie, deep linked). Thus, this more seamless user journey eliminated the requirement of searching for the FLO ID and activation code in the notification email and manually inserting them in the right fields in the Floodlight Open app to activate it (more seamless user journey in <xref rid="figure3" ref-type="fig">Figure 3</xref>).</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>User journey from creating an account to activating the Floodlight Open app. This user journey consists of 4 steps: creating an account, providing e-consent, receiving a personalized Floodlight Open unique identifier (FLO ID) and activation code via email, and downloading and activating the Floodlight Open app (light blue arrows). With the original user journey, participants will have to switch between the app and the email at least twice to copy and enter their FLO ID and activation code to activate all functionalities of the app (red arrows). With the more seamless user journey, the deep-linking feature is integrated in the link provided in the email to download the app from the local app store. With this feature, the personalized FLO ID and activation code are prefilled when the participants launch the Floodlight Open app for the first time (dark blue arrow). Consequently, participants do not have to switch back and forth between interfaces (ie, their email and the Floodlight Open app) to activate all functionalities. ICF: informed e-consent form.</p>
            </caption>
            <graphic xlink:href="humanfactors_v11i1e57033_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>In addition, configurable reminders and push notifications were introduced as the second new UX design feature (<xref ref-type="table" rid="table2">Table 2</xref>). Configurable reminders provided participants the option to set up reminders to perform the tests. Participants could set up daily or weekly reminders by tapping on the reminder icon, which was visible on the app’s dashboard (<xref rid="figure2" ref-type="fig">Figure 2</xref>). Push notifications, by comparison, were designed to serve two purposes: (1) to encourage inactive participants to reengage with the Floodlight Open app, for example, when they closed the app and did not complete the tests or have been inactive for some time, and (2) to motivate committed users to keep performing the tests. Tapping on the notification took the participants directly to the right entry point of the Floodlight Open app to perform the uncompleted or next test. To enable this new feature, participants had to grant permission to receive push notifications.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>List of push notifications and configurable reminders implemented in the Floodlight Open app<sup>a</sup>.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="220"/>
              <col width="280"/>
              <col width="470"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Feature and type</td>
                  <td>Notification</td>
                  <td>Description</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="4">
                    <bold>Push notifications</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Authorization request</td>
                  <td>Floodlight would like to send you notifications. We’ll send you reminders and alerts to keep you on top of your goals and up-to-date with the impact you are having. [Don’t Allow &#124; Ok]</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Sent the first time users open the app</p>
                      </list-item>
                      <list-item>
                        <p>Permission request to allow push notifications: the Floodlight Open app can send notifications to users at different touch points within the users’ journey in the app</p>
                      </list-item>
                      <list-item>
                        <p>User declines permission: the Floodlight Open app cannot send notifications to users. This affects the user experience</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Authorization reminder</td>
                  <td>Need help keeping up with your Daily Activities? You can allow notifications in your Settings. [Go to Settings &#124; Not now]</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Sent if permission is declined and when the app is open for the first time after 7 days, but never during an active test</p>
                      </list-item>
                      <list-item>
                        <p>The Go to Settings button opens the Floodlight screen in the phone settings, where users can re-enable notifications</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Authorization accepted</td>
                  <td>Thanks for downloading Floodlight Open. Let’s get you signed up and started!</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>If accepted, it opens immediately on the sign-up screen</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Incomplete daily activities</td>
                  <td>You’re doing great! Do you have time to [log your mood &#124; start on symbols &#124; squash some tomatoes &#124; see the shapes &#124; handle balance &#124; get moving]?</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>When users do not complete daily activities in one go, a notification is sent in 4 hours or at 7 PM, at the latest. No notifications are sent after 7 PM, and notifications are sent no more than once per day</p>
                      </list-item>
                      <list-item>
                        <p>Tapping on the notification takes users to the next test in the daily activities to continue with the remaining tests. The message is dependent on the last test completed</p>
                      </list-item>
                      <list-item>
                        <p>Multiple notifications are never sent</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completed only daily activities</td>
                  <td>You have finished your Daily Activities – ready to finish up with a 2MWT<sup>b</sup>?</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>When users complete only daily activities but not the 2-minute walk, a notification is sent in 4 hours or at 7 PM, at the latest. No notifications are sent after 7 PM, and notifications are sent no more than once per day</p>
                      </list-item>
                      <list-item>
                        <p>Clicking on the notification takes users to the 2MWTb</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Incomplete 2MWT<sup>b</sup></td>
                  <td>Don’t forget your 2MWT<sup>b</sup> today. If you can, get started today!</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>When users access and abandon the 2MWTb, a notification is sent after 4 hours or at 7 PM, at the latest. No notifications are sent after 7 PM, and notifications are sent no more than once per day</p>
                      </list-item>
                      <list-item>
                        <p>Tapping on the notification takes users to the 2-minute walk</p>
                      </list-item>
                      <list-item>
                        <p>Users receive this reminder every time the 2MWTb is abandoned</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Completed only the 2MWT<sup>b</sup></td>
                  <td>You’ve checked off your 2MWT<sup>b</sup> – now let’s finish up with your Daily Activities.</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>When users complete only the 2MWTb but not daily activities, a notification is sent in 4 hours or at 7 PM, at the latest. No notifications are sent after 7 PM, and notifications are sent no more than once per day</p>
                      </list-item>
                      <list-item>
                        <p>Tapping on the notification takes users to the daily activities</p>
                      </list-item>
                      <list-item>
                        <p>Users receive this reminder only once a day</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Encouragement</td>
                  <td>You’ve done an incredible job helping us build research so far – ready to check another day off your list?</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Sent at 10 AM the day after 3 consecutive test runs are completed</p>
                      </list-item>
                      <list-item>
                        <p>Tapping on the notification takes users to the daily activities</p>
                      </list-item>
                      <list-item>
                        <p>Users receive this notification no more than twice per week</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Encouragement</td>
                  <td>It’s that time again – ready to check another day off your list?</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Sent at 10 AM the day after 3 consecutive days of no test runs</p>
                      </list-item>
                      <list-item>
                        <p>Tapping on the notification takes users to the dashboard</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Acknowledgment</td>
                  <td>Just a quick thank you. Your support is helping us learn more about MS. We hope you find it useful too!</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Sent every 2 weeks at 6 PM</p>
                      </list-item>
                      <list-item>
                        <p>Tapping on the notification takes users to the dashboard</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
                <tr valign="top">
                  <td colspan="4">
                    <bold>Configurable reminders</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>General reminder</td>
                  <td>It’s time to complete my Daily Activities and 2MWT<sup>b</sup>. Let’s do it!</td>
                  <td>
                    <list list-type="bullet">
                      <list-item>
                        <p>Only 1 reminder can be set up, which can be triggered daily, weekly, or on certain days of the week and at any time</p>
                      </list-item>
                    </list>
                  </td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table2fn1">
                <p><sup>a</sup>Push notifications and configurable reminders were made available on October 21, 2019, for the iOS version and on February 19, 2020, for the Android version of the Floodlight Open app.</p>
              </fn>
              <fn id="table2fn2">
                <p><sup>b</sup>2MWT: Two-Minute Walk Test.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <p>The push notifications were designed as a friendly communication with a strong emphasis on the emotional context (<xref ref-type="table" rid="table2">Table 2</xref>), as the emotional interpretation of a message can impact the user’s response [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. The emotional interpretation begins with the perception of a friendly communication and leads to the planning and execution of a responsive action. Notifications designed in this way are less likely to be ignored and can help create the perception of a human touch within the Floodlight Open app. Hence, they are quite effective for eliciting short-term actions [<xref ref-type="bibr" rid="ref22">22</xref>] and are an important variable in improving adherence [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
          <p>The frequency and logic with which push notifications were triggered were carefully considered to limit disturbance. Receiving many notifications in a short interval or during inopportune times can overwhelm and irritate users [<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref26">26</xref>], which may cause them to turn off notifications or even uninstall the app. Therefore, the notifications were designed such that they are never sent more than twice per day, never sent after 7 PM, and sent only when the user seems to have abandoned the Floodlight Open tests.</p>
        </sec>
        <sec>
          <title>Statistical Analysis</title>
          <p>The quantitative UX analysis was conducted on data available in the publicly available data set [<xref ref-type="bibr" rid="ref15">15</xref>]. As information on self-declared MS status was collected only after the Floodlight Open app was activated, both participants with MS and participants without MS were included in the analysis on the effectiveness of the more seamless user journey. In contrast, the analysis on configurable reminders and push notifications was limited to participants with MS to keep the analysis as consistent as possible with the quantitative UX analysis.</p>
          <p>To study the effectiveness of the more seamless user journey, the conversion rate, which is the proportion of participants who successfully completed the registration and activation process, was compared across 2 cohorts. The first cohort followed the original user journey without the deep-linking feature, whereas the second cohort followed the more seamless user journey that took advantage of the deep-linking feature. Because this UX design feature was released on a separate schedule for the iOS and Android versions of the Floodlight Open app, the first cohort included data collected from November 12, 2018, when the activation dates of the FLO IDs were first logged, through July 17, 2019, when the more seamless user journey along with the deep-linking feature was first implemented. The second cohort included data from all participants who registered from October 21, 2019, when the more seamless user journey was fully implemented in the United States, through November 2, 2021, when the study closed in the United States. The gap between July 17, 2019, and October 21, 2019, was required, as the more seamless user journey feature was released on different schedules for iOS and Android platforms.</p>
          <p>The impact of introducing push notifications and configurable reminders on UX (ie, user engagement and retention) was assessed through continuous app usage time, inactivity time, test completion rate, and user retention rate. The continuous usage time is the number of consecutive days on which a participant used the Floodlight Open app, namely, on how many days in a row they performed the Floodlight Open tests.</p>
          <p>The inactivity time, by comparison, is the time interval between 2 continuous use times during which a participant did not perform any test, that is, how many days in a row a participant waited before returning to perform a test. This metric is strongly affected by the frequency with which participants performed the tests and the likelihood of participants returning to the tests. The nature of the distribution can guide, for example, the choice of successful engagement methods that can further increase user engagement and retention. For both continuous usage time and inactivity time, the probability of <italic>n</italic> days of continuous usage and inactivity, respectively, was computed.</p>
          <p>The test completion rate is defined as the fraction of participants performing at least <italic>n</italic> test series (DA, all daily activities included in the fixed sequence except the SBT and UTT [DA<sub>x</sub>], or 2MWT) since the activation of the Floodlight Open app. The completion rate is a common measure for assessing the effectiveness of UX features, that is, for assessing whether the tasks performed by users achieve specified goals in terms of accuracy and completeness in a specified context of use [<xref ref-type="bibr" rid="ref27">27</xref>]. It does not consider how the goals were achieved but only the extent to which they were achieved. The higher the test completion rate is, the more engaged the users are and the more likely they are to come back and, in this case, perform the assessments. The test completion rate is calculated over the entire duration of the assessed period and does not distinguish between intermittent and continuous usage.</p>
          <p>The user retention rate, by comparison, is the fraction of participants who returned to perform the Floodlight Open tests <italic>n</italic> days after the activation of the Floodlight Open app. The retention rate is extensively used to measure the success of smartphone apps, with higher retention corresponding to higher adoption and level of engagement [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>].</p>
          <p>These UX metrics (continuous app usage time, inactivity time, test completion rate, and user retention rate) characterize the UX with the Floodlight Open app and provide insights into how committed the participants are. Because taking the gait and postural stability tests require both time and space (see the <italic>Qualitative UX Analysis</italic> section), 3 separate test series were considered for each of these metrics: DA (ie, all active tests administered in the fixed sequence: DMQ, IPS, IPS Digit–Digit, PT, DaS, SBT, and UTT), all DA except the gait and postural stability tests (DA<sub>x</sub>; ie, DMQ, IPS, IPS Digit–Digit, PT, and DaS), and 2MWT.</p>
          <p>For each test series, the complementary cumulative distributions of the 4 UX metrics were compared in MS participants using data collected before (November 12, 2018, through October 21, 2019) versus after (February 19, 2020, through November 2, 2021) the configurable reminders and push notifications were introduced. The gap between November 12, 2018, and October 21, 2019, was necessary due to the different release schedules of reminders and notifications for the iOS and Android versions. Hence, during this period, reminders and notifications were available to some, but not all, MS participants. It is possible that individual participants were included in both observation periods if they took the Floodlight Open tests during both periods. Because the different durations of these 2 periods might impact the continuous usage times and the inactivity times, both UX metrics were assessed over the first 343 days of data collected from each participant.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Participants</title>
        <p>Until November 2, 2021, when the study closed in the United States, the Floodlight Open app was downloaded 5225 times, including 4240 (81.15%) times on iOS devices and 985 (18.85%) times on Android devices, across the 17 participating countries. The baseline demographics of the US participants with MS included in the qualitative and quantitative UX analyses on reminders and notifications are presented in <xref ref-type="table" rid="table3">Table 3</xref>.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Baseline demographics of US participants with MS<sup>a</sup> included in the qualitative UX<sup>b</sup> analysis and the quantitative UX analysis.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="140"/>
            <col width="0"/>
            <col width="120"/>
            <col width="0"/>
            <col width="140"/>
            <col width="0"/>
            <col width="130"/>
            <col width="0"/>
            <col width="0"/>
            <col width="110"/>
            <col width="0"/>
            <col width="100"/>
            <col width="0"/>
            <col width="0"/>
            <col width="110"/>
            <col width="0"/>
            <col width="120"/>
            <thead>
              <tr valign="bottom">
                <td colspan="3">Variable</td>
                <td colspan="2">Qualitative UX analysis (N=22<sup>c</sup>)</td>
                <td colspan="13">Quantitative UX analysis<sup>d</sup>, n (%)</td>
              </tr>
              <tr valign="bottom">
                <td colspan="3">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="5">FLO<sup>e</sup> app without configurable reminders and push notifications<sup>f</sup> (n=350)</td>
                <td colspan="5">FLO app with configurable reminders and push notifications<sup>g</sup> (n=172)</td>
                <td colspan="3">All<sup>h</sup> (N=498)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">Female (n=264)</td>
                <td colspan="2">Male (n=86)</td>
                <td colspan="3">Female (n=123)</td>
                <td colspan="2">Male (n=49)</td>
                <td colspan="3">Female (n=368)</td>
                <td>Male (n=130)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">Age (y), mean (SD; range)</td>
                <td colspan="2">50 (9.9; 18-74)</td>
                <td colspan="2">47.53 (11.4; 19-71)</td>
                <td colspan="2">49.63 (13.2; 19-84)</td>
                <td colspan="3">48.69 (12.29; 22-73)</td>
                <td colspan="2">50.73 (10.57; 30-79)</td>
                <td colspan="3">47.6 (11.6; 19-73)</td>
                <td>49.7 (12.7;19-84)</td>
              </tr>
              <tr valign="top">
                <td colspan="18">
                  <bold>Age distribution (y), n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>18-24</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">4 (1.5)</td>
                <td colspan="2">1 (1.2)</td>
                <td colspan="3">4 (3.3)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="3">6 (1.6)</td>
                <td colspan="2">1 (0.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>25-34</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">32 (12.1)</td>
                <td colspan="2">12 (13.9)</td>
                <td colspan="3">10 (8.1)</td>
                <td colspan="2">3 (6.1)</td>
                <td colspan="3">42 (11.4)</td>
                <td colspan="2">16 (12.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>35-44</td>
                <td colspan="2">3 (13.6)</td>
                <td colspan="2">64 (24.2)</td>
                <td colspan="2">19 (22.1)</td>
                <td colspan="3">32 (26)</td>
                <td colspan="2">11 (22.5)</td>
                <td colspan="3">99 (26.9)</td>
                <td colspan="2">29 (22.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>45-54</td>
                <td colspan="2">7 (31.8)</td>
                <td colspan="2">90 (34.1)</td>
                <td colspan="2">22 (25.6)</td>
                <td colspan="3">31 (25.2)</td>
                <td colspan="2">19 (38.8)</td>
                <td colspan="3">111 (30.2)</td>
                <td colspan="2">38 (29.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>55-64</td>
                <td colspan="2">7 (31.8)</td>
                <td colspan="2">53 (20.1)</td>
                <td colspan="2">24 (27.9)</td>
                <td colspan="3">31 (25.2)</td>
                <td colspan="2">12 (24.5)</td>
                <td colspan="3">78 (21.2)</td>
                <td colspan="2">34 (26.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>65-74</td>
                <td colspan="2">5 (22.7)</td>
                <td colspan="2">21 (8)</td>
                <td colspan="2">7 (8.1)</td>
                <td colspan="3">15 (12.2)</td>
                <td colspan="2">3 (6.1)</td>
                <td colspan="3">32 (8.7)</td>
                <td colspan="2">10 (7.7)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>≥75</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (1.2)</td>
                <td colspan="3">0 (0)</td>
                <td colspan="2">1 (2)</td>
                <td colspan="3">0 (0)</td>
                <td colspan="2">2 (1.5)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>MS: multiple sclerosis.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>UX: user experience.</p>
            </fn>
            <fn id="table3fn3">
              <p><sup>c</sup>Of the 22 participants included in the qualitative user experience (UX) analysis, 19 (86.4%) were female.</p>
            </fn>
            <fn id="table3fn4">
              <p><sup>d</sup>Some participants may be included both in the cohort with configurable reminders and notifications and in the cohort without configurable reminders and notifications if they provided data during both periods. Demographic information was collected only after the successful activation of the Floodlight Open app and is, therefore, not available for the participants included in the assessment of the more seamless user journey.</p>
            </fn>
            <fn id="table3fn5">
              <p><sup>e</sup>FLO: Floodlight Open.</p>
            </fn>
            <fn id="table3fn6">
              <p><sup>f</sup>Includes all US participants with MS who participated in the study from November 12, 2018, through October 20, 2019.</p>
            </fn>
            <fn id="table3fn7">
              <p><sup>g</sup>Includes all US participants with MS who participated in the study from February 19, 2020, through November 2, 2021.</p>
            </fn>
            <fn id="table3fn8">
              <p><sup>h</sup>Includes all US participants with MS who participated in the study from November 12, 2018, through November 2, 2021, and were included in the analysis of the impact of introducing configurable reminders and push notifications.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Qualitative UX Analysis</title>
        <p>A total of 22 US participants were enrolled in the qualitative substudy, of which 15 (68%) were interviewed. Between 7 and 19 participants are considered adequate for qualitative research [<xref ref-type="bibr" rid="ref30">30</xref>].</p>
        <p>The qualitative UX analysis reveals key points for improving the UX with the Floodlight Open app (<xref ref-type="table" rid="table4">Table 4</xref>). While many participants did not face any difficulties downloading the Floodlight Open app and were willing to perform the tests daily, some were unaware or confused about the activation process despite instructions being provided on the study’s web portal (see <italic>Need for a More Seamless User Journey</italic> section in <xref ref-type="table" rid="table4">Table 4</xref>). Other participants reported that they did not complete the activation process due to distractions or the lack of reminders to complete this step. Here, a more seamless journey from registering on the web portal to activating the Floodlight Open app could improve the UX. In addition, participants who successfully activated the Floodlight Open app self-reported that they used it for 2 to 30 days and agreed that screen contents, prompts, and information were easy to see and understand. However, they also reported that they often forgot to perform the tests or felt it was not always feasible to perform all the tests in one setting. Therefore, configurable reminders and push notifications would have been beneficial (see bottom section in <xref ref-type="table" rid="table4">Table 4</xref>). Such UX design features could be used to set up reminders to perform the tests or to stop the current test and plan to complete the tests later. Furthermore, participants were not always available to perform tests that required them to stand or walk:</p>
        <disp-quote>
          <p>I can only proceed so far because I’m in the car waiting for my kid; I can’t stand and balance...or do the walking back and forth and the balancing stuff.</p>
        </disp-quote>
        <disp-quote>
          <p>The part that is difficult to get done is the 2-minute walk. To find the time...is sometimes hard for someone like me who is more active.</p>
        </disp-quote>
        <disp-quote>
          <p>Certain tasks...were a little too long. How many more lines do I need to draw? How many more tomatoes can I pinch?</p>
        </disp-quote>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Learnings from the qualitative UX<sup>a</sup> analysis.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="230"/>
            <col width="770"/>
            <thead>
              <tr valign="top">
                <td>Learnings from the qualitative UX analysis</td>
                <td>Comments made by participants that support the learnings</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Need for a more seamless user journey</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“I see a register button and an activate button, and I don’t know if I am registered, or what I need to do to activate it. I remember getting to this page and thinking there’s something I have to do, some code or something to be able to activate it.”</p>
                    </list-item>
                    <list-item>
                      <p>“I let it go too long before I tried to use it, and so the registration/activation process was not clear to me at that point and I never followed up on it.”</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Need for configurable reminders and push notifications</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>“I just don’t know. I think maybe it was something that was on my phone, and I was like, ‘What is this? You know?’”</p>
                    </list-item>
                    <list-item>
                      <p>“I would say life got in the way.”</p>
                    </list-item>
                    <list-item>
                      <p>“I just forgot. I got distracted. It just went out of my brain and never came back. What I should have done in retrospect is put a reminder popup in my phone, like to pop up every day. I would much rather the app remind me. The less I have to touch my phone, the better my life is.”</p>
                    </list-item>
                    <list-item>
                      <p>“I have been terrible at using the app. I’ve used it twice. I think one of the problems I had with the app is it doesn’t remind me to do it. If my phone doesn’t tell me to do something, it probably doesn’t happen. I would have been much more inclined to do it if it had reminded me to do it.”</p>
                    </list-item>
                    <list-item>
                      <p>“Things were crazy with work. I’ve had other things on my mind. I didn’t see anything pop up reminding me to use it.”</p>
                    </list-item>
                    <list-item>
                      <p>“I didn’t read the instructions. I had to guess what to do with the matching shapes. At first I thought I was being timed so I was rushing.”</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table4fn1">
              <p><sup>a</sup>UX: user experience.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Consequently, in the subsequent section on quantitative UX analysis, UX with the Floodlight Open app was investigated with respect to DA, DA<sub>x</sub>, and 2MWT.</p>
      </sec>
      <sec>
        <title>Quantitative UX Analysis</title>
        <sec>
          <title>User Journey</title>
          <p>Of the 1089 US participants, 608 (55.8%) with or without MS (self-declared MS disease status was not available for this analysis, as this information was collected only after the successful activation of the app) followed the original user journey without the deep-linking feature, and 481 (44.2%) participants with or without MS followed the newer, more seamless user journey with the deep-linking feature. The flow diagrams in <xref rid="figure4" ref-type="fig">Figure 4</xref> show the conversion rates from creating an account to activating the app for both cohorts. In both cohorts, all participants who created an account completed the registration process, provided informed consent, and enrolled in the study. However, <xref rid="figure4" ref-type="fig">Figure 4</xref> shows that introducing the new user journey improved the conversion rate of the participants who succeeded in activating the app (359/481, 74.6% with the more seamless user journey vs 328/608, 53.9% with the original user journey).</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Conversion rate diagrams. These diagrams depict the user journey from registration on the Floodlight Open web portal (creating a Floodlight Open account) to the activation of the Floodlight Open app (A) before and (B) after implementing the more seamless user journey. FLO: Floodlight Open; ICF: informed e-consent form.</p>
            </caption>
            <graphic xlink:href="humanfactors_v11i1e57033_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Configurable Reminders and Push Notifications</title>
          <p>The analysis on configurable reminders and push notifications included 172 participants with MS to whom this UX design feature was available and 350 participants with MS to whom this feature was not available (<xref ref-type="table" rid="table3">Table 3</xref>). The cumulative distributions of the continuous usage times of participants with MS using the Floodlight Open app with reminders and notifications and those using the Floodlight Open app without reminders and notifications are plotted in a log-log scale for DA, DA<sub>x</sub>, and 2MWT in <xref rid="figure5" ref-type="fig">Figure 5</xref>A. The introduction of reminders and notifications increased the continuous app usage times. The longest continuous usage times with reminders and notifications versus those without reminders and notifications were 103 versus 13 days for DA, 224 versus 61 days for DA<sub>x</sub>, and 65 versus 12 days for 2MWT. Similarly, reminders and notifications increased the proportion of participants using the app for at least 3 consecutive days (DA and DA<sub>x</sub>: ~30% vs ~12%; 2MWT: ~30% vs ~20%).</p>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>Complementary cumulative distributions of the continuous app use time (A), inactivity time (B), test completion rate (C), and user retention rate (D) of participants with multiple sclerosis (MS) using the Floodlight Open app with reminders and notifications (wR&#38;N; blue) and without reminders and notifications (woR&#38;N; green) for all daily activities performed in the fixed sequence (DA), all daily activities performed in the fixed sequence without Static Balance Test and U-Turn Test (DAx), and Two-Minute Walk Test (2MWT). Continuous app usage time, test completion rate, and user retention rate improved with reminders and notifications after an initial onboarding phase, whereas inactivity time was comparable between the 2 cohorts.</p>
            </caption>
            <graphic xlink:href="humanfactors_v11i1e57033_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p><xref rid="figure5" ref-type="fig">Figure 5</xref>B presents the inactivity time distributions from participants using the Floodlight Open app with configurable reminders and push notifications and those using the Floodlight Open app without configurable reminders and push notifications on a log-log scale for DA, DA<sub>x</sub>, and 2MWT. These distributions were similar for participants with reminders and notifications and those without reminders and notifications for DA, DA<sub>x</sub>, and 2MWT, exhibiting an approximate power law with a coefficient of 0.96 in both cohorts. The longest inactivity times with reminders and notifications versus without reminders and notifications were 145 versus 263 days for DA, 138 versus 309 days for DA<sub>x</sub>, and 181 versus 263 days for 2MWT.</p>
          <p><xref rid="figure5" ref-type="fig">Figure 5</xref>C presents the test completion rate distributions for DA, DA<sub>x</sub>, and 2MWT. These distributions show that the introduction of reminders and notifications resulted in higher test completion rates, except during the initial onboarding phase when DA and DA<sub>x</sub> completion rates were similar in both cohorts. During this onboarding phase, day-1 test completion rates with and without reminders and notifications were 66% (113/172) and 66.9% (234/350), respectively, for DA and 81.3% (140/172) and 86% (301/350), respectively, for DA<sub>x</sub>. These test completion rates are expected to be &#60;100% because not all participants who activated the Floodlight Open app proceeded to perform at least 1 DA or DA<sub>x</sub> series. However, the effectiveness of introducing reminders and notifications became evident after this initial onboarding phase (ie, after the first DA series and after the third DA<sub>x</sub> series; <xref rid="figure5" ref-type="fig">Figure 5</xref>C). When considering the 2MWT instead, participants with reminders and notifications showed higher test completion rates than participants without reminders and notifications (41.5% [72/172] with reminders and notifications vs 34.8% [122/350] without reminders and notifications) on the first day itself. Across all 3 test series, the largest number of test series completed increased with the introduction of reminders and notifications (279 vs 64 for DA, 283 vs 126 for DA<sub>x</sub>, and 302 vs 76 for 2MWT).</p>
          <p><xref rid="figure5" ref-type="fig">Figure 5</xref>D presents the user retention rate distributions. During the initial onboarding phase, user retention rates were comparable between participants with reminders and notifications and those without reminders and notifications. On day 1, DA user retention rates were 65.7% (113/172) and 61.7% (216/350), respectively, and DA<sub>x</sub> user retention rates were 79.6% (137/172) and 82.8% (290/350), respectively (<xref ref-type="table" rid="table4">Table 4</xref>). DA<sub>x</sub> user retention rates continued to be comparable between both cohorts for approximately the first 10 days. After this onboarding phase, however, the effectiveness of reminders and notifications in improving user retention rate became evident. Interestingly, after the high drop-off observed during the first few days after the activation of the app (3 days for DA and DA<sub>x</sub> and 2 days for 2MWT), all user retention rate distributions obtained with reminders and notifications plateaued up to approximately day 30. On day 30, user retention rates were considerably higher in participants with versus participants without reminders and notifications (53/172, 30.8% vs 34/350, 9.7% for DA; 53/172, 30.8% vs 60/350, 17.1% for DA<sub>x</sub>; and 39/172, 22.6% vs 22/350, 6.2% for 2MWT; <xref ref-type="table" rid="table5">Table 5</xref>).</p>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>User retention rates of the Floodlight Open app with and without reminders and notifications from participants with MS<sup>a</sup> and average user retention rates for medical apps and health and fitness apps reported by Rosenfelder [<xref ref-type="bibr" rid="ref31">31</xref>] on days 1, 3, 7, 14, and 30.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="30"/>
              <col width="230"/>
              <col width="150"/>
              <col width="140"/>
              <col width="140"/>
              <col width="140"/>
              <col width="140"/>
              <thead>
                <tr valign="top">
                  <td colspan="3">Apps, configuration, and series</td>
                  <td colspan="5">User retention rate</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Day 1</td>
                  <td>Day 3</td>
                  <td>Day 7</td>
                  <td>Day 14</td>
                  <td>Day 30</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="8">
                    <bold>Floodlight Open app, % (n/N)</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="7">
                    <bold>Without configurable reminders and push notifications</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>DA<sup>b</sup></td>
                  <td>61.7 (216/350)</td>
                  <td>32 (112/350)</td>
                  <td>23.4 (82/350)</td>
                  <td>16.3 (57/350)</td>
                  <td>9.7 (34/350)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>DA<sub>x</sub><sup>c</sup></td>
                  <td>82.8 (290/350)</td>
                  <td>48.8 (171/350)</td>
                  <td>34.5 (121/350)</td>
                  <td>28 (98/350)</td>
                  <td>17.1 (60/350)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>2MWT<sup>d</sup></td>
                  <td>32.3<strike>4</strike> (113/350)</td>
                  <td>18.2 (64/350)</td>
                  <td>14.2 (50/350)</td>
                  <td>11.3 (39/350)</td>
                  <td>6.2 (22/350)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="7">
                    <bold>With configurable reminders and push notifications</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>DA</td>
                  <td>65.7 (113/172)</td>
                  <td>36.6 (63/172)</td>
                  <td>32.6 (56/172)</td>
                  <td>30.8 (53/172)</td>
                  <td>30.8 (53/172)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>DA<sub>x</sub></td>
                  <td>79.6 (137/172)</td>
                  <td>51.1 (88/172)</td>
                  <td>36.6 (63/172)</td>
                  <td>30.8 (53/172)</td>
                  <td>30.8 (53/172)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>2MWT</td>
                  <td>40.7 (70/172)</td>
                  <td>32.6 (56/172)</td>
                  <td>28.5 (49/172)</td>
                  <td>24.4 (42/172)</td>
                  <td>22.6 (39/172)</td>
                </tr>
                <tr valign="top">
                  <td colspan="8">
                    <bold>Rosenfelder [<xref ref-type="bibr" rid="ref31">31</xref>], 2020, %<sup>e</sup></bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="7">
                    <bold>Medical apps</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Active</td>
                  <td>20</td>
                  <td>11.52</td>
                  <td>9.24</td>
                  <td>7.19</td>
                  <td>5.46</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td colspan="7">
                    <bold>Health and fitness apps</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Active</td>
                  <td>18.37</td>
                  <td>10.56</td>
                  <td>7.77</td>
                  <td>5.56</td>
                  <td>3.6</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table5fn1">
                <p><sup>a</sup>MS: multiple sclerosis.</p>
              </fn>
              <fn id="table5fn2">
                <p><sup>b</sup>DA: all daily activities that were administered in a predefined, fixed sequence.</p>
              </fn>
              <fn id="table5fn3">
                <p><sup>c</sup>DA<sub>x</sub>: all daily activities that were administered in a predefined, fixed sequence, except the Static Balance Test and U-Turn Test.</p>
              </fn>
              <fn id="table5fn4">
                <p><sup>d</sup>2MWT: Two-Minute Walk Test.</p>
              </fn>
              <fn id="table5fn5">
                <p><sup>e</sup>The absolute number of uses retained at each time point were not reported in Rosenfelder [<xref ref-type="bibr" rid="ref31">31</xref>], 2020.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Smartphones enable out-of-clinic assessments of chronic neurological diseases. Despite the rapidly increasing number of mobile health care apps available for consumers’ self-care, there is a paucity of research into the UX of DHTTs for MS. In this paper, we present our qualitative and quantitative UX analyses of the Floodlight Open app and demonstrate that the adoption of key UX design features markedly improved user acquisition, engagement, and retention. Understanding how the presence or absence of specific UX design features affects participants’ experiences offers important guidance for the refinement of an existing or the design of a new DHTT. Therefore, UX design features are a significant consideration when designing and evaluating such tools.</p>
        <p>Assessing MS symptoms over time with the Floodlight Open app requires specific user stimulation and guidance through seamless and flexible user journeys enhanced by engaging features to improve the overall UX. By considering participants’ feedback collected in the quantitative UX substudy, we enhanced the onboarding process by implementing a more seamless user registration and app activation journey and improved the UX through configurable reminders and push notifications. We derived several distributions from real-world data that describe key aspects of participants’ behavior in their environment. Such measurements and their statistical analysis might be used to help describe realistic user behavior and design health care apps similar to our Floodlight Open app. Our findings allow us to gain a better understanding of users’ experience in such settings and to make informed design decisions for self-monitoring mobile apps that support people with MS.</p>
        <p>Users’ first experience with the registration to the Floodlight Open study and the activation of the study app is important to increase user acquisition. Furthermore, the first few days after activating the app are similarly critical for long-term engagement and retention. For instance, user acquisition, engagement, and retention can all be improved by guiding users throughout the Floodlight Open study registration, app activation process, and daily activities, reminding them about the daily activities to be performed and allowing them to plan when to perform the daily activities. Our results demonstrate that a seamless UX is essential to minimize the rate at which users drop out along the end-to-end journey. With a seamless user journey, users are led along the registration-activation journey and are not distracted by unrelated content or activities, resulting in a higher conversion rate from creating an account to activating the Floodlight Open app.</p>
        <p>Configurable reminders and push notifications can help keep the participants engaged with mobile health care apps, such as the Floodlight Open app, and help retain them beyond the initial onboarding phase. Our findings show that continuous use times, test completion rates, and user retention rates are generally higher with configurable reminders and push notifications than without configurable reminders and push notifications, whereas inactivity time is comparable between the 2 cohorts. This improvement in user engagement is most evident for 2MWT from the first day and for DA and DA<sub>x</sub> after the initial onboarding phase, during which the participants are still exploring the Floodlight Open app. Therefore, to fully optimize the UX, the app should ask the users to accept and receive reminders and notifications only after this initial onboarding phase [<xref ref-type="bibr" rid="ref32">32</xref>]. Interrupting users with notifications too soon after the activation of the app may create frustration and may ultimately lead them to abandon the app. The app should, therefore, minimize the mental and physical interaction efforts during the first few days of use.</p>
        <p>Comparing the different test series, we noted slightly worse user retention for 2MWT than for either DA or DA<sub>x</sub>. Taking the 2MWT requires the greatest effort, which is in line with some dissatisfaction reported in a previous proof-of-concept study [<xref ref-type="bibr" rid="ref33">33</xref>]. It is possible that the study participants did want to take the 2MWT but did not find a suitable opportunity to take it each day. In fact, participants in Floodlight Open were found to persistently take the 2MWT at least once per week [<xref ref-type="bibr" rid="ref15">15</xref>], which suggests that a more flexible or less frequent assessment schedule could be beneficial.</p>
      </sec>
      <sec>
        <title>Comparison With Prior Work</title>
        <p>Although several other smartphone apps are available for people with MS (for a review on MS apps, refer to the study by Howard et al [<xref ref-type="bibr" rid="ref34">34</xref>]), to our knowledge, this is the first analysis to assess the impact of UX design features on user engagement and retention. Nonetheless, previous analyses have shown that user engagement and retention remain two of the barriers to the long-term successful deployment of DHTTs (for reviews, refer to works of Pratap et al [<xref ref-type="bibr" rid="ref6">6</xref>] and Amagai et al [<xref ref-type="bibr" rid="ref35">35</xref>]). Several UX design features have been suggested to improve the overall UX, including a more seamless user journey, configurable reminders, and push notifications [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref35">35</xref>-<xref ref-type="bibr" rid="ref38">38</xref>]. However, differences in the definitions used to assess user retention (eg, user retention definitions based on the user simply opening or interacting with the DHHT [<xref ref-type="bibr" rid="ref31">31</xref>] vs completing a test or series of tests [<xref ref-type="bibr" rid="ref6">6</xref>]), limited statistical power due to small sample sizes [<xref ref-type="bibr" rid="ref37">37</xref>], and differences in the observed study period [<xref ref-type="bibr" rid="ref37">37</xref>] may make direct comparisons of user retention across different DHHTs challenging.</p>
        <p>To compare like with like, we computed the user retention with the Floodlight Open app for the same observation period as that reported in the study by Rosenfelder [<xref ref-type="bibr" rid="ref31">31</xref>] for medical as well as health and lifestyle apps. Both data sets indicate that the largest reduction of users occurs from days 1 to 3, whereas the reduction in user retention is low between days 7 and 30. This suggests that a significant proportion of users who will not use the Floodlight Open app (or other health care apps) in the long term will stop using the app within the first 3 days and that this dropout is likely to be observed within the first 7 days. These results also suggest that participants who use the app for &#62;3 days are likely to use it for at least 30 days. A similar dropout during the first 7 days has also been previously reported for the whole study cohort of Floodlight Open [<xref ref-type="bibr" rid="ref15">15</xref>].</p>
        <p>Of note, our user retention rates are approximately 2- to 6-fold higher than those reported by Rosenfelder [<xref ref-type="bibr" rid="ref31">31</xref>] (<xref ref-type="table" rid="table5">Table 5</xref>) despite using a more conservative definition of user retention (completing a test series vs simply interacting with or opening the app). It is conceivable that not all apps included in the report by Rosenfelder [<xref ref-type="bibr" rid="ref31">31</xref>] feature the same UX design features as the Floodlight Open app does. However, favorable user retention rates were observed with the Floodlight Open app even when the app did not have configurable reminders or push notifications. This suggests that differences in the perceived benefit of the app might have also contributed to the favorable retention profile, although other reasons cannot be excluded [<xref ref-type="bibr" rid="ref39">39</xref>]. Despite our favorable user retention and user engagement findings, a previous analysis showed that improvement in smartphone sensor data collection could be achieved through passive data collection methods [<xref ref-type="bibr" rid="ref15">15</xref>].</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>A few limitations are noted. First, while participants could turn off the configurable reminders and push notifications, this action was not logged. Instead, we compared participants who enrolled before with those who enrolled after these features were implemented. For the former cohort, we included only the data collected up to the implementation of reminders and notifications in our analyses to be able to assess the impact of reminders and notifications. Second, our results were influenced by the duration of the study and by incoming participants who activated the Floodlight Open app on different dates over the duration of the study and might not be part of the study for the same number of days. Besides, for events approaching the duration of the study, there is an artificially lower likelihood of observation, and events lasting longer than the study cannot be observed. Finally, the use of the Floodlight Open app in a clinical study other than the Floodlight Open observational study may boost user engagement and retention due to additional motivational incentives. Such clinical referrals have been shown to improve user retention [<xref ref-type="bibr" rid="ref6">6</xref>]. However, information on which participants participated in such studies is not available, and without it, accounting for it is not possible.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>We presented the qualitative and quantitative UX analyses of the Floodlight Open app, a DHTT for MS. Learnings from the qualitative UX analysis led to the implementation of a more seamless user journey and the introduction of configurable reminders and push notifications. These US design features improved user acquisition, user engagement, and user retention. The continued assessment of UX and improvement of UX design features are critical steps in optimizing the long-term adoption of the Floodlight Open technology and similar DHTTs.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">2MWT</term>
          <def>
            <p>Two-Minute Walk Test</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">DA</term>
          <def>
            <p>all daily activities that were administered in a predefined, fixed sequence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">DaS</term>
          <def>
            <p>Draw a Shape Test</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">DAx</term>
          <def>
            <p>all daily activities that were administered in a predefined, fixed sequence excluding the Static Balance Test and U-Turn Test</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">DHTT</term>
          <def>
            <p>digital health technology tool</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">DMQ</term>
          <def>
            <p>Daily Mood Questionnaire</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">FLO ID</term>
          <def>
            <p>personal Floodlight Open unique identifier</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">IPS</term>
          <def>
            <p>Information Processing Speed</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">MS</term>
          <def>
            <p>multiple sclerosis</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">PT</term>
          <def>
            <p>Pinching Test</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">SBT</term>
          <def>
            <p>Static Balance Test</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">UTT</term>
          <def>
            <p>U-Turn Test</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">UX</term>
          <def>
            <p>user experience</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to thank all the Roche Floodlight Open team members, in particular, Luca Capezzuto, as well as all the participants and researchers who expressed interest in this study. This research was funded by F. Hoffmann-La Roche Ltd, Basel, Switzerland. Writing and editorial assistance for this manuscript was provided by Sven Holm, PhD, contractor for F. Hoffmann-La Roche Ltd. Up-to-date details on Roche’s Global Policy on Sharing of Clinical Study Information and how to request access to related clinical study documents are provided [<xref ref-type="bibr" rid="ref40">40</xref>].</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>Request for the data underlying this publication requires a detailed, hypothesis-driven statistical analysis plan that is collaboratively developed by the requester and company subject matter experts. Such requests should be directed to dbm.datarequest@roche.com for consideration. Anonymized records for individual patients across &#62;1 data source external to Roche cannot, and should not, be linked due to a potential increase in the risk of patient reidentiﬁcation.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="conflict">
        <p>AG, LK, and RL are employees of F Hoffmann-La Roche Ltd. ML is a consultant for F Hoffmann-La Roche Ltd via Inovigate. JBJ is an employee of Sutter Health’s Center for Health Systems Research. He has received research grants from Genentech and AstraZeneca.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kappos</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wolinsky</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Giovannoni</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Arnold</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Bernasconi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Model</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Koendgen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Manfrini</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Belachew</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hauser</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>Contribution of relapse-independent progression vs relapse-associated worsening to overall confirmed disability accumulation in typical relapsing multiple sclerosis in a pooled analysis of 2 randomized clinical trials</article-title>
          <source>JAMA Neurol</source>
          <year>2020</year>
          <month>09</month>
          <day>01</day>
          <volume>77</volume>
          <issue>9</issue>
          <fpage>1132</fpage>
          <lpage>40</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32511687"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamaneurol.2020.1568</pub-id>
          <pub-id pub-id-type="medline">32511687</pub-id>
          <pub-id pub-id-type="pii">2766801</pub-id>
          <pub-id pub-id-type="pmcid">PMC7281382</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>Hobart</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bowen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pepper</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Crofts</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Eberhard</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Berger</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Boyko</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Boz</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Butzkueven</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Celius</surname>
              <given-names>EG</given-names>
            </name>
            <name name-style="western">
              <surname>Drulovic</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Flores</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Horáková</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lebrun-Frénay</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Marrie</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Overell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Piehl</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Rasmussen</surname>
              <given-names>PV</given-names>
            </name>
            <name name-style="western">
              <surname>Sá</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Sîrbu</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Skromne</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Torkildsen</surname>
              <given-names>Ø</given-names>
            </name>
            <name name-style="western">
              <surname>van Pesch</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Vollmer</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Zakaria</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ziemssen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Giovannoni</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>International consensus on quality standards for brain health-focused care in multiple sclerosis</article-title>
          <source>Mult Scler</source>
          <year>2019</year>
          <month>11</month>
          <volume>25</volume>
          <issue>13</issue>
          <fpage>1809</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/abs/10.1177/1352458518809326?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1352458518809326</pub-id>
          <pub-id pub-id-type="medline">30381987</pub-id>
          <pub-id pub-id-type="pmcid">PMC6826858</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>Montalban</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Graves</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Midaglia</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mulero</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Julian</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schadrack</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gossens</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ganzetti</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Scotland</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lipsmeier</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>van Beek</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bernasconi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Belachew</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hauser</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>A smartphone sensor-based digital outcome assessment of multiple sclerosis</article-title>
          <source>Mult Scler</source>
          <year>2022</year>
          <month>04</month>
          <volume>28</volume>
          <issue>4</issue>
          <fpage>654</fpage>
          <lpage>64</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/abs/10.1177/13524585211028561?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/13524585211028561</pub-id>
          <pub-id pub-id-type="medline">34259588</pub-id>
          <pub-id pub-id-type="pmcid">PMC8961252</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>van der Walt</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Butzkueven</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Shin</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Midaglia</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Capezzuto</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Davies</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Butler</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Costantino</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Montalban</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Developing a digital solution for remote assessment in multiple sclerosis: from concept to software as a medical device</article-title>
          <source>Brain Sci</source>
          <year>2021</year>
          <month>09</month>
          <day>21</day>
          <volume>11</volume>
          <issue>9</issue>
          <fpage>1247</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=brainsci11091247"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/brainsci11091247</pub-id>
          <pub-id pub-id-type="medline">34573267</pub-id>
          <pub-id pub-id-type="pii">brainsci11091247</pub-id>
          <pub-id pub-id-type="pmcid">PMC8471038</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>Gromisch</surname>
              <given-names>ES</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Haselkorn</surname>
              <given-names>JK</given-names>
            </name>
            <name name-style="western">
              <surname>Lo</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Agresta</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Mobile health (mHealth) usage, barriers, and technological considerations in persons with multiple sclerosis: a literature review</article-title>
          <source>JAMIA Open</source>
          <year>2020</year>
          <month>12</month>
          <day>15</day>
          <volume>4</volume>
          <issue>3</issue>
          <fpage>ooaa067</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34514349"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooaa067</pub-id>
          <pub-id pub-id-type="medline">34514349</pub-id>
          <pub-id pub-id-type="pii">ooaa067</pub-id>
          <pub-id pub-id-type="pmcid">PMC8423420</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>Pratap</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Neto</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Snyder</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Stepnowsky</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Elhadad</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Grant</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mohebbi</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Mooney</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Suver</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wilbanks</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mangravite</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Heagerty</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Areán</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Omberg</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Indicators of retention in remote digital health studies: a cross-study evaluation of 100,000 participants</article-title>
          <source>NPJ Digit Med</source>
          <year>2020</year>
          <month>02</month>
          <day>17</day>
          <volume>3</volume>
          <fpage>21</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-020-0224-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-020-0224-8</pub-id>
          <pub-id pub-id-type="medline">32128451</pub-id>
          <pub-id pub-id-type="pii">224</pub-id>
          <pub-id pub-id-type="pmcid">PMC7026051</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Law</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Roto</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Hassenzahl</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vermeeren</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Kort</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Understanding, scoping and defining user experience: a survey approach</article-title>
          <source>Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</source>
          <year>2009</year>
          <conf-name>CHI '09</conf-name>
          <conf-date>April 4-9, 2009</conf-date>
          <conf-loc>Boston, MA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1518701.1518813</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>Bitkina</surname>
              <given-names>OV</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Usability and user experience of medical devices: an overview of the current state, analysis methodologies, and future challenges</article-title>
          <source>Int J Ind Ergon</source>
          <year>2020</year>
          <month>03</month>
          <volume>76</volume>
          <fpage>102932</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ergon.2020.102932</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>Park</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>SH</given-names>
            </name>
          </person-group>
          <article-title>Defining user value: a case study of a smartphone</article-title>
          <source>Int J Ind Ergon</source>
          <year>2013</year>
          <month>07</month>
          <volume>43</volume>
          <issue>4</issue>
          <fpage>274</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ergon.2013.04.005</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>Park</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>Cho</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Developing elements of user experience for mobile phones and services: survey, interview, and observation approaches</article-title>
          <source>Hum Factors Ergon Manuf Serv Ind</source>
          <year>2011</year>
          <month>10</month>
          <day>20</day>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>279</fpage>
          <lpage>93</lpage>
          <pub-id pub-id-type="doi">10.1002/hfm.20316</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>Park</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>Oh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Moon</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Modeling user experience: a case study on a mobile device</article-title>
          <source>Int J Ind Ergon</source>
          <year>2013</year>
          <month>03</month>
          <volume>43</volume>
          <issue>2</issue>
          <fpage>187</fpage>
          <lpage>96</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ergon.2013.01.005</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yardley</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Morrison</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bradbury</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Muller</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>The person-based approach to intervention development: application to digital health-related behavior change interventions</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <month>01</month>
          <day>30</day>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>e30</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2015/1/e30/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.4055</pub-id>
          <pub-id pub-id-type="medline">25639757</pub-id>
          <pub-id pub-id-type="pii">v17i1e30</pub-id>
          <pub-id pub-id-type="pmcid">PMC4327440</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yardley</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Spring</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Riper</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Morrison</surname>
              <given-names>LG</given-names>
            </name>
            <name name-style="western">
              <surname>Crane</surname>
              <given-names>DH</given-names>
            </name>
            <name name-style="western">
              <surname>Curtis</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Merchant</surname>
              <given-names>GC</given-names>
            </name>
            <name name-style="western">
              <surname>Naughton</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Blandford</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Understanding and promoting effective engagement with digital behavior change interventions</article-title>
          <source>Am J Prev Med</source>
          <year>2016</year>
          <month>11</month>
          <volume>51</volume>
          <issue>5</issue>
          <fpage>833</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1016/j.amepre.2016.06.015</pub-id>
          <pub-id pub-id-type="medline">27745683</pub-id>
          <pub-id pub-id-type="pii">S0749-3797(16)30243-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Ploderer</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Wadley</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Webber</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Borland</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Trajectories of engagement and disengagement with a story-based smoking cessation app</article-title>
          <source>Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems</source>
          <year>2017</year>
          <conf-name>CHI '17</conf-name>
          <conf-date>May 6-11, 2017</conf-date>
          <conf-loc>Denver, CO</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3025453.3026054</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>Oh</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Capezzuto</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kriara</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Schjodt-Eriksen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>van Beek</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bernasconi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Montalban</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Butzkueven</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kappos</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Giovannoni</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bove</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Julian</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gossens</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Use of smartphone-based remote assessments of multiple sclerosis in Floodlight Open, a global, prospective, open-access study</article-title>
          <source>Sci Rep</source>
          <year>2024</year>
          <month>01</month>
          <day>02</day>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>122</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41598-023-49299-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41598-023-49299-4</pub-id>
          <pub-id pub-id-type="medline">38168498</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41598-023-49299-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC10762023</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>Jones</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Popova</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schjodt-Eriksen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Julian</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Early experience engaging patients in the use of a mobile application for tracking multiple sclerosis</article-title>
          <source>Mult Scler J</source>
          <year>2020</year>
          <pub-id pub-id-type="doi">10.1016/j.neurol.2021.02.360</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>Graves</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Elantkowski</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>YP</given-names>
            </name>
            <name name-style="western">
              <surname>Dondelinger</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lipsmeier</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bernasconi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Montalban</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Midaglia</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Assessment of upper extremity function in multiple sclerosis: feasibility of a digital pinching test</article-title>
          <source>JMIR Form Res</source>
          <year>2023</year>
          <month>10</month>
          <day>02</day>
          <volume>7</volume>
          <fpage>e46521</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://formative.jmir.org/2023//e46521/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/46521</pub-id>
          <pub-id pub-id-type="medline">37782540</pub-id>
          <pub-id pub-id-type="pii">v7i1e46521</pub-id>
          <pub-id pub-id-type="pmcid">PMC10580133</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>WY</given-names>
            </name>
            <name name-style="western">
              <surname>Bourke</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Lipsmeier</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bernasconi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Belachew</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gossens</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Graves</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Montalban</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>U-turn speed is a valid and reliable smartphone-based measure of multiple sclerosis-related gait and balance impairment</article-title>
          <source>Gait Posture</source>
          <year>2021</year>
          <month>02</month>
          <volume>84</volume>
          <fpage>120</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0966-6362(20)30650-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.gaitpost.2020.11.025</pub-id>
          <pub-id pub-id-type="medline">33310432</pub-id>
          <pub-id pub-id-type="pii">S0966-6362(20)30650-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hesser-Biber</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Leavy</surname>
              <given-names>PL</given-names>
            </name>
          </person-group>
          <source>The Practice of Qualitative Research</source>
          <year>2011</year>
          <publisher-loc>Thousand Oaks, CA</publisher-loc>
          <publisher-name>SAGE Publications, Inc</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gloyd</surname>
              <given-names>DM</given-names>
            </name>
          </person-group>
          <article-title>Positive user experience and medical adherence</article-title>
          <source>Proceedings of the 2003 International Conference on Designing Pleasurable Products and Interfaces</source>
          <year>2003</year>
          <conf-name>DPPI '03</conf-name>
          <conf-date>June 23-26, 2003</conf-date>
          <conf-loc>Pittsburgh, PA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/782901.782902</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>Leventhal</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Safer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Panagis</surname>
              <given-names>DM</given-names>
            </name>
          </person-group>
          <article-title>The impact of communications on the self-regulation of health beliefs, decisions, and behavior</article-title>
          <source>Health Educ Q</source>
          <year>1983</year>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>3</fpage>
          <lpage>29</lpage>
          <pub-id pub-id-type="doi">10.1177/109019818301000101</pub-id>
          <pub-id pub-id-type="medline">6629788</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>Lipkus</surname>
              <given-names>IM</given-names>
            </name>
            <name name-style="western">
              <surname>Hollands</surname>
              <given-names>JG</given-names>
            </name>
          </person-group>
          <article-title>The visual communication of risk</article-title>
          <source>J Natl Cancer Inst Monogr</source>
          <year>1999</year>
          <issue>25</issue>
          <fpage>149</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.1093/oxfordjournals.jncimonographs.a024191</pub-id>
          <pub-id pub-id-type="medline">10854471</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>Morrison</surname>
              <given-names>LG</given-names>
            </name>
            <name name-style="western">
              <surname>Hargood</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Pejovic</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Geraghty</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Lloyd</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Goodman</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Michaelides</surname>
              <given-names>DT</given-names>
            </name>
            <name name-style="western">
              <surname>Weston</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Musolesi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Weal</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Yardley</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The effect of timing and frequency of push notifications on usage of a smartphone-based stress management intervention: an exploratory trial</article-title>
          <source>PLoS One</source>
          <year>2017</year>
          <month>1</month>
          <day>3</day>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>e0169162</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0169162"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0169162</pub-id>
          <pub-id pub-id-type="medline">28046034</pub-id>
          <pub-id pub-id-type="pii">PONE-D-16-32583</pub-id>
          <pub-id pub-id-type="pmcid">PMC5207732</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nahum-Shani</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Spring</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Witkiewitz</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tewari</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>Just-in-Time Adaptive Interventions (JITAIs) in mobile health: key components and design principles for ongoing health behavior support</article-title>
          <source>Ann Behav Med</source>
          <year>2018</year>
          <month>05</month>
          <day>18</day>
          <volume>52</volume>
          <issue>6</issue>
          <fpage>446</fpage>
          <lpage>62</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27663578"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12160-016-9830-8</pub-id>
          <pub-id pub-id-type="medline">27663578</pub-id>
          <pub-id pub-id-type="pii">10.1007/s12160-016-9830-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC5364076</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Whelan</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Orme</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Kingsnorth</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Sherar</surname>
              <given-names>LB</given-names>
            </name>
            <name name-style="western">
              <surname>Denton</surname>
              <given-names>FL</given-names>
            </name>
            <name name-style="western">
              <surname>Esliger</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Examining the use of glucose and physical activity self-monitoring technologies in individuals at moderate to high risk of developing type 2 diabetes: randomized trial</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <month>10</month>
          <day>28</day>
          <volume>7</volume>
          <issue>10</issue>
          <fpage>e14195</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/10/e14195/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/14195</pub-id>
          <pub-id pub-id-type="medline">31661077</pub-id>
          <pub-id pub-id-type="pii">v7i10e14195</pub-id>
          <pub-id pub-id-type="pmcid">PMC6913728</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Klasnja</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Harrison</surname>
              <given-names>BL</given-names>
            </name>
            <name name-style="western">
              <surname>LeGrand</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>LaMarca</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Froehlich</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hudson</surname>
              <given-names>SE</given-names>
            </name>
          </person-group>
          <article-title>Using wearable sensors and real time inference to understand human recall of routine activities</article-title>
          <source>Proceedings of the 10th International Conference on Ubiquitous Computing</source>
          <year>2008</year>
          <conf-name>UbiComp '08</conf-name>
          <conf-date>September 21-24, 2008</conf-date>
          <conf-loc>Seoul, Korea</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1409635.1409656</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <article-title>ISO/IEC 25022:2016 systems and software engineering — systems and software quality requirements and evaluation (SQuaRE) — measurement of quality in use</article-title>
          <source>International Organization for Standardization</source>
          <year>2016</year>
          <access-date>2024-05-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/35746.html">https://www.iso.org/standard/35746.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sigg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lagerspetz</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Peltonen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Nurmi</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Tarkoma</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Exploiting usage to predict instantaneous app popularity: trend filters and retention rates</article-title>
          <source>ACM Trans Web</source>
          <year>2019</year>
          <month>04</month>
          <day>02</day>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.1145/3199677</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zuniga</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Flores</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lagerspetz</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Tarkoma</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Manner</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hui</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Manner</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Tortoise or hare? Quantifying the effects of performance on mobile app retention</article-title>
          <source>Proceedings of the World Wide Web Conference</source>
          <year>2019</year>
          <conf-name>WWW '19</conf-name>
          <conf-date>May 13-17, 2019</conf-date>
          <conf-loc>San Francisco, CA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3308558.3313428</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hennink</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kaiser</surname>
              <given-names>BN</given-names>
            </name>
          </person-group>
          <article-title>Sample sizes for saturation in qualitative research: a systematic review of empirical tests</article-title>
          <source>Soc Sci Med</source>
          <year>2022</year>
          <month>01</month>
          <volume>292</volume>
          <fpage>114523</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0277-9536(21)00855-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.socscimed.2021.114523</pub-id>
          <pub-id pub-id-type="medline">34785096</pub-id>
          <pub-id pub-id-type="pii">S0277-9536(21)00855-8</pub-id>
        </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>Rosenfelder</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>2020 app retention benchmarks</article-title>
          <source>AppsFlyer</source>
          <access-date>2022-01-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.appsflyer.com/infograms/app-retention-benchmarks-2020/">https://www.appsflyer.com/infograms/app-retention-benchmarks-2020/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gamberini</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Petrucci</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Spoto</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Spagnolli</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Embedded persuasive strategies to obtain visitors’ data: comparing reward and reciprocity in an amateur, knowledge-based website</article-title>
          <source>Proceedings of the Second International Conference on Persuasive Technology</source>
          <year>2007</year>
          <conf-name>PERSUASIVE 2007</conf-name>
          <conf-date>April 26-27, 2007</conf-date>
          <conf-loc>Palo Alto, CA</conf-loc>
          <pub-id pub-id-type="doi">10.1007/978-3-540-77006-0_24</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Midaglia</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mulero</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Montalban</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Graves</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hauser</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Julian</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schadrack</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gossens</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Scotland</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lipsmeier</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>van Beek</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bernasconi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Belachew</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Adherence and satisfaction of smartphone- and smartwatch-based remote active testing and passive monitoring in people with multiple sclerosis: nonrandomized interventional feasibility study</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>08</month>
          <day>30</day>
          <volume>21</volume>
          <issue>8</issue>
          <fpage>e14863</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/8/e14863/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/14863</pub-id>
          <pub-id pub-id-type="medline">31471961</pub-id>
          <pub-id pub-id-type="pii">v21i8e14863</pub-id>
          <pub-id pub-id-type="pmcid">PMC6743265</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Howard</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Win</surname>
              <given-names>KT</given-names>
            </name>
            <name name-style="western">
              <surname>Guan</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Mobile apps used for people living with multiple sclerosis: a scoping review</article-title>
          <source>Mult Scler Relat Disord</source>
          <year>2023</year>
          <month>05</month>
          <volume>73</volume>
          <fpage>104628</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2211-0348(23)00132-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.msard.2023.104628</pub-id>
          <pub-id pub-id-type="medline">37003008</pub-id>
          <pub-id pub-id-type="pii">S2211-0348(23)00132-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amagai</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pila</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kaat</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Nowinski</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gershon</surname>
              <given-names>RC</given-names>
            </name>
          </person-group>
          <article-title>Challenges in participant engagement and retention using mobile health apps: literature review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>05</month>
          <day>26</day>
          <volume>24</volume>
          <issue>4</issue>
          <fpage>e35120</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/4/e35120/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/35120</pub-id>
          <pub-id pub-id-type="medline">35471414</pub-id>
          <pub-id pub-id-type="pii">v24i4e35120</pub-id>
          <pub-id pub-id-type="pmcid">PMC9092233</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>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sporrel</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>van Hoof</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Simons</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>de Boer</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Ettema</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Nibbeling</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Deutekom</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kröse</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Reinforcement learning to send reminders at right moments in smartphone exercise application: a feasibility study</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2021</year>
          <month>06</month>
          <day>04</day>
          <volume>18</volume>
          <issue>11</issue>
          <fpage>6059</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph18116059"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph18116059</pub-id>
          <pub-id pub-id-type="medline">34199880</pub-id>
          <pub-id pub-id-type="pii">ijerph18116059</pub-id>
          <pub-id pub-id-type="pmcid">PMC8200090</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bremer</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Sarker</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Recruitment and retention in mobile application-based intervention studies: a critical synopsis of challenges and opportunities</article-title>
          <source>Inform Health Soc Care</source>
          <year>2023</year>
          <month>04</month>
          <day>03</day>
          <volume>48</volume>
          <issue>2</issue>
          <fpage>139</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1080/17538157.2022.2082297</pub-id>
          <pub-id pub-id-type="medline">35656732</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Polhemus</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Simblett</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dawe Lane</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Elliott</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jilka</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Negbenose</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Burke</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Weyer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Novak</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dockendorf</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Temesi</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Wykes</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Experiences of health tracking in mobile apps for multiple sclerosis: a qualitative content analysis of user reviews</article-title>
          <source>Mult Scler Relat Disord</source>
          <year>2023</year>
          <month>01</month>
          <volume>69</volume>
          <fpage>104435</fpage>
          <pub-id pub-id-type="doi">10.1016/j.msard.2022.104435</pub-id>
          <pub-id pub-id-type="medline">36493561</pub-id>
          <pub-id pub-id-type="pii">S2211-0348(22)00939-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Giunti</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kool</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rivera Romero</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Dorronzoro Zubiete</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Exploring the specific needs of persons with multiple sclerosis for mHealth solutions for physical activity: mixed-methods study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2018</year>
          <month>02</month>
          <day>09</day>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>e37</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2018/2/e37/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.8996</pub-id>
          <pub-id pub-id-type="medline">29426814</pub-id>
          <pub-id pub-id-type="pii">v6i2e37</pub-id>
          <pub-id pub-id-type="pmcid">PMC5889817</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
          <article-title>Our commitment to transparency of clinical study information</article-title>
          <source>Roche</source>
          <access-date>2024-02-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://go.roche.com/data_sharing">https://go.roche.com/data_sharing</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
