<?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">
<?covid-19-tdm?>
<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">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</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">v5i3e27882</article-id>
      <article-id pub-id-type="pmid">33724198</article-id>
      <article-id pub-id-type="doi">10.2196/27882</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>The Dutch COVID-19 Contact Tracing App (the CoronaMelder): Usability Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hallberg</surname>
            <given-names>Sarah</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Benis</surname>
            <given-names>Arriel</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Bente</surname>
            <given-names>Britt Elise</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Centre for eHealth and Wellbeing Research</institution>
            <institution>Department of Psychology, Health and Technology</institution>
            <institution>University of Twente</institution>
            <addr-line>Drienerlolaan 5</addr-line>
            <addr-line>Enschede, 7522 NB</addr-line>
            <country>Netherlands</country>
            <phone>31 53 489 9660</phone>
            <email>b.e.bente@utwente.nl</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9142-4946</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>van 't Klooster</surname>
            <given-names>Jan Willem Jaap Roderick</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5413-2792</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Schreijer</surname>
            <given-names>Maud Annemarie</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3326-1648</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Berkemeier</surname>
            <given-names>Lea</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7065-5158</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>van Gend</surname>
            <given-names>Joris Elmar</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9207-5250</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Slijkhuis</surname>
            <given-names>Peter Jan Hendrik</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3855-5699</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Kelders</surname>
            <given-names>Saskia Marion</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8949-6871</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>van Gemert-Pijnen</surname>
            <given-names>Julia Elisabeth Wilhelmina Cornelia</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6511-7240</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Centre for eHealth and Wellbeing Research</institution>
        <institution>Department of Psychology, Health and Technology</institution>
        <institution>University of Twente</institution>
        <addr-line>Enschede</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Behavioural Management and Social Sciences Lab</institution>
        <institution>Faculty of Behavioral, Management and Social Sciences</institution>
        <institution>University of Twente</institution>
        <addr-line>Enschede</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Optentia Research Focus Area</institution>
        <institution>North West University</institution>
        <addr-line>Vanderbijlpark</addr-line>
        <country>South Africa</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Britt Elise Bente <email>b.e.bente@utwente.nl</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>3</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>26</day>
        <month>3</month>
        <year>2021</year>
      </pub-date>
      <volume>5</volume>
      <issue>3</issue>
      <elocation-id>e27882</elocation-id>
      <history>
        <date date-type="received">
          <day>11</day>
          <month>2</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>25</day>
          <month>2</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>12</day>
          <month>3</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>15</day>
          <month>3</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Britt Elise Bente, Jan Willem Jaap Roderick van 't Klooster, Maud Annemarie Schreijer, Lea Berkemeier, Joris Elmar van Gend, Peter Jan Hendrik Slijkhuis, Saskia Marion Kelders, Julia Elisabeth Wilhelmina Cornelia van Gemert-Pijnen. Originally published in JMIR Formative Research (http://formative.jmir.org), 26.03.2021.</copyright-statement>
      <copyright-year>2021</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 Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on http://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2021/3/e27882" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Adoption and evaluation of contact tracing tools based on information and communications technology may expand the reach and efficacy of traditional contact tracing methods in fighting COVID-19. The Dutch Ministry of Health, Welfare and Sports initiated and developed CoronaMelder, a COVID-19 contact tracing app. This app is based on a Google/Apple Exposure Notification approach and aims to combat the spread of the coronavirus among individuals by notifying those who are at increased risk of infection due to proximity to someone who later tests positive for COVID-19. The app should support traditional contact tracing by faster tracing and greater reach compared to regular contact tracing procedures.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The main goal of this study is to investigate whether the CoronaMelder is able to support traditional contact tracing employed by public health authorities. To achieve this, usability tests were conducted to answer the following question: is the CoronaMelder user-friendly, understandable, reliable and credible, and inclusive?</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Participants (N=44) of different backgrounds were recruited: youth with varying educational levels, youth with an intellectual disability, migrants, adults (aged 40-64 years), and older adults (aged &#62;65 years) via convenience sampling in the region of Twente in the Netherlands. The app was evaluated with scenario-based, think-aloud usability tests and additional interviews. Findings were recorded via voice recordings, observation notes, and the Dutch User Experience Questionnaire, and some participants wore eye trackers to measure gaze behavior.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Our results showed that the app is easy to use, although problems occurred with understandability and accessibility. Older adults and youth with a lower education level did not understand why or under what circumstances they would receive notifications, why they must share their key (ie, their assigned identifier), and what happens after sharing. In particular, youth in the lower-education category did not trust or understand Bluetooth signals, or comprehend timing and follow-up activities after a risk exposure notification. Older adults had difficulties multitasking (speaking with a public health worker and simultaneously sharing the key in the app). Public health authorities appeared to be unprepared to receive support from the app during traditional contact tracing because their telephone conversation protocol lacks guidance, explanation, and empathy.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The study indicated that the CoronaMelder app is easy to use, but participants experienced misunderstandings about its functioning. The perceived lack of clarity led to misconceptions about the app, mostly regarding its usefulness and privacy-preserving mechanisms. Tailored and targeted communication through, for example, public campaigns or social media, is necessary to provide correct information about the app to residents in the Netherlands. Additionally, the app should be presented as part of the national coronavirus measures instead of as a stand-alone app offered to the public. Public health workers should be trained to effectively and empathetically instruct users on how to use the CoronaMelder app.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>usability testing</kwd>
        <kwd>user evaluation</kwd>
        <kwd>user experience</kwd>
        <kwd>contact tracing apps</kwd>
        <kwd>CoronaMelder</kwd>
        <kwd>COVID-19</kwd>
        <kwd>pandemic</kwd>
        <kwd>mobile apps</kwd>
        <kwd>mHealth</kwd>
        <kwd>public health</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>After the World Health Organization officially declared the COVID-19 outbreak as a pandemic, countries all over the world were urged to implement strict interventions in order to limit viral spread and to prevent overload of health care systems [<xref ref-type="bibr" rid="ref1">1</xref>]. The key essentials of these interventions focus on reducing the risk of COVID-19 transmission and consist of a package of instruments that are implemented worldwide and are based on responses to earlier pandemics. They include behavioral measures (social distancing, handwashing, personal protective equipment), adequate resources (personnel and materials for massive-scale testing, contact tracing and supported isolation), monitoring symptoms (contact tracing of possibly infected persons), and the use of digital tools [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      <p>In traditional contact tracing approaches, public health authorities (PHA) follow protocols that aim “to interrupt transmission chains by ensuring that persons who have been in contact with an infected individual are notified that they are at increased risk of infection and how to take action to prevent passing the infection to others” [<xref ref-type="bibr" rid="ref2">2</xref>]. This is important because although the coronavirus incubation period ranges between 1 and 14 days [<xref ref-type="bibr" rid="ref4">4</xref>], an infected individual can transmit the virus up to 48 hours before the onset of symptoms [<xref ref-type="bibr" rid="ref5">5</xref>]. In addition, some infected individuals do not develop symptoms but are still infectious [<xref ref-type="bibr" rid="ref6">6</xref>]. According to the contact tracing protocol, PHA (1) contact positive-tested individuals, (2) advise them about measures, (3) identify together with them how or by whom they were infected, (4) list and contact all persons they have been in contact with, and (5) arrange for individuals’ contacts to be tested [<xref ref-type="bibr" rid="ref7">7</xref>]. Despite being successful, traditional contact tracing by public health staff is labor-intensive, slow, and error-prone because people do not remember all their contacts [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. Hence, the European Centre for Disease Prevention and Control has recommended the usage of digital tools, such as mobile tracing apps, to enhance and optimize traditional contact tracing [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
      <p>Contact tracing apps could potentially provide several benefits as they (1) do not rely on the memory of the user (reminding users who they have had contact with), (2) allow contacts unknown to the user to be notified, (3) can speed up and enhance the tracing process, and (4) may facilitate further follow-up of contacts by PHA [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. However, there are also some limitations in using these apps—not everyone has a smartphone or is able to carry their phone with them at all times; older smartphones or operating systems may not support newer apps (eg, newly developed apps can only operate on smartphones with operating systems iOS 13.5 or Android version 6, or later); the tracing technology inherently produces false positives and false negatives; and there are privacy concerns [<xref ref-type="bibr" rid="ref2">2</xref>]. Furthermore, not everyone will be capable of or willing to use these apps (eg, older adults or vulnerable populations) [<xref ref-type="bibr" rid="ref10">10</xref>]. These apps may complement but can never replace conventional contact tracing systems coordinated by PHA [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
      <p>The Dutch Ministry of Health, Welfare and Sports (VWS) created conditions for the implementation of such an app. These conditions are listed in a <italic>Plan of Requirements</italic> [<xref ref-type="bibr" rid="ref11">11</xref>] and mandate that the app should (1) be anonymous and voluntary to use; (2) be developed as open source (co-designed in an open Figma design platform); (3) notify users when they are at increased risk; (4) be in line with Guidelines for Infection Control [<xref ref-type="bibr" rid="ref12">12</xref>]; (5) operate in addition to manual contact tracing (individuals should not receive help through the app that they would not receive without the app); (6) be inclusive (aimed at the largest possible relevant target group through explicit attention to language, literacy, and general/digital limitations); (7) aim to prevent reporting of false positives; and (8) involve international cooperation (eg, the app should be available on all phones operating on iOS and Android systems; connections between app users are made via Bluetooth; protection of privacy should be guaranteed [the app should be in line with common security standards and Web Content Accessibility guidelines, and a Data Privacy Impact Assessment should be performed]; and calculation of risks [distance, duration, and date of exposure] should be performed by the Google/Apple Exposure Notification framework [<xref ref-type="bibr" rid="ref13">13</xref>]).</p>
      <p>Contact tracing apps from other countries were examined by experts [<xref ref-type="bibr" rid="ref14">14</xref>] to evaluate if these apps could also be implemented in the Netherlands. However, none of the evaluated apps met the above-mentioned criteria. The VWS therefore decided to develop a COVID-19 contact tracing app using the Google/Apple Exposure Notification framework that would be interoperable (to facilitate cross-border use): the CoronaMelder app. A development team, supported by an advisory committee and four task forces, was assigned to develop and test the CoronaMelder. The design of the app followed a privacy-by-design approach to minimize privacy invasion. During the development of the CoronaMelder, the app was tested with a variety of end users in field tests [<xref ref-type="bibr" rid="ref15">15</xref>], think-aloud usability tests, practical tests, and ethical tests [<xref ref-type="bibr" rid="ref16">16</xref>]. Additionally, the digital security of the app was tested using penetration tests and data privacy impact assessments. The findings of these tests led to continuous evaluation of the development and implementation of the CoronaMelder [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
      <p>This paper focuses on the added value of the CoronaMelder app to support contact tracing. Think-aloud usability tests were conducted from June 29 to July 3, 2020, in the selected test region of Twente in the Netherlands. Twente was chosen for the current study because of its willingness to participate, available expertise, and the coronavirus-proof test infrastructure of the University of Twente. The usability tests aimed to evaluate the user-friendliness, understandability, reliability and credibility, inclusiveness, and user experience of the CoronaMelder. These criteria were chosen because the CoronaMelder could only support traditional contact tracing by PHA if the criteria are satisfied. As the app is to be used by the public, it needs to be understandable and usable by users varying in terms of digital literacy, educational background, and ethnicity. To this end, various target groups were involved in the usability tests. The findings of this study will contribute improvements in the design of the app and support the VWS in its decision whether to launch the app. This paper aims to answer the following question: is the CoronaMelder user-friendly, understandable, reliable and credible, and inclusive?</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Setting</title>
        <p>The study consisted of scenario-based usability tests with additional interview questions and the Dutch User Experience Questionnaire (UEQ-Dutch) [<xref ref-type="bibr" rid="ref17">17</xref>]. The usability tests were conducted using a scenario-based, think-aloud method [<xref ref-type="bibr" rid="ref18">18</xref>], captured by researcher observations and voice recordings, and took place from June 29 to July 3, 2020. A beta version of the app was evaluated using test iOS (version 0.1, build 172) and Android (version 0.3.1, build 107) phones. Mock-ups (Figma, version 0.7.1) were used for the scenarios that could not be tested in the beta version due to the current stage of development (ie, being able to download the app from the App Store). The study was conducted at the University of Twente’s DesignLab and in the Experivan mobile lab [<xref ref-type="bibr" rid="ref19">19</xref>], which was used to visit participants with an intellectual disability. The BMS Lab protocol for coronavirus-safe research on humans has been approved by the Executive Board of the University of Twente. Hands and equipment were disinfected before and after the tests, and national measures were followed (per the National Institute for Public Health and the Environment [RIVM] [<xref ref-type="bibr" rid="ref20">20</xref>]).</p>
      </sec>
      <sec>
        <title>Participants</title>
        <p>Participants were recruited using convenience sampling in Twente.</p>
        <p>To test whether the app is inclusive, participants from the following target groups were included:</p>
        <list list-type="bullet">
          <list-item>
            <p>Youth (&#60;21 years) with a lower level of education (n=14); this included primary education and prevocational secondary education;</p>
          </list-item>
          <list-item>
            <p>Youth (&#60;21 years) with a higher level of education (n=5); this included senior general secondary education, preuniversity senior secondary vocational education, higher vocational education, and university education;</p>
          </list-item>
          <list-item>
            <p>Youth with an intellectual disability (n=4);</p>
          </list-item>
          <list-item>
            <p>Migrants (n=2);</p>
          </list-item>
          <list-item>
            <p>Adults (40-64 years) (n=5);</p>
          </list-item>
          <list-item>
            <p>Older adults (&#62;65 years) (n=14).</p>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>Ethics Approval and Consent to Participate</title>
        <p>The study was approved by the university’s Ethical Committee (BCE200953).</p>
        <p>Participants were informed of the voluntary nature of their participation and confidentiality was guaranteed. All participants signed an informed consent, and a parent or guardian signed the informed consent for underaged participants.</p>
      </sec>
      <sec>
        <title>Procedure</title>
        <p>Adults (aged 40-64 years), older adults (aged &#62;65 years), and migrants were contacted by the researchers by telephone. In this call, an explanation was provided about the nature and purpose of the study and an appointment was scheduled for the test. Recruitment of the younger participants was arranged through an intermediary (eg, school principal, mentor). The parents or guardians of minors were contacted by the intermediary via telephone and asked for their permission to let their children participate in the study. After the call with the researcher, all participants (or intermediaries) received email confirmation of the appointment, which also included additional information on participation. <xref rid="figure1" ref-type="fig">Figure 1</xref> provides an overview of the procedure for participants.</p>
        <p>The usability tests were conducted individually and in pairs in the case of youth in the lower-education category since research shows that minors are more capable of identifying a larger number of problems and details while working in pairs [<xref ref-type="bibr" rid="ref21">21</xref>]. Before the test, the nature and purpose of the study were explained again, and permission for participation and audio recordings was given by signing the informed consent form. Parents or guardians had to sign the informed consent for minor youth. After providing additional consent, 6 participants additionally wore Tobii eye-tracker glasses (Tobii Gaming) for gaze analysis. An eye tracker was used due to people’s strong urge to move their eyes, so that the fovea is pointed at whatever stimulus they are currently thinking about or processing. This is referred to as the so-called eye-mind link [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]. This theory makes eye tracking a reliable tool for exploring visual attention. These results are discussed elsewhere [<xref ref-type="bibr" rid="ref25">25</xref>] and are outside of the scope of this paper.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Flowchart of study recruitment and procedure. The top part visualizes the recruitment methods, through both direct (n=21) and indirect (via intermediaries/representatives, n=23) channels. Included participants were tested in a stationary and mobile lab, with or without additional eye tracking, following the test protocol depicted on the right. UEQ-Dutch: Dutch User Experience Questionnaire.</p>
          </caption>
          <graphic xlink:href="formative_v5i3e27882_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The test protocol (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) started with general questions about the impact of the pandemic on the participants’ lives and about what they had already heard about contact tracing apps for COVID-19. Thereafter, each participant actioned four scenarios on the app, which represented actual use of the app (1-hour test) while simultaneously thinking aloud. Before the usability test started, participants could choose between an iOS and Android test smartphone, per their preference. The four scenarios were:</p>
        <list list-type="order">
          <list-item>
            <p>Introduction to the app: in this scenario, the app was shown in the App Store, and additional information about the app could be read. Researchers focused on whether participants understood how to download the app and where they could find additional information, as well as whether they read the information.</p>
          </list-item>
          <list-item>
            <p>Onboarding and activation of the app: in this scenario, the app’s operation was explained through onboarding steps, in which participants learned about the content of the app and confirmed the right settings for app use (allow the app to use Bluetooth and to send notifications). After onboarding was completed, the app was activated and participants had the opportunity to explore the app independently. Researchers focused on whether the explanation of the app’s function was clear, how participants acted, and whether they understood the permissions they consented to.</p>
          </list-item>
          <list-item>
            <p>Receiving notifications: in this scenario, participants receive a notification from the app about their increased risk of infection because they have been in close contact with an individual who has tested positive for COVID-19. Researchers focused on whether participants understood what a notification entailed, whether it was clear to them why they received a notification, and what an increased risk status was based on. It was also examined whether it was clear to the participants what actions they should take after receiving a notification.</p>
          </list-item>
          <list-item>
            <p>Sharing keys (telephone conversation with PHA): in this scenario, participants were asked to imagine they had recently been tested for COVID-19. During the scenario, participants received a phone call from a PHA worker, informing them of a positive test result. The PHA worker followed the Dutch Gemeentelijke Gezondheidsdienst (Regional Public Health Services) telephone script (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>), in which the participant was asked about their symptoms and received help with sharing their key (ie, their assigned identifier). First, the participant had to provide the key to the PHA worker by phone. Next, the participant had to click a button on the app interface to share the key with other app users (to warn the people they were in contact with).</p>
          </list-item>
        </list>
        <p>After completing the scenarios, closing interview questions were asked about the participants’ attitude toward the app and their willingness to use it. Additionally, a general questionnaire was administered (<xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>), collecting data on gender, age, highest completed level of education, physical limitations in using apps, and a self-reported digital skills assessment, combined with the UEQ-Dutch. Within the UEQ-Dutch, participants had to assess different characteristics of the app (eg, whether the app is easy to use, visually attractive, supportive, and reliable) on a 7-point Likert scale. Researchers focused on whether the steps to be completed on the app were clear and easy to follow, and whether participants understood the utility and consequences of sharing their key. Differences between target groups were explored to investigate whether the app is inclusive. Whether the conversation with the PHA worker matched the steps that must be completed in the app was also examined.</p>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>The recordings of the usability tests were pseudonymized (by BB) and stored on a data server at the University of Twente and were only accessible to the researchers involved. These storage and associated processes were certified according to ISO/IEC (International Organization for Standardization/International Electrotechnical Commission) 27001 and NEN 7510 standards. Recordings of 3 participants (1 youth with a higher educational level and 2 youths with an intellectual disability) were not stored correctly due to technical errors, so these participants were excluded from the study. Recordings were transcribed verbatim (by MS, LB, JG), and all transcripts were analyzed (by BB and MS) to identify fragments on user-friendliness, understandability, reliability and credibility, and inclusiveness. Relevant fragments were labeled with the main codes “user-friendliness,” “understandability,” “reliability and credibility,” and “inclusiveness” in Microsoft Excel. Next, the fragments within the main codes were analyzed axially to link fragments to each other and create new subcodes within each main code. Two researchers (BB and MS) coded 6 transcripts together to determine coding agreements. BB and MS each coded half of the other transcripts while considering the coding agreements. The coding scheme was revised several times by both researchers, and fragments were reread and recoded if necessary. </p>
        <p>Descriptive statistics were generated for the general questionnaire using SPSS, version 20 (IBM Corp) [<xref ref-type="bibr" rid="ref26">26</xref>]. The outcomes of the UEQ-Dutch were analyzed within the data analysis tool [<xref ref-type="bibr" rid="ref27">27</xref>] offered by UEQ. This tool is benchmarked every year by UEQ to keep the validity of the tools as high as possible. The data gathered from the UEQ-Dutch questionnaire were input into the tool, which resulted in descriptive statistics and graphical representations of the gathered UEQ-Dutch data.</p>
      </sec>
      <sec>
        <title>Availability of Data and Materials</title>
        <p>The transcribed data are not publicly available due to privacy restrictions but are available from the corresponding author upon reasonable request. All screenshots of the CoronaMelder app are online, available via Figma.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>This section discusses participant demographics as well as the user-friendliness, understandability, reliability and credibility, and inclusiveness results of the CoronaMelder app.</p>
      <sec>
        <title>Participant Characteristics</title>
        <p>In total, data from 44 participants were included in this study. The sample comprised 31 males (70.5%). The mean age was 40 years, ranging from 13 to 79 years, and 26 (59%) participants reported having completed a higher education level. The majority indicated not having physical limitations to using apps in general. Nearly all rated their digital skills to be between “not handy, not clumsy” and “very handy.” All participant characteristics are listed in detail in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
        <p>The following sections will focus on the research question: is the CoronaMelder user-friendly, understandable, reliable and credible, and inclusive? <xref ref-type="table" rid="table2">Table 2</xref> presents an overview of how many arguments were mentioned by participants per theme, indicating their positive or negative opinion, or whether they understood the items related to the theme. The majority of the participants were positive about the user-friendliness, reliability, and credibility of the app. Participants from all target groups indicated more negative comments than positive ones regarding the understandability of the working mechanism of the CoronaMelder.</p>
        <p><xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref> provides an overview of the number of positive and negative comments per topic, per target group.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Demographic data of participants (N=44).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="770"/>
            <col width="0"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Characteristic</td>
                <td>Value</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">Age (years), mean (range)</td>
                <td>40 (13-79)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Gender, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Male</td>
                <td colspan="2">31 (70.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Female</td>
                <td colspan="2">13 (29.5)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Highest completed education level, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>None or primary education</td>
                <td colspan="2">12 (27.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Preparatory secondary vocational education (practical)</td>
                <td colspan="2">3 (6.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Preparatory secondary vocational education (theoretical)</td>
                <td colspan="2">3 (6.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Secondary vocational education</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>General secondary education/secondary university education</td>
                <td colspan="2">6 (13.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Propedeutic (higher professional education or scientific education)</td>
                <td colspan="2">4 (9.1)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Bachelor’s degree (higher professional education or scientific education</td>
                <td colspan="2">4 (9.1)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Master’s or doctoral degree</td>
                <td colspan="2">12 (27.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Physical limitations in using apps in general, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>I have trouble reading</td>
                <td colspan="2">2 (4.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>I am dyslectic</td>
                <td colspan="2">1 (2.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>I am visually impaired</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>I have a motor disability</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>I am hard of hearing</td>
                <td colspan="2">1 (2.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>I have limited digital skills</td>
                <td colspan="2">2 (4.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Other (please specify)</td>
                <td colspan="2">1 (2.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>None</td>
                <td colspan="2">36 (81.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Did not state</td>
                <td colspan="2">1 (2.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Self-reported digital skills assessment, n (%)</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Very handy</td>
                <td colspan="2">9 (20.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Handy</td>
                <td colspan="2">22 (50.0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Not handy, not clumsy</td>
                <td colspan="2">12 (27.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Clumsy</td>
                <td colspan="2">1 (2.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Very clumsy</td>
                <td colspan="2">9 (20.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>I do not know, no opinion</td>
                <td colspan="2">0 (0)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Number of participants who stated a positive or negative comment about the CoronaMelder per topic (user-friendliness, understandability, reliability and credibility, and inclusiveness). For understandability of the notification and key-sharing system, the table demonstrates how many participants understood how the CoronaMelder app worked.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="370"/>
            <col width="0"/>
            <col width="300"/>
            <col width="0"/>
            <col width="300"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Theme</td>
                <td colspan="2">Positive/understand, n (%)</td>
                <td>Negative/did not understand, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">
                  <bold>User-friendliness</bold>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Layout</td>
                <td colspan="2">23 (53)</td>
                <td colspan="2">8 (18)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Navigation</td>
                <td colspan="2">33 (75)</td>
                <td colspan="2">9 (20)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Understandability</bold>
                </td>
                <td colspan="2">
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Language</td>
                <td colspan="2">7 (16)</td>
                <td colspan="2">10 (23)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Receiving a notification</td>
                <td colspan="2">15 (34)</td>
                <td colspan="2">21 (48)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Sharing the key</td>
                <td colspan="2">15 (34)</td>
                <td colspan="2">19 (43)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">Reliability and credibility</td>
                <td colspan="2">19 (43)</td>
                <td>6 (14)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">Inclusiveness</td>
                <td colspan="2">5 (11)</td>
                <td> 9 (20)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>User-Friendliness</title>
        <p>User-friendliness was assessed with the UEQ-Dutch and during the interview. In <xref rid="figure2" ref-type="fig">Figure 2</xref>, the outcomes of the UEQ-Dutch for the entire population are displayed for each of the six assessed scales. The scales include <italic>attractiveness</italic> (an overall impression of how much users like or dislike the app), <italic>perspicuity</italic> (how easy it is for participants to become familiar with the app), <italic>efficiency</italic> (the ability of users to use the app as intended), <italic>dependability</italic> (whether the user feels in control of the interaction with the app), <italic>stimulation</italic> (whether the app is exciting and motivating to use), and <italic>novelty</italic> (whether the app catches the interest of the user).</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Boxplot with a mean score per User Experience Questionnaire (UEQ) scale for the total population, scoring from –3 (horribly bad) to +3 (extremely good). The error bars show confidence intervals.</p>
          </caption>
          <graphic xlink:href="formative_v5i3e27882_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Participants rated the CoronaMelder app between 0.9 and 1.7 for all scales, which represents a positive evaluation (values &#62;0.8) [<xref ref-type="bibr" rid="ref28">28</xref>]. For perspicuity and efficiency, the app was rated relatively high, indicating the CoronaMelder is easy to become familiar with and participants were able to use the app as intended. The CoronaMelder scored relatively low on novelty, indicating that it was not proficient in capturing user interest.</p>
        <sec>
          <title>Layout</title>
          <p>The interviews showed that most of the participants liked the style of the app. The use of pictures within the app was appreciated, particularly by youth with an intellectual disability, who indicated having difficulties reading long texts. Representation and inclusiveness were achieved by displaying images of people from different cultures (<xref rid="figure3" ref-type="fig">Figure 3</xref>). The examples of when exposure leads to an increased risk (<xref rid="figure3" ref-type="fig">Figure 3</xref>) were commended since they helped participants better understand when they were exposed. Below is a sample response from participant 38, a youth with an intellectual disability:</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>App screenshots viewed during onboarding: (left) an example of when users are not exposed to increased risk and (right) an example of when users might be exposed to increased risk.</p>
            </caption>
            <graphic xlink:href="formative_v5i3e27882_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <disp-quote>
            <p>Question: Based on what you’ve read so far, what things do you like and recognize as being important for you?</p>
          </disp-quote>
          <disp-quote>
            <p>Participant: That it is explained in a simple way and that not too many words are getting used.</p>
          </disp-quote>
          <disp-quote>
            <p>Question: And do you think that this is addressed here?</p>
          </disp-quote>
          <disp-quote>
            <p>Participant: Yes.</p>
          </disp-quote>
          <p>One negative aspect included participants’ report of not reading long texts or only quickly scanning a text by reading the subheadings and words in bold to understand the most important information:</p>
          <disp-quote>
            <p>Well, I only read bold letters. I always want to be able to download an app quickly, so I am not going to read everything. The smaller, non-bold letters are then less important, I guess, so actually I skipped those.</p>
            <attrib>Participant 2, adult</attrib>
          </disp-quote>
          <p>A few participants suggested that videos in which the information within the app is explained in more detail would be useful because not everyone likes to read, or some may not be able to read well. Additionally, using visualizations was recommended: youth with a lower educational level and those with an intellectual disability were not able to understand how the app worked by only reading the informational texts within the app:</p>
          <disp-quote>
            <p>It might have been useful to design a human with a mobile phone, standing with a group of people, one of whom appeared to be infected, and they all use the app. If there are 5 people and 1 have the virus, then if you make it visual how the app makes contact with other apps, you can explain what Bluetooth does. Because I don’t know if everyone knows what Bluetooth is.</p>
            <attrib>Participant 20, adult</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Navigation</title>
          <p>Most comments on navigation were positive. For example, participants considered the flow of information to be logical. Regardless, multiple issues with navigation were identified. First, it was unclear to participants whether an additional information page with more explanations about the app could be opened in the Google Play Store (<xref rid="figure4" ref-type="fig">Figure 4</xref>); hence, the page was not read by every participant. In particular, older participants did not know it was possible to consult additional information, although they reported wanting to read extra information.</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>The CoronaMelder app as seen in the Google Play Store. The app can be installed by clicking the <italic>Install</italic> button. The text below this button reads: “Receive a notification if you have been in close contact with someone who later tested positive for COVID-19. This app is authorized for use in the Netherlands and uses the Google/Apple Exposure Notification system.” Additional information can be found in the <italic>About this app</italic> section. The text under this heading reads: “Help to stop the spread of the coronavirus in the Netherlands.”.</p>
            </caption>
            <graphic xlink:href="formative_v5i3e27882_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>Second, within the app, some buttons (eg, <italic>Sharing the Key</italic> and <italic>Request a Corona Test</italic>) were only visible after scrolling, which was not clear for some participants, who therefore could not find the buttons:</p>
          <disp-quote>
            <p>I didn’t know there was another fourth button […] Sometimes you think that what is visible here, is everything. Then I will not go scrolling automatically, but it could just be me.</p>
            <attrib>Participant 27, adult</attrib>
          </disp-quote>
          <p>Third, the app did not provide clear expectations to the participants on what to do after activating the app. After activation, the home screen (<xref rid="figure5" ref-type="fig">Figure 5</xref>) is displayed, informing users that the app is activated and ready for use. Younger participants automatically closed the app, whereas older participants became disoriented and reported being unsure about what to do next:</p>
          <disp-quote>
            <p>You could also put that in the text ‘the app is active and if you are sufficiently informed you don’t have to do anything’, because people will ask ‘what now?’</p>
            <attrib>Participant 8, adult</attrib>
          </disp-quote>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>The app’s home screen, which appears after the user has finished the onboarding and activation of the app. At the top (1), the app explains its activation for use. Below this are several information pages on (2) how the app works (frequently asked questions), (3) what to do if one receives a notification, (4) how to request a COVID-19 test, and (5) how to share one’s key.</p>
            </caption>
            <graphic xlink:href="formative_v5i3e27882_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>Positive remarks on navigation included the ease of onboarding and activating the app and the logical sequence flow of providing information about the app during onboarding (<xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref>). The majority of both older and younger participants indicated that they normally would click quickly through the screens and only read the information properly since they were participating in the study. The younger participants gave permission to receive notifications and use Bluetooth without delay, while the older participants thought carefully about granting permission:</p>
          <disp-quote>
            <p>Most of it is very logical. I now read the texts properly, but usually I would probably click and skip faster through it.</p>
            <attrib>Participant 4, older adult</attrib>
          </disp-quote>
        </sec>
      </sec>
      <sec>
        <title>Understandability</title>
        <p>Participants from all target groups provided more negative comments than positive ones on the understandability of several topics. Understandability problems occurred due to inconsistency in the terms used and not reading information on how the app works. Most problems concerned receiving a notification from the app and sharing the key when tested positive to support contact tracing. The app was inconsistent in the ways it referred to the coronavirus (eg, “coronavirus,” “COVID-19,” and “corona”) and to the key that should be shared after testing positive (eg, “ID,” “code,” “control code”). Furthermore, a clear definition or explanation was lacking within the app about what it means to be exposed (“exposure”) or at “increased risk” of a COVID-19 infection. The texts also include technical English vocabulary, such as “ID,” “share,” “enable,” and “upload.” Older participants in particular did not know what those words meant and were confused by them:</p>
        <disp-quote>
          <p>Now suddenly some English words are used. Well, that is a problem for some people. You should not do that. Or you should provide both languages. But now you have people who get stuck around here […] this can confuse people.</p>
          <attrib>Participant 4, older adult</attrib>
        </disp-quote>
        <sec>
          <title>Understandability of Receiving Notifications When Exposed to an Increased Risk</title>
          <p>The app sends a notification to the phone, explaining that the user is at increased risk because on a certain date they were close for more than 10 minutes to another app user who later tested positive. Opening the notification brings the user to an information page in the app that explains what the user should do.</p>
          <sec>
            <title>Being at Risk: When and How a Notification Will Be Received</title>
            <p>The test showed that the majority of participants, but in particular youth in the lower-education category, did not understand under what circumstances they would receive a notification; for example, participants believed they would receive an alarm immediately after exposure:</p>
            <disp-quote>
              <p>But I am not quite sure how it works exactly, whether it’s anonymous or when you receive a notification… If I understand correctly, you will receive a notification if you have been with someone for more than 10 minutes, but then you do not know whether the person is infected or not? And if they have been tested, you will receive a notification that they were infected. Can I figure that out based on this? Well, I don’t think so.</p>
              <attrib>Participant 32, older adult</attrib>
            </disp-quote>
            <p>Youth in the higher-education category, adults, and older adults also reported that the time between exposure and notification (within 14 days) is too long, although they can imagine why this is the case. A few participants even labeled the app as useless when they did not receive a notification immediately after being exposed because by the time they receive the notification, according to them, it is too late to take appropriate action:</p>
            <disp-quote>
              <p>It would be nice if, for example, someone has corona, then if you walk by, your phone will beep at once, like a message will be given […] Because after five days, it is already too late. If someone has the coronavirus and you immediately get a message, then you know, oh I must keep my distance.</p>
              <attrib>Participant 14, youth, lower-education category</attrib>
            </disp-quote>
            <p>None of the participants, regardless of age and education, understood when they were at increased risk for possible infection. For example, they were not aware of how long and how close they must be to someone who turned out to be infected to receive an increased risk notification. Participants also appeared not to understand that the app only communicates with other apps, so they will only receive a notification if the infected person also uses the app. It was unclear to participants that exposure detection was based on Bluetooth connection between different smartphones and based on actually being exposed to the infected persons themselves. The exposure threshold level of 10 minutes was questioned by participants. Participants (across all target groups) believed that they can also be infected when they are in close proximity to someone for less than 10 minutes.</p>
            <disp-quote>
              <p>But 10 minutes … isn’t that quite long? Suppose he has coronavirus and I stand near him for 2 minutes and then leave […] 2 minutes is enough anyway.</p>
              <attrib>Participant 15, youth, lower-education category</attrib>
            </disp-quote>
          </sec>
          <sec>
            <title>What to Do After Receiving a Notification</title>
            <p>While youth with both lower and higher educational levels indicated that the app adequately explained what to do after they receive a notification, both adults and older adults mentioned that the app does not provide clear advice and even gives contradicting advice. For example, the app advises staying at home but also continuing daily life while being aware of symptoms.</p>
            <disp-quote>
              <p>But what I do want to know – and I miss that in here – is: what should I do now? I would like to know very specifically: what should I do? What options do I have? […] Or even more socially democratic: we recommend the following […] Suppose if you receive a notification, I want to know what now? What should I do? Then I don’t need to know about symptoms or about a corona test...</p>
              <attrib>Participant 12, adult</attrib>
            </disp-quote>
            <p>Participants emphasized that the app should clarify how it notifies users, and what users are expected to do after receiving this notification. A few participants reported that they did not find the information about symptoms of the coronavirus and the possibility of requesting a test useful; they preferred to read advice on what they should do at that moment:</p>
            <disp-quote>
              <p>If you get a notification, 1) I want to know how I get this notification, 2) suppose I have received a notification, what now? What am I supposed to do? I don’t need to know about symptoms or about a corona test then.</p>
              <attrib>Participant 12, adult</attrib>
            </disp-quote>
          </sec>
        </sec>
        <sec>
          <title>Understandability of Sharing a Key After Testing Positive</title>
          <p>Various understandability issues were identified in the scenario of a positive test, as well as some positive remarks. The issues revolved around not understanding what the key is, where to find it, when to share it, and how to share it. For example, some participants mentioned they did not know what the key involved or what they were expected to do:</p>
          <disp-quote>
            <p>Well, I see now that it [the app] works through a key and I haven’t read about that anywhere yet. So, I don’t know what that key involves.</p>
            <attrib>Participant 12, adult</attrib>
          </disp-quote>
          <p>Participants were also unaware that a PHA worker would call the participant to initiate key sharing:</p>
          <disp-quote>
            <p>Now they say ‘then the PHA worker will ask you in the telephone conversation to share the key from the app and then upload the keys of the telephones you’ve been in contact with.’ What are they talking about? Which key? I don’t know what key they are talking about.</p>
            <attrib>Participant 12, adult</attrib>
          </disp-quote>
          <p>A few youths in the lower-education category or with an intellectual disability did not understand how the app knew that one had received a positive test result:</p>
          <disp-quote>
            <p>But how does the app know you have corona? Do you have to type that in the app?</p>
            <attrib>Participant 15, youth, lower-education category</attrib>
          </disp-quote>
          <p>Participants expressed different opinions regarding the text about sharing the key. Youth in the lower education category appeared to easily share the key and did not want information about what was expected from them. A few adults mentioned that the symptoms of the coronavirus and the implemented measurements are repeated too often within the app. The texts were considered to be too long, and it was reported that an overload of information should be prevented. Adults in particular expressed their indignation about the choice to share one’s key; they mentioned that if people were not willing to share the key, they should not have downloaded the app:</p>
          <disp-quote>
            <p>If I have the app, wouldn’t that obligate me to share the key? I think you should share the key, that this choice option doesn’t have to be in there. Otherwise, I wouldn’t have to install the app. We try to help get this virus under control, together. Together, therefore, means that you have to share this information with others. So, I think that this choice to share or not is ridiculous.</p>
            <attrib>Participant 5, adult</attrib>
          </disp-quote>
          <p>The steps participants must perform to share the key were clear to most youth and adults, although some older adults did not understand which process starts after they click on the <italic>Share Your Code</italic> button. It was unclear to them why they must point the key to the PHA worker first and whether they had to share the key afterward with other users by clicking on the button. Some thought they must send the key to their contacts via other communication channels:</p>
          <disp-quote>
            <p>My question is whether if it says ‘share codes’, whether this relates to the person I’ve been in contact with […] or whether codes are shared with the PHA, and the PHA then warns people I’ve been in contact with. That’s unclear to me.</p>
            <attrib>Participant 18, older adult</attrib>
          </disp-quote>
          <p>Some youths in the lower-education category pointed out that when the key is mentioned to a PHA worker, the app is not anonymous anymore since the PHA worker knows which key belongs to which person. Below is a sample exchange between participant 13 (youth, lower-education category) and the interviewer:</p>
          <disp-quote>
            <p>Participant: Well, now they suddenly have my number at the PHA?</p>
          </disp-quote>
          <disp-quote>
            <p>Interviewer: Yes, that’s right, the corona test is not anonymous. But sharing the key is.</p>
          </disp-quote>
          <disp-quote>
            <p>Participant: But if I share my key with them, then it is not completely anonymous, right?</p>
          </disp-quote>
          <p>In addition to this, some adults were irritated by the notification (<xref rid="figure6" ref-type="fig">Figure 6</xref>) that comes after sharing the key. They reported that one only used the app if one wanted to warn others and assessed the extra permission notification for sharing as unnecessary:</p>
          <disp-quote>
            <p>In my opinion, this is a strange choice. […] It was clearly emphasized at the beginning [onboarding] that the app is anonymous. I also think now, since I downloaded the app, I have to warn others. That’s not a choice, it’s a logical consequence of the fact that I installed the app. I specifically downloaded the app because it’s anonymized. This is just part of the deal. I have no idea who I’m sending it to [the key], I don’t know where I was [during the possible infection], I don’t know anything, but I do know that others will receive a signal just like I received a signal. Then I should no longer have the choice of sharing or not sharing.</p>
            <attrib>Participant 5, adult</attrib>
          </disp-quote>
          <p>Participants, with the exception of older adults, considered the steps provided by the PHA worker for sharing the key on the app to be clear and easy to follow:</p>
          <disp-quote>
            <p>It was super easy for me. Even a young child can do this on their own.</p>
            <attrib>Participant 2, adult</attrib>
          </disp-quote>
          <disp-quote>
            <p>This is unclear, how to do that, because there is nothing, the screen says only ‘close’ to me […] Yes, because, what you said to me, I cannot carry out […] No, I only have to close the blue bar […] Maybe I can do that, maybe that will work […] No, I returned to the previous screen…</p>
            <attrib>Participant 4, older adult</attrib>
          </disp-quote>
          <p>Participants did express that the simulated telephone conversation with the PHA worker lacks guided assistance, further explanations, and empathy. However, a telephone conversation was seen as a more personal approach, although youth with a lower educational level or with an intellectual disability preferred not to be called, and a few said they will not answer the phone if the PHA worker calls from a number with no calling ID. Additionally, too little attention was paid to the emotions that the message of testing positive can convey to participants. Participants suggested that PHA workers should make time to help them through the scenario, especially older adults, and should identify themselves to ensure reliability. Participants reported that the PHA worker should calmly go through the steps with the app users and not ask them to perform certain steps without providing an explanation:</p>
          <disp-quote>
            <p>I think it is pleasant if someone calls you and goes calmly through the app with you. That they don’t just say, well you have to do this and that, but that they really explain step by step what to do and where I have to click, in the app. That might be useful for older people or people who do not know or understand how the app works. I think that would be useful.</p>
            <attrib>Participant 25, youth, higher-education category</attrib>
          </disp-quote>
          <fig id="figure6" position="float">
            <label>Figure 6</label>
            <caption>
              <p>The notification that pops up after sharing the key, asking the user for permission to share their information and notify others after they click on <italic>Share the Key</italic>. The text reads: “Share your random IDs with [name of the app]. Your randomly generated IDs for the past 14 days will be used to notify others that they have been at increased risk. Your personal data and test results will not be shared with others.” The choice options are translated as “do not share” and “share codes.”.</p>
            </caption>
            <graphic xlink:href="formative_v5i3e27882_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Reliability and Credibility</title>
        <p>The app was assumed to be reliable because it was presented as a government app, and participants trust the VWS:</p>
        <disp-quote>
          <p>[Participant is reading additional information in the App Store] ‘Released by the Ministry of Health, Welfare and Sports’. Well, that seems confidential to me.</p>
          <attrib>Participant 19, youth, lower-education category</attrib>
        </disp-quote>
        <p>The explanation about data storage and anonymity (<xref rid="figure7" ref-type="fig">Figure 7</xref>) earns trust, and adult participants in particular applauded the fact that the app does not require personal data.</p>
        <disp-quote>
          <p>I think it’s good that they clearly state what makes the app safe and anonymous, I think that’s strong […] Otherwise if these weren’t listed it would scare people off.</p>
          <attrib>Participant 21, youth, higher-education category</attrib>
        </disp-quote>
        <fig id="figure7" position="float">
          <label>Figure 7</label>
          <caption>
            <p>Screenshot of frequently asked questions, with responses (left) indicating that the app does not track users’ GPS and (right) how the app is anonymous.</p>
          </caption>
          <graphic xlink:href="formative_v5i3e27882_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Although adults assessed the app as trustworthy, youth in the lower-education group did not understand how the app guarantees privacy. Participants (from different target groups) believed that they would be tracked and that others would know their name and address when they reported a positive diagnosis. These misconceptions are not only caused by a lack of explanation or by participants not reading the information provided, but also because participants mistrust the use of Bluetooth—some participants may think it will still track their location and that the app will connect with people who are not directly in close proximity to them (eg, separated by a wall):</p>
        <disp-quote>
          <p>It says that the app knows via Bluetooth whether you were close to someone […] The app doesn’t know where you were and who you are. But that’s nonsense, it has to be. If you turn on Bluetooth, you immediately see where someone is […] That’s through the Apple satellite, same for the Samsung satellite. They can always track your phone, it doesn’t matter if you have turned it [GPS tracking] off. That’s why it’s nonsense, and they should add that. But well, if that is the case, if I already know that someone will use my location, I will immediately delete the app.</p>
          <attrib>Participant 15, youth, lower-education category</attrib>
        </disp-quote>
        <p>Other participants were less doubtful about the use of Bluetooth, reporting that they thought the acquisition and storage of data was safe. Additionally, if privacy is guaranteed, multiple participants (mostly youth in the higher-education category and adults) mentioned their willingness to use the app:</p>
        <disp-quote>
          <p>Of course, in relation to privacy, you always check who monitors what data, but that will undoubtedly also be properly secured and your GPS location data will not be used or stored. That sounds safe, and I assume it is.</p>
          <attrib>Participant 4, older adult</attrib>
        </disp-quote>
      </sec>
      <sec>
        <title>Inclusiveness</title>
        <p>Differences in inclusiveness were found across age groups. In general, participants from all target groups with the exception of older adults did not have any problems using the app. Among older adults, there was a dichotomy between those who had digital skills and those who had trouble finding specific information within the app, opening and closing specific screens, and attending a telephone call while simultaneously opening and using the app:</p>
        <disp-quote>
          <p>Turn on speaker, that will be interesting. I’m going to see if I can do that. Speaker, yes, I did it! I succeeded. Well, to the Corona app, let me ask, how do I get there? These are things I’m not handy with. I have to go to the app. It works on my own phone, but now it won’t. Close everything … no, I shouldn’t do that. Ah, this one. Yes, I’m in the Corona app now.</p>
          <attrib>Participant 29, older adult</attrib>
        </disp-quote>
        <p>Older adults were able to perform the steps to share the key under the guidance of the PHA worker but had difficulty performing these steps while talking on their mobile phone. For example, older adults were not aware of how they could turn on the speaker or close the call screen and open the app. However, they signaled willingness to learn how to use the app:</p>
        <disp-quote>
          <p>Oh that’s difficult, then I have to make a phone call and look something up in the app. I don’t know how to do that. Normally I can’t even answer my phone when I’m doing something else on my phone.</p>
          <attrib>Participant 1, older adult</attrib>
        </disp-quote>
        <p>Additionally, youth with an intellectual disability appeared to lean on the researcher while conducting the test. They were in doubt and asked for confirmation each time before clicking on a screen or button. They appeared to not know what they were doing or why they must do it. For example, while sharing the key, they followed the steps the PHA worker provided them, without seeming to understand what they were doing or what would happen next.</p>
        <p>Regarding the language used in the app, participants reacted differently according to their educational or cultural background. For example, youth in the higher-education category and both adult and older adults thought the language was clear and easy to understand and that appropriate words were used to express the purpose of the app:</p>
        <disp-quote>
          <p>Of course not everyone can read properly, that can be a bottleneck. The information should actually be as simple as possible. I think it is easy to read, but I don’t know if that applies to everyone.</p>
          <attrib>Participant 11, adult</attrib>
        </disp-quote>
        <p>Youth with a lower educational level, youth with an intellectual disability, and migrants reported that the words used were too difficult to understand and texts were too long. The latter indicated that the app should work in other languages, such as English and Arabic.</p>
        <disp-quote>
          <p>P1: It has really difficult words…P2: I agree, and difficult words are annoying to read</p>
          <attrib>Paired participants 16.1 and 16.2, youth, lower-education category</attrib>
        </disp-quote>
        <disp-quote>
          <p>Some words I don’t understand so well. It would be easier for me if I could choose another language.</p>
          <attrib>Participant 41, migrant</attrib>
        </disp-quote>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study aims to answer the research question: is the CoronaMelder user-friendly, understandable, reliable and credible, and inclusive? Based on the findings, we can conclude that the CoronaMelder is easy to use. The app was seen by most as a good initiative because it warns them about possible infections, protects them, and could help avoid a second viral wave. The app was considered reliable because it is an initiative from the government (VWS). After participants read the information in the App Store, they indicated understanding how the app operates, and many were curious to become familiar with the app and expressed their intention to download it. Several general reasons why participants were willing to use the app were indicated, such as protecting themselves and their loved ones, creating sufficient support for the app, and helping to get COVID-19 under control and ease nationwide measures. However, it appeared that essential parts of the app were not understood by the participants, such as the notification system, the sharing of the authorization key via PHA, or how the app guarantees privacy.</p>
        <p>Doubts and fears were expressed regarding privacy, usefulness, and consequences of the CoronaMelder. Among the reasons for these negative attitudes were fewer positive arguments in the media and the number of false positives. Reasons not to use the CoronaMelder were expressed, such as perceiving the app as useless, thinking the coronavirus and corresponding measures were overrated, not wanting to be in quarantine (without confirmed risk), and limited phone memory or battery capacity. In terms of inclusiveness, it appears the CoronaMelder is not accessible to various target groups. Youth at a lower educational level or those with disabilities had difficulties using the app due to low literacy and language problems, and the older adults experienced difficulties related to limited digital skills.</p>
        <p>Whether the app will be effective in supporting traditional contact tracing is a concern since the majority of participants did not understand how the app operates or why there is a delay between exposure/increased risk and receiving a notification. The app provides complex information and lacks explanations; therefore, users find it unclear what actions the app expects from them. This lack of clarity has led to misconceptions about the app in terms of operation, privacy, and usefulness, thus affecting participants’ willingness to use it. This also affects the adoption of the app and adherence. Additionally, the protocol of PHA workers lacks guidance, explanation, and empathy, revealing that PHA staff are unprepared to support users with the app to the fullest extent during the pandemic (eg, with key-sharing procedures) in addition to their other responsibilities.</p>
      </sec>
      <sec>
        <title>Comparison With Studies on Other COVID-19 Contact Tracing Apps</title>
        <p>To the best of our knowledge, this is the first study to pretest the usability of the Dutch CoronaMelder app. Studies of other countries’ contact tracing apps that operate similarly to the CoronaMelder reported comparable findings on participants’ attitudes toward these kinds of apps. In a study by Horstmann et al [<xref ref-type="bibr" rid="ref29">29</xref>] on the German Corona-Warn-App, participants indicated that there were no reasons not to use the app, that the benefits would outweigh the risks, and that they believed the app would contribute to slowing down the pandemic [<xref ref-type="bibr" rid="ref29">29</xref>]. On the other hand, in studies of apps in Germany, Switzerland, and France, the most frequently mentioned reasons not to use the app were privacy concerns [<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref35">35</xref>], doubts about usefulness [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref36">36</xref>], and lack of technical equipment (eg, not all smartphone operating systems can access the apps) [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. In both of the studies on the Corona-Warn-App (Germany) [<xref ref-type="bibr" rid="ref29">29</xref>] and the SwissCovid app (Switzerland) [<xref ref-type="bibr" rid="ref34">34</xref>], as well as in a longitudinal survey about the Dutch CoronaMelder [<xref ref-type="bibr" rid="ref38">38</xref>], privacy concerns appeared to be associated with a lack of trust in the national government (or in PHA).</p>
        <p>In addition, the StopCovid app (France) showed low uptake [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref39">39</xref>] because the app appeared uninteresting and ineffective [<xref ref-type="bibr" rid="ref36">36</xref>]. The same study also reported that 71% of their participants suggested that better communication strategies would increase uptake of the app. Our study stated that the reasons mentioned for not using the app were already expressed before contact tracing apps were launched. However, it was reported [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref40">40</xref>] that these concerns were still raised after app implementation, which indicates that public health campaigns promoting contact tracing apps were not able to eliminate these concerns.</p>
      </sec>
      <sec>
        <title>Lessons Learned and Recommendations</title>
        <sec>
          <title>Adequate and Targeted Communication</title>
          <p>The tests showed that lack of clarity led to misconceptions about the app, affecting participants’ willingness to use it. Communication about the app is therefore essential for acceptance [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Targeted and tailored group-specific communication should happen through channels such as public campaigns, animations, social media, and ambassadors or influencers [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. Communication should be customized according to the aim of the app in relation to other national COVID-19 measures (eg, testing, quarantine, social distancing) [<xref ref-type="bibr" rid="ref3">3</xref>] and in collaboration with PHA and family physicians.</p>
          <p>Providing more explanations, plus emphasizing the advantages of the app in comparison to regular contact tracing, increases the likelihood that, when individuals download the app, they will know what to expect as well as what is expected of them [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. Walrave et al [<xref ref-type="bibr" rid="ref35">35</xref>] had already reported that the intention to adopt a contact tracing app increases if people know how to use the app. Hence, it would be important to have a helpdesk where people can ask questions, for example, about the purpose of contact tracing and how the CoronaMelder contributes to this, how the app operates abroad (ie, outside of the Netherlands), how anonymity is guaranteed, how data is stored, what the role of PHA will be, and who to approach in case of uncertainty or fear regarding possible risks of infection.</p>
        </sec>
        <sec>
          <title>Embedment in Traditional Contact Tracing by PHA</title>
          <p>Our study suggests that it is important for PHA workers to be well prepared in guiding users to share their keys in case of positive test results. It is important to consider the app not as a stand-alone tool but as part of the pandemic infrastructure [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref41">41</xref>] and to embed it within PHA workers’ workflow. Hence, it is crucial to provide access to tests, regardless of symptoms, but dependent on the contact date with an infected person; complete testing quickly and deliver tests results within 24 hours; clarify the scope of the app compared to other digital resources (eg, Dashboard, Thuisarts.nl) or apps to be developed; arrange international agreements about interoperability with contact tracing apps in other countries; facilitate effective and efficient interaction between PHA and the CoronaMelder; and evaluate the effects of the CoronaMelder on contact tracing, individuals’ behavior, and society.</p>
          <p>PHA should coordinate how their health care workers can guide individuals through the steps of sharing the key with the app. PHA workers should be trained to properly and empathetically explain which steps people must follow on the app. After all, PHA workers are responsible for both conducting the conversation about the test result and instructing users on the app. This means that they should be well educated about the aim and operation of the app and about their task and role during the phone call. It is therefore recommended to examine ways PHA workers can proceed to effectively and empathetically interact with app users.</p>
        </sec>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>The first strength of this study is its focus on participants of different backgrounds (age, education, etc) to test whether the CoronaMelder is accessible to all residents of the Netherlands. The second strength is the real-time pretesting of the key parts of the CoronaMelder to enable revisions before the definitive launch. The findings of the study were communicated with the software development team to exchange feedback on adjustments to the app and to revise the app during the test days. During development, minor adjustments in the app’s design were made, which means that participants who tested the app later in the study may have viewed some screens that were different to those tested by participants earlier, even though the essential parts of the app were the same. Based on the findings of this study, the VWS decided to launch the app. However, the definitive launch (October 10, 2020) was postponed due to changes in testing policy. The premise “test without symptoms,” which is an important driver for using the app, was changed due to a lack of testing capacity.</p>
      </sec>
      <sec>
        <title>Future Research</title>
        <p>To fulfil the requirements of the CoronaMelder [<xref ref-type="bibr" rid="ref11">11</xref>], the design of the app can be improved. The accessibility and understandability of the app should be customized to differences in literacy and digital skills. Think-aloud, real-world–based scenarios and eye tracking should be designed to involve end users with different literacy levels and digital skills to test use of the app in real time.</p>
        <p>Evaluation of the CoronaMelder app should focus on the key essentials of the app to support early and better contact tracing. Data should therefore be collected on use and adherence regarding follow-up actions after a notification, sharing a key to inform PHA and other users (via the app), and going into isolation when testing positive. The privacy-by-design policy could complicate gaining insight into the added value of the CoronaMelder app since it hinders data collection. A critical view is needed on how to find a balance between user-centered design and the privacy-by-design policy.</p>
        <p>Future studies should also focus on how communication campaigns can be best targeted and customized to reduce uncertainties and misconceptions, thereby improving the understanding of digital contact tracing apps as well as adoption and adherence. Overall, an adequate infrastructure (resources, personnel, capacities, etc) and powerful management tools are needed to implement the CoronaMelder and other digital tools to facilitate and optimize contact tracing to fight a pandemic. The COVID-19 pandemic has had an adverse global impact and requires an interdisciplinary approach. Future studies of the CoronaMelder app should consider the app not as a stand-alone device but as part of a coherent package of anti–COVID-19 measures to fight the pandemic, considering the impact on users, stakeholders, and testing and tracing procedures.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Test protocol.</p>
        <media xlink:href="formative_v5i3e27882_app1.docx" xlink:title="DOCX File , 31 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>PHA telephone script for positive test results.</p>
        <media xlink:href="formative_v5i3e27882_app2.docx" xlink:title="DOCX File , 14 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>The UEQ-Dutch questionnaire.</p>
        <media xlink:href="formative_v5i3e27882_app3.docx" xlink:title="DOCX File , 151 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Number of participants per target group who stated a positive or negative comment about the CoronaMelder, per topic (user-friendliness, understandability, reliability and credibility, and inclusiveness). In the case of the understandability of the notification system and sharing of the key, the table shows how many participants understood how the CoronaMelder app worked.</p>
        <media xlink:href="formative_v5i3e27882_app4.docx" xlink:title="DOCX File , 17 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Steps to onboard and activate the CoronaMelder app.</p>
        <media xlink:href="formative_v5i3e27882_app5.docx" xlink:title="DOCX File , 470 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">IEC</term>
          <def>
            <p>International Electrotechnical Commission</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">ISO</term>
          <def>
            <p>International Organization for Standardization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">PHA</term>
          <def>
            <p>public health authorities</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">RIVM</term>
          <def>
            <p>National Institute for Public Health and the Environment</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">UEQ-Dutch</term>
          <def>
            <p>Dutch User Experience Questionnaire</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">VWS</term>
          <def>
            <p>Ministry of Health, Welfare and Sports</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>We want to thank Jeanique Wegdam (premaster student, Industrial Engineering and Management, University of Twente) for her help with transcribing the interviews. The Dutch Ministry of Health, Welfare and Sports funded the usability study. The DesignLab of the University of Twente facilitated the research by means of a corona proof usability test environment. The Behavioural Management and Social Sciences Lab provided the test infrastructure and the ExperiVan to enable mobile testing.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>BB and JGP were responsible for the coordination of the usability tests. SK, BB, and JGP were involved in the creation of the scenarios and interview scheme. JK, JG, and PS delivered the materials. MS, LB, JG, and PS performed the usability tests. BB and MS analyzed the data and discussed the findings with all authors. BB was a major contributor in writing the manuscript, JGP, JK, and SK contributed to the manuscript by providing feedback and discussing the interpretation of results. All authors read and approved the final manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <article-title>WHO announces COVID-19 outbreak a pandemic</article-title>
          <source>World Health Organization</source>
          <year>2020</year>
          <month>3</month>
          <day>12</day>
          <access-date>2020-07-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/nfsz9hkr">https://tinyurl.com/nfsz9hkr</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <article-title>Mobile applications in support of contact tracing for COVID-19 - A guidance for EU EEA Member States</article-title>
          <source>European Centre for Disease Prevention and Control</source>
          <year>2020</year>
          <month>06</month>
          <day>10</day>
          <access-date>2020-07-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/y7wx2pzy">https://tinyurl.com/y7wx2pzy</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Allen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Block</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Eckersley</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Eifler</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gostin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Goux</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gruener</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hart</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Hitzig</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Krein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Langford</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nordhaus</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenthal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sethi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Siddareth</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Simons</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sitaraman</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Slaughter</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Stanger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tabarrok</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tretikov</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Weyl</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Roadmap to Pandemic Resilience</article-title>
          <source>Edmond J Safra Center for Ethics</source>
          <year>2020</year>
          <month>04</month>
          <day>20</day>
          <access-date>2020-07-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ethics.harvard.edu/Covid-Roadmap">https://ethics.harvard.edu/Covid-Roadmap</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <article-title>When to Quarantine</article-title>
          <source>Centers for Disease Control and Prevention</source>
          <access-date>2020-10-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/coronavirus/2019-ncov/if-you-are-sick/quarantine.html">https://www.cdc.gov/coronavirus/2019-ncov/if-you-are-sick/quarantine.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <article-title>Rapid risk assessment: Coronavirus disease 2019 (COVID-19) pandemic: increased transmission in the EU/EEA and the UK – seventh update</article-title>
          <source>European Centre for Disease Prevention and Control</source>
          <year>2020</year>
          <month>05</month>
          <day>25</day>
          <access-date>2020-07-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/3xmd7kt7">https://tinyurl.com/3xmd7kt7</ext-link>
          </comment>
        </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>Kretzschmar</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Rozhnova</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bootsma</surname>
              <given-names>MCJ</given-names>
            </name>
            <name name-style="western">
              <surname>van Boven</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van de Wijgert</surname>
              <given-names>JHHM</given-names>
            </name>
            <name name-style="western">
              <surname>Bonten</surname>
              <given-names>MJM</given-names>
            </name>
          </person-group>
          <article-title>Impact of delays on effectiveness of contact tracing strategies for COVID-19: a modelling study</article-title>
          <source>The Lancet Public Health</source>
          <year>2020</year>
          <month>08</month>
          <volume>5</volume>
          <issue>8</issue>
          <fpage>e452</fpage>
          <lpage>e459</lpage>
          <pub-id pub-id-type="doi">10.1016/s2468-2667(20)30157-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <article-title>Factsheet: Coronavirus: how does contact tracing work?</article-title>
          <source>Government of the Netherlands</source>
          <year>2020</year>
          <month>08</month>
          <day>18</day>
          <access-date>2020-09-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.government.nl/documents/publications/2020/06/08/coronavirus-how-does-contact-tracing-work">https://www.government.nl/documents/publications/2020/06/08/coronavirus-how-does-contact-tracing-work</ext-link>
          </comment>
        </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>Bi</surname>
              <given-names>Qifang</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Mei</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ye</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zou</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Epidemiology and Transmission of COVID-19 in Shenzhen China: Analysis of 391 cases and 1,286 of their close contacts</article-title>
          <source>medRxiv.</source>
          <comment>Preprint posted online March 27, 2020
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.medrxiv.org/content/10.1101/2020.03.03.20028423v3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1101/2020.03.03.20028423</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>YQ</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Xia</surname>
              <given-names>YY</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Qin</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>ZB</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>XK</given-names>
            </name>
            <name name-style="western">
              <surname>Yin</surname>
              <given-names>WW</given-names>
            </name>
            <name name-style="western">
              <surname>An</surname>
              <given-names>ZJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yin</surname>
              <given-names>ZD</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>QL</given-names>
            </name>
            <name name-style="western">
              <surname>Feng</surname>
              <given-names>LZ</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>ZJ</given-names>
            </name>
            <name name-style="western">
              <surname>Feng</surname>
              <given-names>ZJ</given-names>
            </name>
          </person-group>
          <article-title>[Early containment strategies and core measures for prevention and control of novel coronavirus pneumonia in China]</article-title>
          <source>Zhonghua Yu Fang Yi Xue Za Zhi</source>
          <year>2020</year>
          <month>03</month>
          <day>06</day>
          <volume>54</volume>
          <issue>3</issue>
          <fpage>239</fpage>
          <lpage>244</lpage>
          <pub-id pub-id-type="doi">10.3760/cma.j.issn.0253-9624.2020.03.003</pub-id>
          <pub-id pub-id-type="medline">32064856</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <article-title>Contact tracing for COVID-19: current evidence, options for scale-up and an assessment of resources needed</article-title>
          <source>European Centre for Disease Prevention and Control</source>
          <year>2020</year>
          <month>05</month>
          <day>05</day>
          <access-date>2020-09-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ecdc.europa.eu/en/publications-data/contact-tracing-covid-19-evidence-scale-up-assessment-resources">https://www.ecdc.europa.eu/en/publications-data/contact-tracing-covid-19-evidence-scale-up-assessment-resources</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <article-title>Programma van Eisen voor een digitale oplossing ter aanvulling op bron- en contactonderzoek van de GGD</article-title>
          <source>Rijksoverheid</source>
          <year>2020</year>
          <month>08</month>
          <day>25</day>
          <access-date>2020-09-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rijksoverheid.nl/documenten/richtlijnen/2020/08/25/programma-van-eisen-digitale-aanvulling-bron--en-contactonderzoek-ggd">https://www.rijksoverheid.nl/documenten/richtlijnen/2020/08/25/programma-van-eisen-digitale-aanvulling-bron--en-contactonderzoek-ggd</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <article-title>COVID-19 Richtlijn</article-title>
          <source>Landelijke Coördinatie Infectieziektenbestrijding (LCI)</source>
          <year>2020</year>
          <access-date>2020-11-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://lci.rivm.nl/richtlijnen/covid-19">https://lci.rivm.nl/richtlijnen/covid-19</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <article-title>Google Ondersteuning van volksgezondheidsinstanties</article-title>
          <source>Government of the Netherlands</source>
          <year>2020</year>
          <month>08</month>
          <day>28</day>
          <access-date>2020-10-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rijksoverheid.nl/documenten/publicaties/2020/08/28/google-ondersteuning-van-volksgezondheidsinstanties">https://www.rijksoverheid.nl/documenten/publicaties/2020/08/28/google-ondersteuning-van-volksgezondheidsinstanties</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>KPMG</collab>
          </person-group>
          <article-title>Securitytest potentiële Corona-apps</article-title>
          <source>Rijksoverheid</source>
          <year>2020</year>
          <month>04</month>
          <day>19</day>
          <access-date>2020-10-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rijksoverheid.nl/documenten/publicaties/2020/04/19/rapportage-veiligheidstest-potentiele-corona-apps">https://www.rijksoverheid.nl/documenten/publicaties/2020/04/19/rapportage-veiligheidstest-potentiele-corona-apps</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <article-title>Veldtest Bluetooth Validatie COVID-19 Notificatie APP</article-title>
          <source>Rijksoverheid</source>
          <year>2020</year>
          <month>06</month>
          <day>08</day>
          <access-date>2020-10-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/fa4cnz3k">https://tinyurl.com/fa4cnz3k</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <article-title>Hoe is CoronaMelder getest?</article-title>
          <source>Rijksoverheid</source>
          <access-date>2020-10-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/3zp6fkjb">https://tinyurl.com/3zp6fkjb</ext-link>
          </comment>
        </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>Hinderks</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schrepp</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Domínguez Mayo</surname>
              <given-names>FJ</given-names>
            </name>
            <name name-style="western">
              <surname>Escalona</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Thomaschewski</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Developing a UX KPI based on the user experience questionnaire</article-title>
          <source>Computer Standards &#38; Interfaces</source>
          <year>2019</year>
          <month>07</month>
          <volume>65</volume>
          <fpage>38</fpage>
          <lpage>44</lpage>
          <pub-id pub-id-type="doi">10.1016/j.csi.2019.01.007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Someren</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Barnard</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sandberg</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>The Think Aloud Method - A Practical Guide to Modelling Cognitive Processes</source>
          <year>1994</year>
          <publisher-loc>London, UK</publisher-loc>
          <publisher-name>Academic Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van 't Klooster</surname>
              <given-names>Jan-Willem</given-names>
            </name>
            <name name-style="western">
              <surname>Slijkhuis</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Langener</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Nijen Es</surname>
              <given-names>Lisanne</given-names>
            </name>
            <name name-style="western">
              <surname>Beerlage-de Jong</surname>
              <given-names>Nienke</given-names>
            </name>
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>Lisette</given-names>
            </name>
          </person-group>
          <article-title>Research on the road using the ExperiVan</article-title>
          <source>Abstract Persuasive Health Conference</source>
          <year>2021</year>
          <conf-name>Health by Tech Conference</conf-name>
          <conf-date>Jun 11-12</conf-date>
          <conf-loc>Enschede, Netherlands</conf-loc>
          <fpage>40</fpage>
          <lpage>44</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://research.utwente.nl/en/publications/research-on-the-road-using-the-experivan"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
          <article-title>COVID-19 (Nieuwe Coronavirus)</article-title>
          <source>RIVM</source>
          <access-date>2020-11-06</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.rivm.nl/coronavirus-covid-19">https://www.rivm.nl/coronavirus-covid-19</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Als</surname>
              <given-names>BS</given-names>
            </name>
            <name name-style="western">
              <surname>Jensen</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Skov</surname>
              <given-names>MB</given-names>
            </name>
          </person-group>
          <article-title>Comparison of think-aloud and constructive interaction in usability testing with children</article-title>
          <source>Proceedings of the 2005 Conference on Interaction Design and Children</source>
          <year>2005</year>
          <conf-name>IDC05: Interaction Design and Children</conf-name>
          <conf-date>June</conf-date>
          <conf-loc>Boulder, CO</conf-loc>
          <fpage>9</fpage>
          <lpage>16</lpage>
          <pub-id pub-id-type="doi">10.1145/1109540.1109542</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>Just</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Carpenter</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>A theory of reading: From eye fixations to comprehension</article-title>
          <source>Psychological Review</source>
          <year>1980</year>
          <volume>87</volume>
          <issue>4</issue>
          <fpage>329</fpage>
          <lpage>354</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1037/0033-295X.87.4.329"/>
          </comment>
          <pub-id pub-id-type="doi">10.1037/0033-295x.87.4.329</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>Rayner</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Eye movements and attention in reading, scene perception, and visual search</article-title>
          <source>Q J Exp Psychol (Hove)</source>
          <year>2009</year>
          <month>08</month>
          <volume>62</volume>
          <issue>8</issue>
          <fpage>1457</fpage>
          <lpage>506</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1080/17470210902816461"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/17470210902816461</pub-id>
          <pub-id pub-id-type="medline">19449261</pub-id>
          <pub-id pub-id-type="pii">911217562</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>Rayner</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Reingold</surname>
              <given-names>E.M.</given-names>
            </name>
          </person-group>
          <article-title>Evidence for direct cognitive control of fixation durations during reading</article-title>
          <source>Current Opinion in Behavioral Sciences</source>
          <year>2015</year>
          <month>02</month>
          <volume>1</volume>
          <fpage>107</fpage>
          <lpage>112</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.cobeha.2014.10.008"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.cobeha.2014.10.008</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van 't Klooster</surname>
              <given-names>JWJR</given-names>
            </name>
            <name name-style="western">
              <surname>Slijkhuis</surname>
              <given-names>PJH</given-names>
            </name>
            <name name-style="western">
              <surname>van Gend</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Bente</surname>
              <given-names>BE</given-names>
            </name>
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>JEWC</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kang</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Tiwary</surname>
              <given-names>US</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>WY</given-names>
            </name>
          </person-group>
          <article-title>First Eyetracking Results of Dutch CoronaMelder Contact Tracing and Notification App</article-title>
          <source>Intelligent Human Computer Interaction. IHCI 2020. Lecture Notes in Computer Science, vol 12616</source>
          <year>2021</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>199</fpage>
          <lpage>207</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="book">
          <source>IBM SPSS Statistics for Windows, Version 20.0</source>
          <year>2011</year>
          <publisher-loc>Armonk, NY</publisher-loc>
          <publisher-name>IBM Corp</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
          <source>UEQ Data Analysis Tool, Version 8</source>
          <year>2020</year>
          <access-date>2020-10-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ueq-online.org/">https://www.ueq-online.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schrepp</surname>
              <given-names>DM</given-names>
            </name>
          </person-group>
          <article-title>All you need to know to apply the UEQ successfully in your projects</article-title>
          <source>User Experience Questionnaire Handbook</source>
          <year>2019</year>
          <month>12</month>
          <day>31</day>
          <access-date>2021-03-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ueq-online.org/Material/Handbook.pdf">https://www.ueq-online.org/Material/Handbook.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Horstmann</surname>
              <given-names>KT</given-names>
            </name>
            <name name-style="western">
              <surname>Buecker</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Krasko</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kritzler</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Terwiel</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Who does or does not use the 'Corona-Warn-App' and why?</article-title>
          <source>Eur J Public Health</source>
          <year>2021</year>
          <month>02</month>
          <day>01</day>
          <volume>31</volume>
          <issue>1</issue>
          <fpage>49</fpage>
          <lpage>51</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/33340328"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/eurpub/ckaa239</pub-id>
          <pub-id pub-id-type="medline">33340328</pub-id>
          <pub-id pub-id-type="pii">6042151</pub-id>
          <pub-id pub-id-type="pmcid">PMC7799121</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>Jansen-Kosterink</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hurmuz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>den Ouden</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Velsen</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Predictors to use mobile apps for monitoring COVID-19 symptoms and contact tracing: A survey among Dutch citizens</article-title>
          <source>medRxiv.</source>
          <comment>Preprint posted online June 02, 2020
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.medrxiv.org/content/10.1101/2020.06.02.20113423v1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1101/2020.06.02.20113423</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Joo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shin</surname>
              <given-names>MM</given-names>
            </name>
          </person-group>
          <article-title>Resolving the tension between full utilization of contact tracing app services and user stress as an effort to control the COVID-19 pandemic</article-title>
          <source>Serv Bus</source>
          <year>2020</year>
          <month>09</month>
          <day>01</day>
          <volume>14</volume>
          <issue>4</issue>
          <fpage>461</fpage>
          <lpage>478</lpage>
          <pub-id pub-id-type="doi">10.1007/s11628-020-00424-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rheault</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Musulan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Explaining Support for COVID-19 Cell Phone Contact Tracing</article-title>
          <source>SOCArXiv.</source>
          <comment>Preprint posted online July 3, 2020
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://osf.io/preprints/socarxiv/8wcgz/"/>
          </comment>
          <pub-id pub-id-type="doi">10.31235/osf.io/8wcgz</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>Thomas</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Michaleff</surname>
              <given-names>ZA</given-names>
            </name>
            <name name-style="western">
              <surname>Greenwood</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Abukmail</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Glasziou</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Concerns and Misconceptions About the Australian Government's COVIDSafe App: Cross-Sectional Survey Study</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2020</year>
          <month>11</month>
          <day>04</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e23081</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2020/4/e23081/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23081</pub-id>
          <pub-id pub-id-type="medline">33048826</pub-id>
          <pub-id pub-id-type="pii">v6i4e23081</pub-id>
          <pub-id pub-id-type="pmcid">PMC7644267</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>von Wyl</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Höglinger</surname>
              <given-names>Marc</given-names>
            </name>
            <name name-style="western">
              <surname>Sieber</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kaufmann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Moser</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Serra-Burriel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ballouz</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Menges</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Frei</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Puhan</surname>
              <given-names>MA</given-names>
            </name>
          </person-group>
          <article-title>Drivers of Acceptance of COVID-19 Proximity Tracing Apps in Switzerland: Panel Survey Analysis</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2021</year>
          <month>01</month>
          <day>06</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>e25701</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2021/1/e25701/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/25701</pub-id>
          <pub-id pub-id-type="medline">33326411</pub-id>
          <pub-id pub-id-type="pii">v7i1e25701</pub-id>
          <pub-id pub-id-type="pmcid">PMC7790736</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>Walrave</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Waeterloos</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ponnet</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Adoption of a Contact Tracing App for Containing COVID-19: A Health Belief Model Approach</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2020</year>
          <month>09</month>
          <day>01</day>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>e20572</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2020/3/e20572/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/20572</pub-id>
          <pub-id pub-id-type="medline">32755882</pub-id>
          <pub-id pub-id-type="pii">v6i3e20572</pub-id>
          <pub-id pub-id-type="pmcid">PMC7470174</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>Ilaria</surname>
              <given-names>MN</given-names>
            </name>
            <name name-style="western">
              <surname>Roussel</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Thiébaut</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Tzourio</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>The French Covid-19 contact tracing app: knowledge, attitudes, beliefs and practices of students in the health domain</article-title>
          <source>medRxiv.</source>
          <comment>Preprint posted online November 12, 2020
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.medrxiv.org/content/10.1101/2020.10.23.20218214v2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1101/2020.10.23.20218214</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>Blom</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wenz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cornesse</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Rettig</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Fikel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Friedel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Möhring</surname>
              <given-names>Katja</given-names>
            </name>
            <name name-style="western">
              <surname>Naumann</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Reifenscheid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Krieger</surname>
              <given-names>U</given-names>
            </name>
          </person-group>
          <article-title>Barriers to the Large-Scale Adoption of a COVID-19 Contact Tracing App in Germany: Survey Study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>03</month>
          <day>02</day>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>e23362</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/3/e23362/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23362</pub-id>
          <pub-id pub-id-type="medline">33577466</pub-id>
          <pub-id pub-id-type="pii">v23i3e23362</pub-id>
          <pub-id pub-id-type="pmcid">PMC7927947</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Proszowska</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Jansen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>de Vries</surname>
              <given-names>PW</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 en de “intelligente lockdown" in de ogen van de burgers: deel 3: Meningen over de corona-app</article-title>
          <source>Universiteit Twente</source>
          <year>2020</year>
          <month>10</month>
          <access-date>2020-11-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://coronapapers.nl/uploads/media_item/media_item/146/86/Rapport-Lockdown-in-de-ogen-van-burgers-deel-3-Corona-app-1603965497.pdf">https://coronapapers.nl/uploads/media_item/media_item/146/86/Rapport-Lockdown-in-de-ogen-van-burgers-deel-3-Corona-app-1603965497.pdf</ext-link>
          </comment>
        </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>Jacob</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lawarée</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The adoption of contact tracing applications of COVID-19 by European governments</article-title>
          <source>Policy Design and Practice</source>
          <year>2020</year>
          <month>11</month>
          <day>28</day>
          <fpage>1</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1080/25741292.2020.1850404</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van der Laan</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>van der Waal</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>de Wit</surname>
              <given-names>JMS</given-names>
            </name>
          </person-group>
          <article-title>Eindrapportage - CoronaMelder Evaluatie</article-title>
          <source>Rijksoverheid</source>
          <year>2020</year>
          <month>12</month>
          <day>09</day>
          <access-date>2021-03-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/xr5p6n6y">https://tinyurl.com/xr5p6n6y</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <article-title>Mobile applications to support contact tracing in the EU’s fight against COVID-19: Common EU Toolbox for Member States</article-title>
          <source>European Commission</source>
          <year>2020</year>
          <access-date>2020-11-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/health/sites/health/files/ehealth/docs/covid-19_apps_en.pdf">https://ec.europa.eu/health/sites/health/files/ehealth/docs/covid-19_apps_en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
