<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id><journal-id journal-id-type="publisher-id">humanfactors</journal-id><journal-id journal-id-type="index">6</journal-id><journal-title>JMIR Human Factors</journal-title><abbrev-journal-title>JMIR Hum Factors</abbrev-journal-title><issn pub-type="epub">2292-9495</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v12i1e62776</article-id><article-id pub-id-type="doi">10.2196/62776</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>NutriDiary, a Smartphone-Based Dietary Record App: Description and Usability Evaluation</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Klasen</surname><given-names>Linda</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Koch</surname><given-names>Stefanie Anna Julia</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Benz</surname><given-names>Maike Elena</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Conrad</surname><given-names>Johanna</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Alexy</surname><given-names>Ute</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Blaszkiewicz</surname><given-names>Konrad</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Andone</surname><given-names>Ionut</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>N&#x00F6;thlings</surname><given-names>Ute</given-names></name><degrees>DrPH</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib></contrib-group><aff id="aff1"><institution>Nutritional Epidemiology, Institute of Nutrition and Food Sciences, University of Bonn</institution><addr-line>Friedrich-Hirzebruch-Allee 7</addr-line><addr-line>Bonn</addr-line><country>Germany</country></aff><aff id="aff2"><institution>German Nutrition Society (DGE)</institution><addr-line>Bonn</addr-line><country>Germany</country></aff><aff id="aff3"><institution>Department of Computer Science, University of Bonn</institution><addr-line>Bonn</addr-line><country>Germany</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Kushniruk</surname><given-names>Andre</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Collins</surname><given-names>Clare</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Budiningsari</surname><given-names>Dwi</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Ute N&#x00F6;thlings, DrPH, Nutritional Epidemiology, Institute of Nutrition and Food Sciences, University of Bonn, Friedrich-Hirzebruch-Allee 7, Bonn, 53115, Germany, 49 228 73 6049; <email>noethlings@uni-bonn.de</email></corresp></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>10</day><month>2</month><year>2025</year></pub-date><volume>12</volume><elocation-id>e62776</elocation-id><history><date date-type="received"><day>31</day><month>05</month><year>2024</year></date><date date-type="rev-recd"><day>19</day><month>12</month><year>2024</year></date><date date-type="accepted"><day>22</day><month>12</month><year>2024</year></date></history><copyright-statement>&#x00A9; Linda Klasen, Stefanie Anna Julia Koch, Maike Elena Benz, Johanna Conrad, Ute Alexy, Konrad Blaszkiewicz, Ionut Andone, Ute N&#x00F6;thlings. Originally published in JMIR Human Factors (<ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>), 10.2.2025. </copyright-statement><copyright-year>2025</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2025/1/e62776"/><abstract><sec><title>Background</title><p>Repeated applications of short-term dietary assessment instruments are recommended for estimating usual dietary intake. For this purpose, NutriDiary, a smartphone app for collecting weighed dietary records (WDRs) in the German population, was developed.</p></sec><sec><title>Objective</title><p>We aim to describe NutriDiary and evaluate its usability and acceptability.</p></sec><sec sec-type="methods"><title>Methods</title><p>NutriDiary was developed as a WDR, allowing users to enter food items via text search, barcode scanning, or free text entry. The sample for the evaluation study included 74 participants (n=51, 69% female, aged 18&#x2010;64 years), including 27 (37.5%) experts and 47 (63.5%) laypersons (including n=22, 30%, nutrition students). Participants completed a 1-day WDR and entered a predefined sample meal (n=17 foods) the following day by using NutriDiary. An evaluation questionnaire was answered from which the system usability scale (SUS) score (0&#x2010;100) was calculated. A backward selection procedure (PROC REG in SAS; SAS Institute) was used to identify potential predictors for the SUS score (age, sex, status [expert or laypersons], and operating system [iOS or Android]).</p></sec><sec sec-type="results"><title>Results</title><p>The median SUS score of 75 (IQR 63&#x2010;88) indicated good usability. Age was the only characteristic identified as a potential predictor for a lower SUS score (<italic>P</italic>&#x003C;.001). The median completion time for an individual WDR was 35 (IQR 19&#x2010;52) minutes. Older participants took longer to enter the data than younger ones (18&#x2010;30 y: median 1.5, IQR 1.1&#x2010;2.0 min/item vs 45&#x2010;64 y: median 1.8, IQR 1.3&#x2010;2.3 min/item). Most participants expressed a preference for NutriDiary over the traditional paper-based method.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Good usability and acceptability make NutriDiary promising for use in epidemiological studies.</p></sec></abstract><kwd-group><kwd>dietary assessment</kwd><kwd>food record</kwd><kwd>barcode scanning</kwd><kwd>app</kwd><kwd>mobile phone</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Usual dietary intake, the long-term average daily intake of a nutrient or food<bold>,</bold> is the relevant exposure when studying diet-health relationships in nutritional epidemiology. To estimate usual dietary intake, repeated applications of short-term dietary assessment instruments are recommended [<xref ref-type="bibr" rid="ref1">1</xref>]. Self-reported dietary intake is the most commonly used method in large-scale studies through its rapid and cost-effective use. Mostly, instruments such as 24-hour dietary recalls, food frequency questionnaires or dietary records (DRs) are used, with each of these methods having individual limitations and strengths [<xref ref-type="bibr" rid="ref2">2</xref>]. Repeated use of these traditional dietary assessment instruments is costly and burdensome for both participants and researchers [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. Innovative technologies such as web- or smartphone-based tools have the potential to facilitate self-reported dietary assessment by reducing the costs and time effort of data collection and postprocessing while achieving higher acceptance in study participants [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. Smartphone technology seems particularly promising among those innovative approaches. First, smartphones are widely available to a large proportion of the population. According to a survey conducted in 2021, over 95% of people aged older than 13 years in Germany already use a smartphone [<xref ref-type="bibr" rid="ref8">8</xref>]. Second, due to the advantage of portability and the fact that most people always carry their smartphone with them, smartphone-based tools are well suited for real-time recording of food intake [<xref ref-type="bibr" rid="ref1">1</xref>]. Third, smartphone apps can facilitate food entry through the supplementary use of an integrated barcode scanner or by using the camera function, which reduces the need to look up every food item in a database or enter it manually [<xref ref-type="bibr" rid="ref9">9</xref>]. Nowadays, a large number of commercial nutrition apps for self-tracking or nutritional advice are freely available [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. However, because of their limited scope and questionable quality of nutrient information, those apps tend to be unsuitable for dietary assessment in epidemiological studies [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. Thus, several DR apps have been developed specifically for use in epidemiological studies. In a systematic review by K&#x00F6;nig et al [<xref ref-type="bibr" rid="ref14">14</xref>], 5 core assessment features to collect data on dietary intake in scientific studies by smartphone apps were identified: photo-based assessment, assessment of serving or portion sizes, free-text description of food intake, selection from a food database, and classification systems. These features are used either alone or in combination. Thereby, the combination of photo-based recording with free-text descriptions of the consumed foods or the joint use of a food database and the assessment of serving or portion sizes were the most popular methods [<xref ref-type="bibr" rid="ref14">14</xref>].</p><p>To provide a digital alternative for paper-based dietary assessment in epidemiological studies, we developed NutriDiary, an app for conducting weighed dietary records (WDRs) with an integrated barcode scanner. This paper aims to describe the current version of NutriDiary and to report on its usability and acceptability in laypersons and experts.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>NutriDiary and the NutriDiary Database</title><sec id="s2-1-1"><title>Development and Functions of NutriDiary</title><p>NutriDiary was developed as a smartphone app to conduct WDRs within nutritional epidemiological studies. The app is available in common app stores and study participants (hereafter referred to as users) can use the app on their smartphones with personal login data (<xref ref-type="fig" rid="figure1">Figure 1A</xref>). Users can start their WDR after agreeing to the data protection regulations (<xref ref-type="fig" rid="figure1">Figure 1B</xref>). When entering a new eating occasion, users are initially asked to enter the date, time, and place of consumption (<xref ref-type="fig" rid="figure1">Figure 1C</xref>). Then, the app offers three ways to enter food, beverages, and supplements: (1) a text search and subsequent selection from the underlying database, (2) barcode scanning in the underlying database, or (3) free text entry.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>The NutriDiary app (android version): (A) screen for entering access data, (B) welcome screen, and (C) food entry.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e62776_fig01.png"/></fig><p>If a food item cannot be identified via barcode scanning, the user is guided through a standardized process for collecting all relevant product information (hereinafter referred to as the NutriScan process). Thereby, the user is asked to take photos of the brand and product name, the barcode, the ingredient list and the nutrient table following step-by-step instructions (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). This data is then sent to the NutriScan server and automatically read out using optical character reading. Researchers can access, edit, and download this data via a moderation platform. Based on the packaging information, dieticians can match detailed nutrient data from a similar product in the database or estimate detailed nutrient values by recipe simulation in order to continuously update and expand the underlying database (<xref ref-type="fig" rid="figure2">Figure 2</xref>). The recipe simulation is carried out manually using the list of ingredients and the nutritional table and is described in detail elsewhere [<xref ref-type="bibr" rid="ref15">15</xref>]. Finally, users enter the weighed amount consumed, preparation method, and quantity of potential leftovers (<xref ref-type="fig" rid="figure1">Figure 1C</xref>). If weighing is not possible, users are provided with a range of specified options in the drop-down menu to select an estimated portion size, such as teaspoon or slice. After all foods and beverages have been entered, users are redirected to the main screen, where all entered eating occasions are displayed for final review. To further ease the process of recording, NutriDiary offers some usability features. A recipe editor allows entry of custom recipes, which will be added to the user&#x2019;s personal databases. An integrated help mode provides immediate and problem-specific assistance to users by simply touching the screen element they need help with. In addition, the app includes a photo function for collecting information, for example, on meals consumed out-of-home and entered via free text. After finishing the WDR, data are submitted to a server of the University of Bonn (NutriDiary server, <xref ref-type="fig" rid="figure2">Figure 2</xref>). This server also provides an administration tool to researchers (researcher website) where scientific personnel can select project-specific settings, for example, study name, study duration or the number of recording days. The app also offers the option to integrate an individual questionnaire at the end of the recording period.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Overview of the data structure and data flow of the NutriDiary app; ND: NutriDiary; OCR: optical character reading.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e62776_fig02.png"/></fig></sec><sec id="s2-1-2"><title>Description of the NutriDiary Database</title><p>The complex database structure of NutriDiary is shown in <xref ref-type="fig" rid="figure2">Figure 2</xref>. It currently contains more than 150,000 items (approximately 25% are duplicates due to different packaging sizes and different barcodes) which come from various sources. The core database is divided into the NutriDiary nutrient database and the NutriDiary product information database. The basis of the NutriDiary nutrient database is an adaptation of the in-house food and nutrient database of the DONALD (Dortmund Nutritional and Anthropometric Longitudinally Designed) study named LEBTAB (LEBensmittelTABelle, food table) [<xref ref-type="bibr" rid="ref15">15</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. LEBTAB currently contains around 19,000 generic and branded food items (as of June 2023) with corresponding contents of energy, 82 nutrients, and other nutritional components. Data entries for generic foods are based predominantly on the German national standard food database &#x201C;Bundeslebensmittelschl&#x00FC;ssel&#x201D; (version 3.02 [<xref ref-type="bibr" rid="ref18">18</xref>]; Federal Ministry of Food and Agriculture). The energy and nutrient contents of branded foods are predominantly estimated by recipe simulation using labeled ingredients and declared nutrient contents [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. When the participant enters a food item from the NutriDiary nutrient database, this item is automatically coded and the corresponding values for energy and 82 nutrients are available. To enhance user-friendliness and allow barcode scanning, additional branded food products and barcode information were added to the NutriDiary database structure by:</p><list list-type="bullet"><list-item><p>requesting product information (product name, barcode, ingredient list, and nutrition table) from food manufacturers and others (Atrify [<xref ref-type="bibr" rid="ref19">19</xref>], a subsidiary of GS1 Germany [1WorldSync] and DATA NatuRe eG [<xref ref-type="bibr" rid="ref20">20</xref>], a cooperative to create a central data pool for organically produced foods) to set up the NutriDiary product information database, and</p></list-item><list-item><p>adding barcode information of already included branded products to the NutriDiary nutrient database by searching in open databases such as Open Food Facts [<xref ref-type="bibr" rid="ref21">21</xref>], codecheck [<xref ref-type="bibr" rid="ref22">22</xref>] (Producto Check GmbH), and Open EAN/GTIN Database (European Article Number [EAN]/Global Trade Item Number [GTIN]) [<xref ref-type="bibr" rid="ref23">23</xref>].</p></list-item></list><p>For the branded products obtained through step 1 (NutriDiary product information database), information only on the nutritional values indicated on the packaging (big 7) and the ingredient list are available (<xref ref-type="fig" rid="figure2">Figure 2</xref>). When a participant reports one of these products in a WDR, the trained dieticians match extended nutrient values of an equivalent food from the NutriDiary nutrient database or carry out a recipe simulation as already mentioned above [<xref ref-type="bibr" rid="ref15">15</xref>]. This step generates all 82 nutrients for these products and they are then transferred to the NutriDiary nutrient database, which is constantly growing.</p></sec></sec><sec id="s2-2"><title>The NutriDiary Evaluation Study</title><sec id="s2-2-1"><title>Study Design</title><p>A layperson and expert evaluation was conducted. Participants were asked to keep an individual WDR with NutriDiary for 1 day and to enter a predefined sample meal on the following day. The sample meal was identical for all participants and included 4 meals (breakfast, snack, lunch, and dinner) and was provided as a digital presentation sent to study participants via email. The sample meal comprised both, generic (n=15, presented as text) and branded food items (n=3, presented as pictures of the packaging including barcode), all labeled with a hypothetical quantity of consumption, preparation method, and type of entry (text entry vs barcode scanning). Participants were generally instructed to enter branded products via scanning the barcode. Further, 1 product was intentionally not available in both NutriDiary databases, requiring participants to complete the NutriScan process in order to add the food item to the record. Furthermore, participants were tasked to correct a logged entry and to enter a hypothetical leftover without further instructions but with reference to the NutriDiary website [<xref ref-type="bibr" rid="ref24">24</xref>] to test whether the aids provided there (frequently asked questions and help videos) fulfill their purpose (ie, helping users to help themselves). After participants completed their WDR and entered the sample meal, they were asked to answer an app-integrated evaluation questionnaire on usability and acceptability of NutriDiary on day 3. As the WDRs were not analyzed at the nutrient level, no scales were handed out for weighing the food on day 1. The participants were asked to use scales from their households.</p><p>All participants were provided with a short video giving key instructions on how to use NutriDiary before starting the WDR. The video gave a brief overview of how to use the help mode, enter foods (via text search, barcode scanning, or free text entry) and navigate the recipe book. Furthermore, participants were informed about the NutriDiary website [<xref ref-type="bibr" rid="ref24">24</xref>], where frequently asked questions and help videos for both, iOS and Android can be found. Beyond this, participants did not undergo any additional training in using the app.</p></sec><sec id="s2-2-2"><title>Recruitment of This Study&#x2019;s Population</title><p>We aimed to recruit a minimum of 51 participants, based on the assumptions outlined by Lewis and Sauro [<xref ref-type="bibr" rid="ref25">25</xref>]. This recommendation takes into account an SD of 17.7, which is typical for system usability scale (SUS) scores [<xref ref-type="bibr" rid="ref25">25</xref>], and ensures sufficient precision to achieve a 95% CI with a margin of error of &#x00B1;5 points. This study recruited both laypersons and experts. Experts (trained nutritionists with experience in the field of dietary assessment) were recruited via direct invitations (n=28). Laypersons (n=52) were recruited via oral advertisement in lectures, mailing, and personal contact by students studying nutrition and food science at the University of Bonn, and as part of a student project. The latter mainly targeted participants between 30 and 60 years of age (in the personal environment of the students and in 2 gyms) in order to increase the number of participants in middle age and older in the group of laypersons. All participants had to be fluent in the German language, have a functioning smartphone and a valid email address. Written informed consent from all participants was obtained before enrollment.</p></sec><sec id="s2-2-3"><title>Usability and Acceptability Assessment</title><p>The questionnaire on usability and acceptability included 14 questions on 3 different categories (usability, acceptance, and technical issues). The usability of NutriDiary was assessed by using the SUS by Brooke [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>], which allows for comparison between similar systems or products. In short, the SUS is a Likert scale consisting of 5 positive statements (odd-numbered) and 5 negative statements (even-numbered) to which respondents indicate their degree of agreement on a scale from 1 (strong disagreement) to 5 (strong agreement). For odd items, 1 is subtracted from the user response, and for even-numbered items, 5 is subtracted from the user response, added up and multiplied by 2.5 to convert the score ranging from 0 to 100, whereas higher scores indicate better usability. According to Bangor et al [<xref ref-type="bibr" rid="ref28">28</xref>], an SUS score below 50 is considered as &#x201C;not acceptable,&#x201D; a score between 50&#x2010;70 years as &#x201C;marginal,&#x201D; and a score above 70 as &#x201C;acceptable&#x201D; [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. In our study, an appropriate German translation of the SUS developed by SAP usability professionals of a German software corporation (SAP SE; Systems, Applications &#x0026; Products in Data Processing Societas Europaea) was used and integrated into the usability questionnaire [<xref ref-type="bibr" rid="ref30">30</xref>].</p><p>Age and sex of the participants were assessed within the evaluation questionnaire. Status (expert or layperson) was already categorized during the recruitment process. Information on the operating system was automatically recorded when NutriDiary was used and sent to the server together with the questionnaire data. To find out whether participants would prefer the app to a traditional paper-based WDR, 2 additional questions in the same structure of the SUS were added. In order to assess technical problems participants were asked whether technical errors occurred (yes or no) and, if yes, to describe the error in more detail (free text entry).</p><p>Furthermore, in-app behavior of users was recorded and evaluated. The completion time for a WDR with NutriDiary was determined by using the activity protocol of the app, in which all actions were recorded and time-stamped. For this, the time of all input activities was summed up. Interruptions of more than 5 minutes were counted as breaks and excluded from summation. As the time effort of a WDR depends on the complexity of the meals and the number of foods eaten, the relative completion time (completion time divided by the number of items) was additionally calculated. Furthermore, the percentage of estimated household measurements was of interest as well as the percentage of automatically coded WDR entries.</p></sec><sec id="s2-2-4"><title>Statistical Analyses</title><p>Results and participants&#x2019; characteristics are presented as median with their lower IQRs for continuous variables or as relative frequencies (%) for categorical variables. A backward selection procedure (PROC REG in SAS) was used to identify characteristics of participants that were potential predictors for the SUS score. The following variables were tested: sex (male or female), age (years), status (expert or layperson), and operating system (iOS or Android). All statistical analyses were conducted using SAS (version 9.4). The significance level was set at <italic>P</italic>&#x003C;.05.</p></sec></sec><sec id="s2-3"><title>Ethical Considerations</title><p>All examinations were carried out with written informed consent from study participants. The NutriDiary evaluation study was approved by the Ethics Committee of the University of Bonn (project identification 445/23). All data collected in this study has been pseudonymized to protect participant privacy. No reimbursement was provided to participants for their involvement in this study.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><p>From overall 80 study participants, 74 (27 experts) completed the NutriDiary evaluation study according to this study protocol and answered the evaluation questionnaire (<xref ref-type="table" rid="table1">Table 1</xref>). Most participants were female (51/74, 69%) and younger than 30 years of age (41/74, 55%).</p><p>The overall age ranged from 18 to 64 years and the median age was 29 years (IQR 25&#x2010;45). Overall, 54% (40/74) of the participants owned a smartphone with an iOS operating system. <xref ref-type="table" rid="table2">Table 2</xref> shows the SUS score for NutriDiary for the total study sample and stratified by sex, age groups, status, and operating system. In the overall study sample, the SUS score for NutriDiary ranged from 43 to 100 (data not shown). The median SUS score of 75 (IQR 63&#x2010;88) indicates a good usability of NutriDiary. The mean SUS score was 74 (SD 15; 95% CI 70-77; data not shown). The median SUS score was higher in women than in men (80, IQR 65&#x2010;88, vs 70, IQR 55&#x2010;78) and higher in the group of experts than in the group of laypersons (80, IQR 65&#x2010;88 vs 73, IQR 58&#x2010;88), with female laypersons having a higher SUS score than female experts (83, IQR 66&#x2010;88 vs 80, IQR 60&#x2010;85). Looking at the group of laypersons after excluding nutrition students (labeled in <xref ref-type="table" rid="table1">Tables 1</xref> and <xref ref-type="table" rid="table2">2</xref> as &#x201C;others,&#x201D; median age 55, IQR 29&#x2010;58, years), the median SUS score was 63 (IQR 50&#x2010;73).</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Characteristics of study participants of the NutriDiary evaluation study (N=74).</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Total</td><td align="left" valign="bottom">Experts</td><td align="left" valign="bottom" colspan="3">Laypersons</td></tr><tr><td align="left" valign="bottom"/><td align="left" valign="bottom"/><td align="left" valign="bottom"/><td align="left" valign="bottom">Total</td><td align="left" valign="bottom">Nutrition students</td><td align="left" valign="bottom">Others</td></tr></thead><tbody><tr><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Participants, n (%)</td><td align="left" valign="top">74 (100)</td><td align="left" valign="top">27 (36.5)</td><td align="left" valign="top">47 (63.5)</td><td align="left" valign="top">22 (47)</td><td align="left" valign="top">25 (53)</td></tr><tr><td align="left" valign="top"><bold>Sex (group), n (%)</bold></td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Women</td><td align="left" valign="top">51 (69)</td><td align="left" valign="top">23 (85)</td><td align="left" valign="top">28 (60)</td><td align="left" valign="top">19 (86)</td><td align="left" valign="top">9 (36)</td></tr><tr><td align="left" valign="top">Age, median (IQR)</td><td align="left" valign="top">29 (25&#x2010;45)</td><td align="left" valign="top">35 (28&#x2010;40)</td><td align="left" valign="top">27 (23&#x2010;56)</td><td align="left" valign="top">23 (22&#x2010;26)</td><td align="left" valign="top">55 (29&#x2010;58)</td></tr><tr><td align="left" valign="top"><bold>Age (years), n (%)</bold></td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Age group 1: 18-&#x2264;30</td><td align="left" valign="top">41 (55.4)</td><td align="left" valign="top">12 (44.4)</td><td align="left" valign="top">29 (61.7)</td><td align="left" valign="top">22 (100)</td><td align="left" valign="top">7 (28)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Age group 2:&#x003E;30-&#x2264;45</td><td align="left" valign="top">15 (20.3)</td><td align="left" valign="top">11 (40.7)</td><td align="left" valign="top">4 (8.5)</td><td align="left" valign="top">0 (0)</td><td align="left" valign="top">4 (16)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Age group 3:&#x003E;45&#x2010;65</td><td align="left" valign="top">18 (24.3)</td><td align="left" valign="top">4 (14.8)</td><td align="left" valign="top">14 (29.8)</td><td align="left" valign="top">0 (0)</td><td align="left" valign="top">14 (56)</td></tr><tr><td align="left" valign="top"><bold>Operating system, n (%)</bold></td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>iOS</td><td align="left" valign="top">40 (54)</td><td align="left" valign="top">12 (44.4)</td><td align="left" valign="top">28 (59.6)</td><td align="left" valign="top">12 (54.5)</td><td align="left" valign="top">16 (64)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Android</td><td align="left" valign="top">34 (46)</td><td align="left" valign="top">15 (55.6)</td><td align="left" valign="top">19 (40.4)</td><td align="left" valign="top">10 (45.5)</td><td align="left" valign="top">9 (36)</td></tr></tbody></table></table-wrap><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>System usability scale (SUS) score for the NutriDiary app presented as median (IQR) values.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="top" colspan="3"/><td align="left" valign="bottom" colspan="2">Total</td><td align="left" valign="bottom" colspan="2">Women</td><td align="left" valign="bottom" colspan="2">Men</td></tr><tr><td align="left" valign="top" colspan="3"/><td align="left" valign="bottom">n</td><td align="left" valign="top">Median (IQR)</td><td align="left" valign="bottom">n</td><td align="left" valign="top">Median (IQR)</td><td align="left" valign="bottom">n</td><td align="left" valign="top">Median (IQR)</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="3">SUS score</td><td align="char" char="." valign="top">74</td><td align="char" char="." valign="top">75 (63&#x2010;88)</td><td align="char" char="." valign="top">51</td><td align="char" char="." valign="top">80 (65&#x2010;88)</td><td align="char" char="." valign="top">23</td><td align="char" char="." valign="top">70 (55&#x2010;78)</td></tr><tr><td align="left" valign="top" colspan="9"><bold>Stratified by age group</bold></td></tr><tr><td align="left" valign="top"/><td align="left" valign="top" colspan="2">Age group 1: 18 -&#x2264;30 years</td><td align="char" char="." valign="top">41</td><td align="char" char="." valign="top">80 (70&#x2010;88)</td><td align="char" char="." valign="top">31</td><td align="char" char="." valign="top">83 (70&#x2010;88)</td><td align="char" char="." valign="top">10</td><td align="char" char="." valign="top">71 (63&#x2010;85)</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top" colspan="2">Age group 2: &#x003E;30 -&#x2264;45 years</td><td align="char" char="." valign="top">15</td><td align="char" char="." valign="top">80 (68&#x2010;90)</td><td align="char" char="." valign="top">11</td><td align="char" char="." valign="top">85 (65&#x2010;93)</td><td align="char" char="." valign="top">4</td><td align="char" char="." valign="top">74 (70&#x2010;78)</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top" colspan="2">Age group 3: &#x003E;45&#x2010;65 years</td><td align="char" char="." valign="top">18</td><td align="char" char="." valign="top">58 (50&#x2010;70)</td><td align="char" char="." valign="top">9</td><td align="char" char="." valign="top">58 (48&#x2010;65)</td><td align="char" char="." valign="top">9</td><td align="char" char="." valign="top">65 (50&#x2010;70)</td></tr><tr><td align="left" valign="top" colspan="9"><bold>Stratified by status</bold></td></tr><tr><td align="left" valign="top"/><td align="left" valign="top" colspan="2">Experts</td><td align="char" char="." valign="top">27</td><td align="char" char="." valign="top">80 (65&#x2010;88)</td><td align="char" char="." valign="top">23</td><td align="char" char="." valign="top">80 (60&#x2010;85)</td><td align="char" char="." valign="top">4</td><td align="char" char="." valign="top">83 (70&#x2010;90)</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top" colspan="2"><bold>Laypersons (total)</bold></td><td align="char" char="." valign="top">47</td><td align="char" char="." valign="top">73 (58&#x2010;88)</td><td align="char" char="." valign="top">28</td><td align="char" char="." valign="top">83 (66&#x2010;88)</td><td align="char" char="." valign="top">19</td><td align="char" char="." valign="top">70 (55&#x2010;73)</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">Nutrition students</td><td align="char" char="." valign="top">22</td><td align="char" char="." valign="top">85 (75&#x2010;88)</td><td align="char" char="." valign="top">19</td><td align="char" char="." valign="top">88 (78&#x2010;90)</td><td align="char" char="." valign="top">3</td><td align="char" char="." valign="top">73 (70&#x2010;85)</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">Others</td><td align="char" char="." valign="top">25</td><td align="char" char="." valign="top">63 (50&#x2010;73)</td><td align="char" char="." valign="top">9</td><td align="char" char="." valign="top">55 (48&#x2010;65)</td><td align="char" char="." valign="top">16</td><td align="char" char="." valign="top">66 (53&#x2010;73)</td></tr><tr><td align="left" valign="top" colspan="9"><bold>Stratified by operating system</bold></td></tr><tr><td align="left" valign="top"/><td align="left" valign="top" colspan="2">iOS</td><td align="char" char="." valign="top">40</td><td align="char" char="." valign="top">78 (65&#x2010;88)</td><td align="char" char="." valign="top">26</td><td align="char" char="." valign="top">80 (68&#x2010;90)</td><td align="char" char="." valign="top">14</td><td align="char" char="." valign="top">66 (55&#x2010;73)</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top" colspan="2">Android</td><td align="char" char="." valign="top">34</td><td align="char" char="." valign="top">74 (58&#x2010;85)</td><td align="char" char="." valign="top">25</td><td align="char" char="." valign="top">75 (58&#x2010;85)</td><td align="char" char="." valign="top">9</td><td align="char" char="." valign="top">73 (70&#x2010;85)</td></tr></tbody></table></table-wrap><p>Among the age groups 1 (18-&#x2264;30 y) and 2 (&#x003E;30-&#x2264;45 y), the median SUS score was noticeably higher (80, IQR 70&#x2010;88 and 80, IQR 68&#x2010;90) than in age group 3 (58, IQR 50&#x2010;70). The results of the backward selection procedure showed that age was the only characteristic identified as a potential predictor for the SUS score in the examined sample (<italic>P</italic>&#x003C;.001).</p><p><xref ref-type="fig" rid="figure3">Figure 3</xref> shows the individual statements of the SUS questionnaire and a summary of the answers given by the 74 participants, presented as box plots. The figure shows that agreement tends to be high for the positive (odd-numbered) statements and tends to be low for the negative (even-numbered) statements, as is a prerequisite for a higher SUS score. Among the positive statements, the participants showed the lowest level of agreement with statement 1 &#x201C;I think that I would like to use NutriDiary frequently.&#x201D; For the negative statements, agreement was highest for statement 8 &#x201C;I found NutriDiary very cumbersome to use.&#x201D;</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>User rating (N=74) of the individual statements of the SUS evaluating the usability and acceptability of NutriDiary, shown as box plots. The dot represents the mean and the thick stripe the median. SUS: system usability scale.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="humanfactors_v12i1e62776_fig03.png"/></fig><p><xref ref-type="table" rid="table3">Table 3</xref> shows the results of the evaluated in-app behavior logs and WDRs. The calculated median completion time for an individual WDR (day 1) with NutriDiary was 35 (IQR 19&#x2010;52) minutes. Participants needed a median of 1.6 (IQR 1.2&#x2010;2) minutes to enter an item. This relative completion time was slightly higher in age group 3 (&#x003E;45&#x2010;63 y) compared to younger participants (1.8, IQR 1.3&#x2010;2.3, min/item vs 1.5, IQR 1.1&#x2010;2, min/item). The median time it took participants to enter the sample meal in NutriDiary on day 2 was 15 (IQR 12&#x2010;18) minutes. The median relative completion time for entering the sample meal was 0.8 (IQR 0.7&#x2010;0.9) min/item. Participants in age group 3 took slightly longer than younger participants. The median proportion of already coded items was 68% (IQR 55%&#x2010;82%) and the median proportion of estimated quantities (not weighed) was 8% (IQR 0%&#x2010;29%). Younger participants (age group 1) used more estimated household measurements instead of weighing than participants in age groups 2 and 3 (0%&#x2010;26%, 8% vs 0%&#x2010;31%, 7% and 0%&#x2010;23%, and 4%, respectively).</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Completion time and proportion of items already coded for the total sample (N=74) and stratified by age groups.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Total</td><td align="left" valign="bottom">Age group 1: 18&#x2010;30 y</td><td align="left" valign="bottom">Age group 2: 31&#x2010;45 y</td><td align="left" valign="bottom">Age group 3: 46&#x2010;65 y</td></tr></thead><tbody><tr><td align="left" valign="top">Participants, n (%)</td><td align="char" char="." valign="top">74 (100)</td><td align="char" char="." valign="top">41 (55.4)</td><td align="char" char="." valign="top">15 (20.3)</td><td align="char" char="." valign="top">18 (24.3)</td></tr><tr><td align="left" valign="top">Number of entered items day 1<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="char" char="." valign="top">21 (15&#x2010;31)</td><td align="char" char="." valign="top">22 (16&#x2010;31)</td><td align="char" char="." valign="top">21 (19&#x2010;32)</td><td align="char" char="." valign="top">21 (13&#x2010;30)</td></tr><tr><td align="left" valign="top">Total completion time day 1 (min)<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="char" char="." valign="top">35 (19&#x2010;52)</td><td align="char" char="." valign="top">35 (19&#x2010;45)</td><td align="char" char="." valign="top">44 (19&#x2010;55)</td><td align="char" char="." valign="top">36 (17&#x2010;53)</td></tr><tr><td align="left" valign="top">Relative completion time day 1 (min/item)<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="char" char="." valign="top">1.6 (1.2&#x2010;2)</td><td align="char" char="." valign="top">1.5 (1.1&#x2010;2)</td><td align="char" char="." valign="top">1.5 (1.1&#x2010;2)</td><td align="char" char="." valign="top">1.8 (1.3&#x2010;2.3)</td></tr><tr><td align="left" valign="top">Total completion time sample meal (min)<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="char" char="." valign="top">15 (12&#x2010;18)</td><td align="char" char="." valign="top">14 (11&#x2010;17)</td><td align="char" char="." valign="top">17 (11&#x2010;19)</td><td align="char" char="." valign="top">17 (13&#x2010;23)</td></tr><tr><td align="left" valign="top">Relative completion time sample meal (min/item)<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="char" char="." valign="top">0.8 (0.7&#x2010;0.9)</td><td align="char" char="." valign="top">0.8 (0.6&#x2010;0.9)</td><td align="char" char="." valign="top">0.9 (0.6&#x2010;1.1)</td><td align="char" char="." valign="top">0.9 (0.7&#x2010;1.3)</td></tr><tr><td align="left" valign="top">Proportion of items already coded (%)<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="left" valign="top">68 (55&#x2010;82)</td><td align="char" char="." valign="top">63 (56&#x2010;79)</td><td align="char" char="." valign="top">77 (62&#x2010;86)</td><td align="char" char="." valign="top">71 (50&#x2010;86)</td></tr><tr><td align="left" valign="top">Proportion of estimated household quantities (%)<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="left" valign="top">8 (0&#x2010;29)</td><td align="left" valign="top">8 (0&#x2010;26)</td><td align="char" char="." valign="top">7 (0&#x2010;31)</td><td align="char" char="." valign="top">4 (0&#x2010;23)</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>Median (IQR).</p></fn></table-wrap-foot></table-wrap><p>In total, 24% (18/74) of the participants reported technical issues. In 2 cases, the app crashed, but could be reopened afterward and no data was lost. In 5 cases, participants stated that they had problems finding newly added products (this process is sometimes delayed in rare cases). Further, 4 participants reported that the selection from the drop-down menu did not work properly. In the remaining cases, participants described issues rather associated with this study design than with the technical functions of NutriDiary or gave general comments. For example, 4 participants reported that a barcode presented in the sample meal could not be scanned from the screen (probably due to varying screen-brightness and screen-resolution).</p><p>Overall, 85% (63/74) of the participants were able to enter the sample meal correctly. Of the 11 participants who made mistakes when entering the sample meal, 5 were in age group 1, 2 in age group 2, and 4 in age group 3, indicating that age did not affect the accuracy of data entry. In 2 cases, food items were missing. Further, 3 participants had difficulties in editing a WDR entry and entering hypothetical leftovers. Furthermore, 6 participants entered a different amount of food than that presented in the sample meal. When participants were asked whether they would prefer NutriDiary to the traditional paper method, a total of 77% (57/74) agreed. Only 9.5% (7/74) could imagine, that it would be easier to keep a WDR with pen-and-paper than to use NutriDiary (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>To our knowledge, an app-based WDR system with barcode scanning function for scientific studies in Germany does not exist so far. The popularity and widespread use of smartphones make NutriDiary a promising alternative to the traditional pen-and-paper approach. Different ways for entering food items (text search, barcode scanning, and free text entry) and the NutriScan function enable users to record the products they consume in a very detailed manner. The digital data output has the potential to reduce the burden for researchers also. In this study, we evaluated NutriDiary in a convenience sample of experts and laypersons and found good usability and acceptability.</p><p>The median SUS score of 75 indicated good usability of NutriDiary. The SUS score has been developed as a means to measure the overall perceived usability of a system [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. However, technology-based dietary assessment instruments for scientific purposes are very specific tools that are not designed for everyday use but to generate scientifically useful data. The collection of these data is often challenging for the participants. The first statement of the SUS questionnaire is &#x201C;I think that I would like to use this system frequently.&#x201D; This statement is unlikely to be agreed upon by many people in the case of a WDR due to the burden on participants by the method itself. Nevertheless, the advantage of the SUS score is that it offers the possibility to compare systems used in the same context [<xref ref-type="bibr" rid="ref27">27</xref>]. The median SUS score of 75 for NutriDiary (mean SUS score: 74, SD 15, for comparison) is comparable with SUS scores for other similar technology-based food records such as &#x201C;METADIETA-web&#x201D; (mean SUS score: 68, SD 15, n=26) [<xref ref-type="bibr" rid="ref31">31</xref>], the &#x201C;Eat and Track app&#x201D; (mean SUS score: 69, n=15) [<xref ref-type="bibr" rid="ref32">32</xref>] or the &#x201C;Traqq app&#x201D; (mean SUS score: 79, SD 15, n=22) [<xref ref-type="bibr" rid="ref33">33</xref>].</p><p>Age has been discussed as a major limiting factor for the use of technology-based systems [<xref ref-type="bibr" rid="ref29">29</xref>] or innovative dietary assessment instruments [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. Consistently, the results of the backward selection procedure showed that age was identified as a potential predictor for a lower SUS score in the examined sample. Further, older participants took slightly longer to complete a WDR with NutriDiary than younger ones. Feasibility testing of the digital food record METADIETA-web by Vitale et al [<xref ref-type="bibr" rid="ref31">31</xref>] also showed that the preference for using the digital tool instead of the traditional pen-and-paper method decreased with increasing age [<xref ref-type="bibr" rid="ref31">31</xref>]. Older generations did not grow up with smartphones and computers and are therefore likely to be less intuitive with apps and web-based tools than younger generations. However, longer completion times could also be explained by higher accuracy in entering items and greater patience [<xref ref-type="bibr" rid="ref36">36</xref>], which would be in line with the observation that older participants used fewer estimated household measurements instead of weighing than younger ones in our study (0%&#x2010;23%, 4% for age group 3 vs 0%&#x2010;31%, 7% and 0%&#x2010;26%, 8% for age group 2 and 1, respectively). Nevertheless, an understandable introduction to the use of the instrument might be particularly important in the group of older adults. For practical reasons, only an introductory video was sent out in this study. Our experience in training users to use the NutriDiary app shows that older people tend to ask more questions. This can only be addressed in a face-to-face conversation where it can be ensured that all relevant information is conveyed. Therefore, we recommend a personal introduction when using NutriDiary in epidemiological studies, if feasible.</p><p>The median SUS score was higher in women than in men and higher in the group of experts than in the group of laypersons. This may partly be explained by the fact that the proportion of older people was higher in men than in women and higher in the group of laypersons than in the group of experts. The group of laypersons also included students of nutritional science. Although this group certainly cannot be described as experts, the students may have some background knowledge that could have influenced the outcome. Whether this makes them more critical or less critical in their judgment remains questionable.</p><p>WDRs have the potential to provide the most accurate description of the types and amounts of the foods consumed over a specified period of time, but they are also considered to be one of the most burdensome and elaborate dietary assessment methods. When conducting a WDR, participants have to weigh and write down everything they eat and drink and always carry their kitchen scales, the record sheet, and a pen with them. This process is exhausting and time-consuming and requires a high level of cooperation from the participants [<xref ref-type="bibr" rid="ref37">37</xref>]. The median completion time for conducting a WDR with NutriDiary was 35 minutes (1.6 min/item, <xref ref-type="table" rid="table3">Table 3</xref>) and can be rated as acceptable. When looking at the median relative completion time of the sample meal (here, the amount of the presented foods was predefined), it can be assumed that the single entering process (without weighing) takes around 0.8 minutes per item. This result suggests that weighing accounts for about half the completion time. Keeping this in mind, the single entering process is roughly comparable with the reported average completion time of other text-based DR apps, for example, with &#x201C;My Meal Mate.&#x201D; Here, participants needed on average 22 minutes per day to complete a record with estimated (not weighed) portion sizes [<xref ref-type="bibr" rid="ref38">38</xref>].</p><p>Whether the NutriDiary app significantly reduces the completion time compared to the traditional pen-and-paper method is questionable, because the digital version of a WDR does not change the fact that weighing is required for this dietary assessment method. However, NutriDiary offers some advantages that can make its use more attractive than the traditional method. First, most people always carry their smartphone with them and recording &#x201C;on the go&#x201D; is more practical than using pen-and-paper. Presumably, this makes it less likely that participants forget their records and need to add the meal at a later time. Second, features such as the recipe book and the barcode scanner can make recording easier, as frequently consumed food combinations and recipes can be stored and retrieved later, and consumed products can be added more easily. Furthermore, integrated standard household measurements make it easier to estimate the quantity if weighing is not possible, for example, when eating out of home. The photo function allows participants to add a photo of the meal, which can help the postprocessing. To figure out whether NutriDiary is more attractive to study participants than the traditional pen-and-paper method, we added 2 more questions to the SUS questionnaire (, <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). The result clearly showed that the vast majority would prefer using the NutriDiary app instead of a paper-based food record. To avoid errors caused by application problems using technology-based instruments, an understandable introduction and information structure are necessary to prevent frustration and enable participants to help themselves quickly if they have difficulties. For this purpose, we designed a website where all information and support materials are centralized in 1 location [24].</p><p>When using traditional DRs in epidemiological studies, the postprocessing of the DRs is very time-consuming. The data needs to be digitized and manually coded by the study staff. In this study, 68% (IQR 55%&#x2010;82%) of the food entered in NutriDiary was already coded. Furthermore, the data was already available in digital form, suggesting less costs and time in data postprocessing, compared to the pen-and-paper method. NutriDiary was designed as an app for keeping WDRs, meaning that participants are asked to weigh all the food and drinks they consume. However, as experience showed that this is not always possible, the app also offers the choice of standard household measurements (eg, teaspoon, glass, or portion) to estimate the quantity in situations where weighing is not possible. Considering the burden of weighing all foods, this selection option might tempt participants to estimate rather than weigh. However, the proportion of estimated quantities was rather low and can be considered manageable in this study.</p><p>Within the development process of NutriDiary, building an appropriate food database structure and the collection, standardization, and integration of barcode and food packaging information to enable food entry via barcode scanning was one of the most challenging tasks. The underlying database determines the users&#x2019; success in searching for food items and is essential for the functionality and accuracy of technology based, self-administered dietary assessment tools [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Therefore, we aimed to make the database as complete as possible. Due to a high number of available branded foods and the frequently changing food market, this is a major challenge [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref40">40</xref>-<xref ref-type="bibr" rid="ref43">43</xref>]. According to the Food Federation Germany [<xref ref-type="bibr" rid="ref44">44</xref>], there are more than 170,000 food products available on the German food market. Every year, about 40,000 new products are launched and just as many disappear [<xref ref-type="bibr" rid="ref44">44</xref>]. It also happens that manufacturers change food recipes, which can also change the ingredient lists and nutritional values. These circumstances mean that the database needs to be constantly updated. To make this possible, the NutriScan function described above was developed and integrated. If the app is used regularly, the database is regularly updated with new products recorded by users.</p></sec><sec id="s4-2"><title>Strengths and Limitations</title><p>The NutriDiary evaluation study had some strengths and limitations. As NutriDiary was developed for scientific use, practicing nutritionists were also recruited as experts. Although experts are not intended users of the app, their evaluation allows for a professional view of the usability of NutriDiary. Furthermore, experts decide on the use of the assessment instrument in scientific studies, which is why their opinion on usability is of particular importance in this context. To assess user-friendliness in older age groups as well, we specifically recruited older participants. However, this study population was not representative of the general German population. Most participants were female, young, and highly educated. This limited the generalizability of our results. Nevertheless, it is important to acknowledge that participants in epidemiological studies frequently possess a higher educational status compared to the general population. In addition, participants were aware of the purpose of this study, which was to evaluate the usability and acceptability of NutriDiary, making it difficult to assess the quality and transferability of the data on the completion time and proportion of items already coded. This study aimed to assess the usability and acceptability of NutriDiary and does not contain any data on the validity of the NutriDiary app. However, providing information on the app&#x2019;s validity and psychometric properties is a critical prerequisite for its effective application. Therefore, a validation study has already been initiated and will give insights into the validity and quality of the assessed nutritional data.</p></sec><sec id="s4-3"><title>Conclusion</title><p>NutriDiary is the first smartphone based WDR app with integrated barcode scanning function for scientific purposes in Germany. The evaluation by experts and laypersons indicated an acceptable completion time, good usability and acceptability on the users&#x2019; side, whereby younger experts and laypersons tended to rate the app better than older ones. Future research will give insights into the validity and feasibility of NutriDiary in different study populations.</p></sec></sec></body><back><ack><p>The authors would like to thank all study participants for the provision of their data. Special thanks go to the students Sofie Frey, BSc, and Franziska Oidtmann, BSc, for their support with data collection. This work was supported by Diet-Body-Brain (DietBB) and the Competence Cluster in Nutrition Research funded by the Federal Ministry of Education and Research (FKZ: 01EA1410A).</p></ack><fn-group><fn fn-type="con"><p>LK and UN did the conceptualization. IA, KB, JC, SAJK, LK, MEB, and UN developed the app. LK and MEB handled data curation and worked on the formal analyses. LK wrote the original draft. SAJK, MEB, UA, JC, IA, and UN reviewed and edited the writing. UN supervised the study.</p></fn><fn fn-type="conflict"><p>The authors were involved in the development of the NutriDiary app.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">DONALD study</term><def><p>Dortmund Nutritional and Anthropometric Longitudinally Designed study</p></def></def-item><def-item><term id="abb2">DR</term><def><p>dietary record</p></def></def-item><def-item><term id="abb3">EAN</term><def><p>European Article Number</p></def></def-item><def-item><term id="abb4">GTIN</term><def><p>Global Trade Item Number</p></def></def-item><def-item><term id="abb5">LEBTAB</term><def><p>LEBensmittelTABelle, food table</p></def></def-item><def-item><term id="abb6">SAP SE</term><def><p>Systems, Applications &#x0026; Products in Data Processing Societas Europaea</p></def></def-item><def-item><term id="abb7">SUS</term><def><p>system usability scale</p></def></def-item><def-item><term id="abb8">WDR</term><def><p>weighed dietary record</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Conrad</surname><given-names>J</given-names> </name><name name-style="western"><surname>N&#x00F6;thlings</surname><given-names>U</given-names> </name></person-group><article-title>Innovative approaches to estimate individual usual dietary intake in large-scale epidemiological studies</article-title><source>Proc Nutr Soc</source><year>2017</year><month>08</month><volume>76</volume><issue>3</issue><fpage>213</fpage><lpage>219</lpage><pub-id pub-id-type="doi">10.1017/S0029665116003025</pub-id><pub-id pub-id-type="medline">28162110</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cade</surname><given-names>JE</given-names> </name></person-group><article-title>Measuring diet in the 21st century: use of new technologies</article-title><source>Proc Nutr Soc</source><year>2017</year><month>08</month><volume>76</volume><issue>3</issue><fpage>276</fpage><lpage>282</lpage><pub-id pub-id-type="doi">10.1017/S0029665116002883</pub-id><pub-id pub-id-type="medline">27976605</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Koch</surname><given-names>SAJ</given-names> </name><name name-style="western"><surname>Conrad</surname><given-names>J</given-names> </name><name name-style="western"><surname>Hierath</surname><given-names>L</given-names> </name><etal/></person-group><article-title>Adaptation and evaluation of Myfood24-Germany: a web-based self-administered 24-h dietary recall for the German adult population</article-title><source>Nutrients</source><year>2020</year><month>01</month><day>6</day><volume>12</volume><issue>1</issue><fpage>160</fpage><pub-id pub-id-type="doi">10.3390/nu12010160</pub-id><pub-id pub-id-type="medline">31935885</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Park</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Dodd</surname><given-names>KW</given-names> </name><name name-style="western"><surname>Kipnis</surname><given-names>V</given-names> </name><etal/></person-group><article-title>Comparison of self-reported dietary intakes from the automated self-administered 24-h recall, 4-d food records, and food-frequency questionnaires against recovery biomarkers</article-title><source>Am J Clin Nutr</source><year>2018</year><month>01</month><day>1</day><volume>107</volume><issue>1</issue><fpage>80</fpage><lpage>93</lpage><pub-id pub-id-type="doi">10.1093/ajcn/nqx002</pub-id><pub-id pub-id-type="medline">29381789</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sharp</surname><given-names>DB</given-names> </name><name name-style="western"><surname>Allman-Farinelli</surname><given-names>M</given-names> </name></person-group><article-title>Feasibility and validity of mobile phones to assess dietary intake</article-title><source>Nutrition</source><year>2014</year><volume>30</volume><issue>11-12</issue><fpage>1257</fpage><lpage>1266</lpage><pub-id pub-id-type="doi">10.1016/j.nut.2014.02.020</pub-id><pub-id pub-id-type="medline">24976425</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Illner</surname><given-names>AK</given-names> </name><name name-style="western"><surname>Freisling</surname><given-names>H</given-names> </name><name name-style="western"><surname>Boeing</surname><given-names>H</given-names> </name><name name-style="western"><surname>Huybrechts</surname><given-names>I</given-names> </name><name name-style="western"><surname>Crispim</surname><given-names>SP</given-names> </name><name name-style="western"><surname>Slimani</surname><given-names>N</given-names> </name></person-group><article-title>Review and evaluation of innovative technologies for measuring diet in nutritional epidemiology</article-title><source>Int J Epidemiol</source><year>2012</year><month>08</month><volume>41</volume><issue>4</issue><fpage>1187</fpage><lpage>1203</lpage><pub-id pub-id-type="doi">10.1093/ije/dys105</pub-id><pub-id pub-id-type="medline">22933652</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Thompson</surname><given-names>FE</given-names> </name><name name-style="western"><surname>Subar</surname><given-names>AF</given-names> </name><name name-style="western"><surname>Loria</surname><given-names>CM</given-names> </name><name name-style="western"><surname>Reedy</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Baranowski</surname><given-names>T</given-names> </name></person-group><article-title>Need for technological innovation in dietary assessment</article-title><source>J Am Diet Assoc</source><year>2010</year><month>01</month><volume>110</volume><issue>1</issue><fpage>48</fpage><lpage>51</lpage><pub-id pub-id-type="doi">10.1016/j.jada.2009.10.008</pub-id><pub-id pub-id-type="medline">20102826</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Tenzer</surname><given-names>F</given-names></name></person-group><article-title>Smartphone-Besitz bei Kinder und Jugendliche in Deutschland im Jahr 2021 nach Altersgruppe</article-title><source>Statista</source><year>2022</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://de.statista.com/statistik/daten/studie/1106/umfrage/handybesitz-bei-jugendlichen-nach-altersgruppen/">https://de.statista.com/statistik/daten/studie/1106/umfrage/handybesitz-bei-jugendlichen-nach-altersgruppen/</ext-link></comment></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>Mortazavi</surname><given-names>BJ</given-names> </name><name name-style="western"><surname>Gutierrez-Osuna</surname><given-names>R</given-names> </name></person-group><article-title>A review of digital innovations for diet monitoring and precision nutrition</article-title><source>J Diabetes Sci Technol</source><year>2023</year><month>01</month><volume>17</volume><issue>1</issue><fpage>217</fpage><lpage>223</lpage><pub-id pub-id-type="doi">10.1177/19322968211041356</pub-id><pub-id pub-id-type="medline">34467803</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Holzmann</surname><given-names>SL</given-names> </name><name name-style="western"><surname>Pr&#x00F6;ll</surname><given-names>K</given-names> </name><name name-style="western"><surname>Hauner</surname><given-names>H</given-names> </name><name name-style="western"><surname>Holzapfel</surname><given-names>C</given-names> </name></person-group><article-title>Nutrition apps: quality and limitations. An explorative investigation on the basis of selected apps</article-title><source>Ernahrungs Umschau</source><year>2017</year><volume>64</volume><issue>5</issue><fpage>80</fpage><lpage>89</lpage><pub-id pub-id-type="doi">10.4455/eu.2017.018</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ferrara</surname><given-names>G</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>J</given-names> </name><name name-style="western"><surname>Lin</surname><given-names>S</given-names> </name><name name-style="western"><surname>Hua</surname><given-names>J</given-names> </name><name name-style="western"><surname>Seto</surname><given-names>E</given-names> </name></person-group><article-title>A focused review of smartphone diet-tracking apps: usability, functionality, coherence with behavior change theory, and comparative validity of nutrient intake and energy estimates</article-title><source>JMIR mHealth uHealth</source><year>2019</year><month>05</month><day>17</day><volume>7</volume><issue>5</issue><fpage>e9232</fpage><pub-id pub-id-type="doi">10.2196/mhealth.9232</pub-id><pub-id pub-id-type="medline">31102369</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Maringer</surname><given-names>M</given-names> </name><name name-style="western"><surname>Wisse-Voorwinden</surname><given-names>N</given-names> </name><name name-style="western"><surname>Geelen</surname><given-names>A</given-names> </name></person-group><article-title>Food identification by barcode scanning in the Netherlands: a quality assessment of labelled food product databases underlying popular nutrition applications</article-title><source>Public Health Nutr</source><year>2019</year><month>05</month><volume>22</volume><issue>7</issue><fpage>1215</fpage><lpage>1222</lpage><pub-id pub-id-type="doi">10.1017/S136898001800157X</pub-id><pub-id pub-id-type="medline">29962361</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Fallaize</surname><given-names>R</given-names> </name><name name-style="western"><surname>Zenun Franco</surname><given-names>R</given-names> </name><name name-style="western"><surname>Pasang</surname><given-names>J</given-names> </name><name name-style="western"><surname>Hwang</surname><given-names>F</given-names> </name><name name-style="western"><surname>Lovegrove</surname><given-names>JA</given-names> </name></person-group><article-title>Popular nutrition-related mobile apps: an agreement assessment against a UK reference method</article-title><source>JMIR mHealth uHealth</source><year>2019</year><month>02</month><day>20</day><volume>7</volume><issue>2</issue><fpage>e9838</fpage><pub-id pub-id-type="doi">10.2196/mhealth.9838</pub-id><pub-id pub-id-type="medline">30785409</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>K&#x00F6;nig</surname><given-names>LM</given-names> </name><name name-style="western"><surname>Van Emmenis</surname><given-names>M</given-names> </name><name name-style="western"><surname>Nurmi</surname><given-names>J</given-names> </name><name name-style="western"><surname>Kassavou</surname><given-names>A</given-names> </name><name name-style="western"><surname>Sutton</surname><given-names>S</given-names> </name></person-group><article-title>Characteristics of smartphone-based dietary assessment tools: a systematic review</article-title><source>Health Psychol Rev</source><year>2022</year><month>12</month><volume>16</volume><issue>4</issue><fpage>526</fpage><lpage>550</lpage><pub-id pub-id-type="doi">10.1080/17437199.2021.2016066</pub-id><pub-id pub-id-type="medline">34875978</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sichert-Hellert</surname><given-names>W</given-names> </name><name name-style="western"><surname>Kersting</surname><given-names>M</given-names> </name><name name-style="western"><surname>Chahda</surname><given-names>C</given-names> </name><name name-style="western"><surname>Sch&#x00E4;fer</surname><given-names>R</given-names> </name><name name-style="western"><surname>Kroke</surname><given-names>A</given-names> </name></person-group><article-title>German food composition database for dietary evaluations in children and adolescents</article-title><source>J Food Compost Anal</source><year>2007</year><month>02</month><volume>20</volume><issue>1</issue><fpage>63</fpage><lpage>70</lpage><pub-id pub-id-type="doi">10.1016/j.jfca.2006.05.004</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kroke</surname><given-names>A</given-names> </name><name name-style="western"><surname>Manz</surname><given-names>F</given-names> </name><name name-style="western"><surname>Kersting</surname><given-names>M</given-names> </name><etal/></person-group><article-title>The DONALD Study. History, current status and future perspectives</article-title><source>Eur J Nutr</source><year>2004</year><month>02</month><volume>43</volume><issue>1</issue><fpage>45</fpage><lpage>54</lpage><pub-id pub-id-type="doi">10.1007/s00394-004-0445-7</pub-id><pub-id pub-id-type="medline">14991269</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Perrar</surname><given-names>I</given-names> </name><name name-style="western"><surname>Alexy</surname><given-names>U</given-names> </name><name name-style="western"><surname>N&#x00F6;thlings</surname><given-names>U</given-names> </name></person-group><article-title>Cohort profile update-overview of over 35 years of research in the Dortmund Nutritional and Anthropometric Longitudinally Designed (DONALD) study</article-title><source>Eur J Nutr</source><year>2024</year><month>04</month><volume>63</volume><issue>3</issue><fpage>727</fpage><lpage>740</lpage><pub-id pub-id-type="doi">10.1007/s00394-023-03290-x</pub-id><pub-id pub-id-type="medline">38151532</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="web"><article-title>Bundeslebensmittelschnl&#x00FC;ssel (BLS), version 3.02</article-title><source>Federal Ministry of Food and Agriculture</source><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.blsdb.de/">https://www.blsdb.de/</ext-link></comment></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="web"><article-title>GDSN plattform f&#x00FC;r GS1 member organisationen und communities</article-title><source>1WorldSync</source><year>2023</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.atrify.com/partner/gs1-member-organizations/?gclid=CjwKCAjwqZSlBhBwEiwAfoZUIJ8s4-oKxmTJ2Q86jycpue1mf7O2__wWg6zVBsrmh0KQ_kBbV0gloRoCPXQQAvD_BwE">https://www.atrify.com/partner/gs1-member-organizations/?gclid=CjwKCAjwqZSlBhBwEiwAfoZUIJ8s4-oKxmTJ2Q86jycpue1mf7O2__wWg6zVBsrmh0KQ_kBbV0gloRoCPXQQAvD_BwE</ext-link></comment></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="web"><source>DATA NatuRe eG</source><year>2023</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://datanature.de/">https://datanature.de/</ext-link></comment></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="web"><source>Open food facts</source><year>2023</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://de.openfoodfacts.org/discover">https://de.openfoodfacts.org/discover</ext-link></comment></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="web"><source>Codecheck</source><year>2023</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.codecheck.info/">https://www.codecheck.info/</ext-link></comment></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="web"><source>Open EAN/GTIN Database</source><year>2023</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://opengtindb.org/">https://opengtindb.org/</ext-link></comment></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="web"><person-group person-group-type="author"><collab>Universit&#x00E4;t Bonn</collab></person-group><source>NutriDiary</source><year>2024</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nutridiary-app.de">https://www.nutridiary-app.de</ext-link></comment></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Lewis</surname><given-names>J</given-names> </name><name name-style="western"><surname>Sauro</surname><given-names>J</given-names> </name></person-group><article-title>Sample sizes for a SUS score</article-title><source>MeasuringU</source><year>2022</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://measuringu.com/sample-sizes-for-sus-ci">https://measuringu.com/sample-sizes-for-sus-ci</ext-link></comment></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Brooke</surname><given-names>J</given-names> </name></person-group><source>SUS-a quick and dirty usability scale</source><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://hell.meiert.org/core/pdf/sus.pdf">https://hell.meiert.org/core/pdf/sus.pdf</ext-link></comment></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Brooke</surname><given-names>J</given-names> </name></person-group><article-title>SUS: a retrospective</article-title><source>J Usability Stud</source><year>2013</year><volume>8</volume><issue>2</issue><fpage>29</fpage><lpage>40</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://dl.acm.org/doi/10.5555/2817912.2817913">https://dl.acm.org/doi/10.5555/2817912.2817913</ext-link></comment><pub-id pub-id-type="doi">10.5555/2817912.2817913</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bangor</surname><given-names>A</given-names> </name><name name-style="western"><surname>Kortum</surname><given-names>P</given-names> </name><name name-style="western"><surname>Miller</surname><given-names>J</given-names> </name></person-group><article-title>Determining what individual SUS scores mean: adding an adjective rating scale</article-title><source>J User Exper</source><year>2009</year><volume>4</volume><issue>3</issue><fpage>114</fpage><lpage>123</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://dl.acm.org/doi/10.5555/2835587.2835589">https://dl.acm.org/doi/10.5555/2835587.2835589</ext-link></comment><pub-id pub-id-type="doi">10.5555/2835587.2835589</pub-id></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>Bangor</surname><given-names>A</given-names> </name><name name-style="western"><surname>Kortum</surname><given-names>PT</given-names> </name><name name-style="western"><surname>Miller</surname><given-names>JT</given-names> </name></person-group><article-title>An empirical evaluation of the system usability scale</article-title><source>Int J Hum Comput Interact</source><year>2008</year><month>07</month><day>29</day><volume>24</volume><issue>6</issue><fpage>574</fpage><lpage>594</lpage><pub-id pub-id-type="doi">10.1080/10447310802205776</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="web"><article-title>System usability scale &#x2013; jetzt auch auf deutsch</article-title><source>SAP Website</source><year>2023</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://blogs.sap.com/2016/02/01/system-usability-scale-jetzt-auch-auf-deutsch/">https://blogs.sap.com/2016/02/01/system-usability-scale-jetzt-auch-auf-deutsch/</ext-link></comment></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>Vitale</surname><given-names>M</given-names> </name><name name-style="western"><surname>Bruno</surname><given-names>V</given-names> </name><name name-style="western"><surname>D&#x2019;Abbronzo</surname><given-names>G</given-names> </name><etal/></person-group><article-title>Evaluation of eating habits by 7-day food record: web-PC vs. traditional paper format</article-title><source>Int J Food Sci Nutr</source><year>2023</year><volume>74</volume><issue>4</issue><fpage>580</fpage><lpage>587</lpage><pub-id pub-id-type="doi">10.1080/09637486.2023.2236808</pub-id><pub-id pub-id-type="medline">37455370</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>Wellard-Cole</surname><given-names>L</given-names> </name><name name-style="western"><surname>Potter</surname><given-names>M</given-names> </name><name name-style="western"><surname>Jung</surname><given-names>JJ</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>J</given-names> </name><name name-style="western"><surname>Kay</surname><given-names>J</given-names> </name><name name-style="western"><surname>Allman-Farinelli</surname><given-names>M</given-names> </name></person-group><article-title>A tool to measure young adults&#x2019; food intake: design and development of an australian database of foods for the eat and track smartphone app</article-title><source>JMIR mHealth uHealth</source><year>2018</year><month>11</month><day>7</day><volume>6</volume><issue>11</issue><fpage>e12136</fpage><pub-id pub-id-type="doi">10.2196/12136</pub-id><pub-id pub-id-type="medline">30404768</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>Lucassen</surname><given-names>DA</given-names> </name><name name-style="western"><surname>Brouwer-Brolsma</surname><given-names>EM</given-names> </name><name name-style="western"><surname>van de Wiel</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Siebelink</surname><given-names>E</given-names> </name><name name-style="western"><surname>Feskens</surname><given-names>EJM</given-names> </name></person-group><article-title>Iterative development of an innovative smartphone-based dietary assessment tool: Traqq</article-title><source>J Vis Exp</source><year>2021</year><month>03</month><day>19</day><issue>169</issue><pub-id pub-id-type="doi">10.3791/62032</pub-id><pub-id pub-id-type="medline">33818566</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>Gilsing</surname><given-names>A</given-names> </name><name name-style="western"><surname>Mayhew</surname><given-names>AJ</given-names> </name><name name-style="western"><surname>Payette</surname><given-names>H</given-names> </name><etal/></person-group><article-title>Validity and reliability of a short diet questionnaire to estimate dietary intake in older adults in a subsample of the canadian longitudinal study on aging</article-title><source>Nutrients</source><year>2018</year><month>10</month><day>17</day><volume>10</volume><issue>10</issue><fpage>1522</fpage><pub-id pub-id-type="doi">10.3390/nu10101522</pub-id><pub-id pub-id-type="medline">30336568</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>Carter</surname><given-names>MC</given-names> </name><name name-style="western"><surname>Albar</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Morris</surname><given-names>MA</given-names> </name><etal/></person-group><article-title>Development of a UK online 24-h dietary assessment tool: myfood24</article-title><source>Nutrients</source><year>2015</year><month>05</month><day>27</day><volume>7</volume><issue>6</issue><fpage>4016</fpage><lpage>4032</lpage><pub-id pub-id-type="doi">10.3390/nu7064016</pub-id><pub-id pub-id-type="medline">26024292</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>Kirkpatrick</surname><given-names>SI</given-names> </name><name name-style="western"><surname>Gilsing</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Hobin</surname><given-names>E</given-names> </name><etal/></person-group><article-title>Lessons from studies to evaluate an online 24-hour recall for use with children and adults in canada</article-title><source>Nutrients</source><year>2017</year><month>01</month><day>31</day><volume>9</volume><issue>2</issue><fpage>100</fpage><pub-id pub-id-type="doi">10.3390/nu9020100</pub-id><pub-id pub-id-type="medline">28146125</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>Rutishauser</surname><given-names>IHE</given-names> </name></person-group><article-title>Dietary intake measurements</article-title><source>Public Health Nutr</source><year>2005</year><month>10</month><volume>8</volume><issue>7A</issue><fpage>1100</fpage><lpage>1107</lpage><pub-id pub-id-type="doi">10.1079/phn2005798</pub-id><pub-id pub-id-type="medline">16277822</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Carter</surname><given-names>MC</given-names> </name><name name-style="western"><surname>Burley</surname><given-names>VJ</given-names> </name><name name-style="western"><surname>Nykjaer</surname><given-names>C</given-names> </name><name name-style="western"><surname>Cade</surname><given-names>JE</given-names> </name></person-group><article-title>&#x201C;My Meal Mate&#x201D; (MMM): validation of the diet measures captured on a smartphone application to facilitate weight loss</article-title><source>Br J Nutr</source><year>2013</year><month>02</month><day>14</day><volume>109</volume><issue>3</issue><fpage>539</fpage><lpage>546</lpage><pub-id pub-id-type="doi">10.1017/S0007114512001353</pub-id><pub-id pub-id-type="medline">22717334</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kupis</surname><given-names>J</given-names> </name><name name-style="western"><surname>Johnson</surname><given-names>S</given-names> </name><name name-style="western"><surname>Hallihan</surname><given-names>G</given-names> </name><name name-style="western"><surname>Olstad</surname><given-names>DL</given-names> </name></person-group><article-title>Assessing the usability of the Automated Self-Administered Dietary Assessment Tool (ASA24) among low-income adults</article-title><source>Nutrients</source><year>2019</year><month>01</month><day>10</day><volume>11</volume><issue>1</issue><fpage>132</fpage><pub-id pub-id-type="doi">10.3390/nu11010132</pub-id><pub-id pub-id-type="medline">30634581</pub-id></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ock&#x00E9;</surname><given-names>MC</given-names> </name><name name-style="western"><surname>Westenbrink</surname><given-names>S</given-names> </name><name name-style="western"><surname>van Rossum</surname><given-names>CTM</given-names> </name><name name-style="western"><surname>Temme</surname><given-names>EHM</given-names> </name><name name-style="western"><surname>van der Vossen-Wijmenga</surname><given-names>W</given-names> </name><name name-style="western"><surname>Verkaik-Kloosterman</surname><given-names>J</given-names> </name></person-group><article-title>The essential role of food composition databases for public health nutrition &#x2013; experiences from the Netherlands</article-title><source>J Food Compost Anal</source><year>2021</year><month>08</month><volume>101</volume><fpage>103967</fpage><pub-id pub-id-type="doi">10.1016/j.jfca.2021.103967</pub-id></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Westenbrink</surname><given-names>S</given-names> </name><name name-style="western"><surname>van der Vossen-Wijmenga</surname><given-names>W</given-names> </name><name name-style="western"><surname>Toxopeus</surname><given-names>I</given-names> </name><name name-style="western"><surname>Milder</surname><given-names>I</given-names> </name><name name-style="western"><surname>Ock&#x00E9;</surname><given-names>M</given-names> </name></person-group><article-title>LEDA, the branded food database in the Netherlands: data challenges and opportunities</article-title><source>J Food Compost Anal</source><year>2021</year><month>09</month><volume>102</volume><fpage>104044</fpage><pub-id pub-id-type="doi">10.1016/j.jfca.2021.104044</pub-id></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Pravst</surname><given-names>I</given-names> </name><name name-style="western"><surname>Hribar</surname><given-names>M</given-names> </name><name name-style="western"><surname>&#x017D;mitek</surname><given-names>K</given-names> </name><name name-style="western"><surname>Bla&#x017E;ica</surname><given-names>B</given-names> </name><name name-style="western"><surname>Seljak</surname><given-names>BK</given-names> </name><name name-style="western"><surname>Ku&#x0161;ar</surname><given-names>A</given-names> </name></person-group><article-title>Branded foods databases as a tool to support nutrition research and monitoring of the food supply: insights from the Slovenian composition and labeling information system</article-title><source>Front Nutr</source><year>2021</year><volume>8</volume><fpage>798576</fpage><pub-id pub-id-type="doi">10.3389/fnut.2021.798576</pub-id><pub-id pub-id-type="medline">35059426</pub-id></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cade</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Warthon-Medina</surname><given-names>M</given-names> </name><name name-style="western"><surname>Albar</surname><given-names>S</given-names> </name><etal/></person-group><article-title>DIET@NET: Best Practice Guidelines for dietary assessment in health research</article-title><source>BMC Med</source><year>2017</year><month>11</month><day>15</day><volume>15</volume><issue>1</issue><fpage>202</fpage><pub-id pub-id-type="doi">10.1186/s12916-017-0962-x</pub-id><pub-id pub-id-type="medline">29137630</pub-id></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="web"><article-title>170.000 Lebensmittelprodukte auf dem deutschen Markt</article-title><source>Lebensmittelverband Deutschland</source><year>2023</year><access-date>2025-01-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.lebensmittelverband.de/de/aktuell/20200731-tag-der-lebensmittelvielfalt">https://www.lebensmittelverband.de/de/aktuell/20200731-tag-der-lebensmittelvielfalt</ext-link></comment></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>The NutriScan process.</p><media xlink:href="humanfactors_v12i1e62776_app1.png" xlink:title="PNG File, 73 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>User rating (n=74) on participants&#x2019; preferences for NutriDiary compared to a traditional WDR (pen -and -paper method).</p><media xlink:href="humanfactors_v12i1e62776_app2.jpeg" xlink:title="JPEG File, 90 KB"/></supplementary-material></app-group></back></article>