<?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 Mhealth Uhealth</journal-id><journal-id journal-id-type="publisher-id">mhealth</journal-id><journal-id journal-id-type="index">13</journal-id><journal-title>JMIR mHealth and uHealth</journal-title><abbrev-journal-title>JMIR Mhealth Uhealth</abbrev-journal-title><issn pub-type="epub">2291-5222</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">v14i1e64787</article-id><article-id pub-id-type="doi">10.2196/64787</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Spanish Version of the mHealth App Usability Questionnaire (S-MAUQ): Translation, Adaptation, and Validation Study</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes" equal-contrib="yes"><name name-style="western"><surname>Carrillo-Le&#x00F3;n</surname><given-names>Antonio L</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Falgueras-Cano</surname><given-names>Juan</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>D&#x00ED;az-Mohedo</surname><given-names>Esther</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Languages and Computer Science, University of M&#x00E1;laga</institution><addr-line>C/ Doctor Ortiz Ramos s/n (Campus de Teatinos)</addr-line><addr-line>M&#x00E1;laga</addr-line><country>Spain</country></aff><aff id="aff2"><institution>Department of Physiotherapy, University of M&#x00E1;laga</institution><addr-line>M&#x00E1;laga</addr-line><country>Spain</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Buis</surname><given-names>Lorraine</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Daud</surname><given-names>Aziah</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Carrouel</surname><given-names>Florence</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Antonio L Carrillo-Le&#x00F3;n, PhD, Department of Languages and Computer Science, University of M&#x00E1;laga, C/ Doctor Ortiz Ramos s/n (Campus de Teatinos), M&#x00E1;laga, 29071, Spain, 34 951952390; <email>alcarrillo@uma.es</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>all authors contributed equally</p></fn></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>20</day><month>4</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e64787</elocation-id><history><date date-type="received"><day>16</day><month>08</month><year>2024</year></date><date date-type="rev-recd"><day>20</day><month>12</month><year>2025</year></date><date date-type="accepted"><day>11</day><month>02</month><year>2026</year></date></history><copyright-statement>&#x00A9; Antonio L Carrillo-Le&#x00F3;n, Juan Falgueras-Cano, Esther D&#x00ED;az-Mohedo. Originally published in JMIR mHealth and uHealth (<ext-link ext-link-type="uri" xlink:href="https://mhealth.jmir.org">https://mhealth.jmir.org</ext-link>), 20.4.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mHealth and uHealth, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://mhealth.jmir.org/">https://mhealth.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://mhealth.jmir.org/2026/1/e64787"/><abstract><sec><title>Background</title><p>In the current digital landscape, ensuring optimal usability is one of the most crucial factors determining the success of any mobile app. Questionnaire-based usability evaluations represent a highly prevalent methodology for this purpose. To date, questionnaires have been developed to assess the general system usability; however, there are hardly any questionnaires specifically designed to assess the usability of mobile health (mHealth) apps. The most widespread, the mHealth App Usability Questionnaire (MAUQ), has been developed in 4 versions according to the type of app (interactive or standalone) and the target user (patient or provider).</p></sec><sec><title>Objective</title><p>The objective of this study was to translate and validate the English version of the MAUQ (standalone, for patients) into a Spanish version (S-MAUQ).</p></sec><sec sec-type="methods"><title>Methods</title><p>The methodology used here follows that proposed by Sousa and Rojjanasrirat, which comprises 4 stages. The initial stage of the process entails a translation, harmonization, and adaptation procedure. The second and third entailed content validation (by 10 experts) and face validation (by 12 target users), respectively, which were conducted to evaluate the relevance and clarity of the questionnaire items. The item-level content validity index, scale content validity index (S-CVI), item-level face validity index, and scale face validity index (S-FVI), as well as the modified kappa statistic (&#x03BA;) were used to evaluate interrater agreement among the raters, considering the probability of agreement by chance (Pc). The fourth and final stage of the process involved the assessment of the questionnaire&#x2019;s reliability. A sample of 61 young adult participants installed an mHealth app (the Yazio app), used it, and responded to the S-MAUQ. The Cronbach &#x03B1; value for the entire questionnaire and its subscales were then calculated.</p></sec><sec sec-type="results"><title>Results</title><p>For the second stage, the S-CVI was initially 0.778. We removed items #14 and #15 from the Spanish version as they were unclear and not relevant. The S-CVI changed to 0.881. The third stage had an S-FVI of 0.927, indicating that the items are clear and straightforward for the nonexpert target user to understand. Furthermore, with each &#x03BA; value &#x003E;0.74, the validity of the instrument is supported. The fourth stage demonstrated the reliability of the S-MAUQ with a Cronbach &#x03B1; value of 0.87.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>The final version of the S-MAUQ met the validation criteria, demonstrating reliability and validity that are comparable with those of the original version. Consequently, the S-MAUQ is suitable for evaluating the usability of mHealth apps for young Spanish adults. Further research involving larger and more diverse samples is recommended.</p></sec></abstract><kwd-group><kwd>mHealth</kwd><kwd>usability questionnaires</kwd><kwd>usability evaluation</kwd><kwd>medical informatics</kwd><kwd>mobile health</kwd><kwd>app</kwd><kwd>mobile application</kwd><kwd>translation</kwd><kwd>adaptation</kwd><kwd>validation study</kwd><kwd>questionnaire-based evaluation</kwd><kwd>methodology</kwd><kwd>Spanish version</kwd><kwd>S-MAUQ</kwd><kwd>reliability</kwd><kwd>internal consistency</kwd><kwd>kappa statistic</kwd><kwd>digital health</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>mHealth is an acronym for mobile health, which is used to describe the practice of medicine and public health that is supported by mobile devices [<xref ref-type="bibr" rid="ref1">1</xref>]. Such mobile devices encompass mobile phones, tablets, and wearable devices, including smart watches. mHealth apps can collect health information for practitioners, researchers, and patients alike and can monitor patients&#x2019; vital signs in real time. They facilitate direct care using mobile telemedicine and are used in the training of and collaboration with health workers [<xref ref-type="bibr" rid="ref2">2</xref>].</p><p>The use of mHealth apps is increasing at a considerable rate [<xref ref-type="bibr" rid="ref3">3</xref>], as evidenced by the growing number of users or patients [<xref ref-type="bibr" rid="ref4">4</xref>]. Moreover, the emergence of innovative eHealth and mHealth technologies has the potential to significantly improve the cost-effectiveness of the health care system [<xref ref-type="bibr" rid="ref5">5</xref>].</p><p>Presently, these health apps are typically developed either by researchers or, in the majority of cases, by commercial companies, without collaboration between these two groups. The lack of interaction between researchers and commercial developers in the field of health-related apps has resulted in a situation where commercially available apps have not been subjected to scientific validation and apps that have been developed from research projects are not commercially available [<xref ref-type="bibr" rid="ref6">6</xref>].</p><p>It is imperative that mHealth apps are designed in a manner that ensures optimal <italic>usability</italic>. Such apps must be straightforward to use and capable of achieving their intended objectives in an efficient manner. Well-designed mHealth apps have demonstrated cost-effectiveness through the education and empowerment of patients as well as through improved treatment adherence. However, some reviews have highlighted the absence of criteria for assessing the validity of mHealth apps.</p><p>mHealth apps can be classified into two principal categories: those designed for patients and those designed for health care providers. <italic>Patient-focused</italic> apps are designed to assist with the management of health behaviors, whereas those oriented toward <italic>health care providers</italic> facilitate services such as prescriptions and education. Furthermore, mHealth apps can be classified into two additional categories: <italic>interactive</italic> apps, which facilitate communication with health care providers, and <italic>standalone</italic> apps, which include features such as reminders but lack provider interaction [<xref ref-type="bibr" rid="ref7">7</xref>].</p><p>The optimal <italic>usability</italic> of apps is characterized by several key attributes, including efficiency, satisfaction, learnability, memorability, and low error rates [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. However, the intrinsic constraints of mobile devices, notably their limited display area, can present obstacles to the attainment of these objectives [<xref ref-type="bibr" rid="ref9">9</xref>].</p><p>The People at the Center of Mobile App usability model considers the user, task, and context of use to evaluate usability. This includes the cognitive load associated with tasks such as exercising while using the app, as discussed by Harrison et al [<xref ref-type="bibr" rid="ref10">10</xref>]. To minimize errors, usability should be assessed using the following criteria: effectiveness, efficiency, satisfaction, learnability, memorability, and cognitive load [<xref ref-type="bibr" rid="ref10">10</xref>].</p><p>A few usability scales have been evaluation to ascertain their relative importance in the context of the development of general software systems and mobile apps. For example, the Mobile App Rating Scale (MARS) [<xref ref-type="bibr" rid="ref11">11</xref>], its user version (uMARS) [<xref ref-type="bibr" rid="ref12">12</xref>], System Usability Scale [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>], and Post-Study System Usability Questionnaire [<xref ref-type="bibr" rid="ref15">15</xref>]. However, these scales are not appropriate for evaluating mHealth apps, as they were not developed with mHealth apps as a specific focus.</p><p>One of the most pivotal usability scales for assessing the usability of mHealth apps is the mHealth App Usability Questionnaire (MAUQ) [<xref ref-type="bibr" rid="ref7">7</xref>]. This assesses the ease of use, interface, satisfaction, and usefulness of mHealth apps for end users.</p><p>The standalone for patient version of MAUQ has been translated, among other languages, into Malay, German, and Italian [<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref18">18</xref>]. It is noteworthy that, while this research was being developed, another related study was published (a Spanish version of MAUQ standalone, for patient [<xref ref-type="bibr" rid="ref19">19</xref>]) but adapted to breastfeeding support apps. However, it has too many differences from the original and some incorrect formulas, as will be addressed in the discussion section.</p><p>The objective of our study was to translate and validate the English version of the MAUQ (standalone, for patients) into a Spanish version (S-MAUQ) for use in future mHealth app research and development.</p><p>The importance of the translation into Spanish and its corresponding validation lies in two fundamental points: on the one hand, the large size of the Spanish-speaking community and, on the other, the cultural diversity of the type of user of these apps. Without this linguistic adaptation, these questionnaires would be out of reach for many users.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Overview of the Questionnaire</title><p>As previously stated, the MAUQ, developed and validated by Zhou and colleagues [<xref ref-type="bibr" rid="ref7">7</xref>], is designed to assess the usability of mHealth apps among patients and health care providers. There are two versions of MAUQ, one for interactive apps and one for stand-alone apps. Each also addresses two of its potential users: patient or health care professional. We will work on MAUQ for standalone apps intended for patients. Always consider that the term &#x201C;patient&#x201D; refers to a person who uses an mHealth app to manage their health either for maintenance or improvement.</p><p>The questionnaire is comprised of 3 subscales or dimensions: ease of use (items #1 to #5), interface and satisfaction (items #6 to #12), and usefulness (items #13 to #18). Participants are required to indicate their level of agreement with each item on a 7-point Likert scale, with 1 representing strong disagreement and 7 representing strong agreement. The overall usability of the app is determined by calculating the total score and the mean score of all statements. A higher overall mean score is indicative of superior app usability. Conversely, a mean score &#x003C;4 indicates suboptimal usability.</p><p>The original MAUQ (standalone, for patient version) exhibited robust internal consistency, with an overall Cronbach &#x03B1; value of 0.914. This indicates a high degree of correlation between the questionnaire items, indicating good reliability. The study was conducted in 2020 [<xref ref-type="bibr" rid="ref7">7</xref>].</p><p>The methodology used to translate and validate the original MAUQ (standalone, for patient version) into Spanish followed the approach proposed by Sousa and Rojjanasrirat [<xref ref-type="bibr" rid="ref20">20</xref>], with the objective of ensuring equivalence between the original and translated versions. The process is comprised of several steps (illustrated in <xref ref-type="fig" rid="figure1">Figure 1</xref>), which can be grouped into the following 4 stages: translation and adaptation, content validation, face validation, and internal consistency reliability.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>The flow of translation, cross-cultural adaptation, and validation process for the Spanish version of the mHealth App Usability Questionnaire (S-MAUQ).</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e64787_fig01.png"/></fig></sec><sec id="s2-2"><title>Translation and Adaptation Process</title><p>The preliminary phase of the translation process entailed the participation of two certified translators, each with a specialized understanding of both Spanish culture and linguistics. These professionals engaged in a forward translation from English to Spanish. One translator had a background in computer science, while the other had a background in health sciences. This resulted in the generation of two distinct documents designated T1 and T2.</p><p>Subsequently, the documents (T1 and T2) underwent a harmonization process. A third translator, a Spanish language teacher with more than 5 years of teaching experience, was tasked with identifying any ambiguities; discrepancies; and differences in words, sentences, grammar, and meaning. This was accomplished through a comparison of T1 and T2 with the original MAUQ. Any discrepancies and ambiguities were discussed and resolved through a process of consensus decision-making involving the third translator, the first two translators, and two members of the research team. The process culminated in the production of an initial translated version of the MAUQ document (T3).</p><p>In the third phase of the process, the translated version of the MAUQ (T3) was provided to 2 independent native Spanish speakers who had acquired English as a second language. One individual (a computer science lecturer) was a content expert in the instrument&#x2019;s construct, while the other had no prior knowledge of the instrument (an English language teacher). The 2 participants then produced independent back-translated versions of the MAUQ (T4 and T5).</p><p>Last, a committee was established comprising 3 researchers, the translators involved in the initial and concluding stages, and the original developers of the MAUQ (when necessary). The committee conducted a comparative analysis of the documents with the original MAUQ, engaging in discussions via email and web-based meetings. Any ambiguities or inconsistencies in cultural meaning and expression of words and sentences and the format of the answers were addressed and resolved through consensus among the committee members. This process resulted in the development of the prefinal Spanish questionnaire, designated as S-MAUQ&#x2019;.</p></sec><sec id="s2-3"><title>Content Validation and Face Validation</title><p>Content validation is achieved by a panel of experts who assess the relevance and clarity of questionnaire items for measuring the usability of health-related mobile apps. Face validation is accomplished by a set of nonexperts or target users who specifically assess the clarity of the items.</p><sec id="s2-3-1"><title>Participants</title><p>For the content validation, a panel of 10 experts was formed. Our panel included 3 mobile app developers, 2 senior lecturers with a PhD in computer science, 2 usability experts, and 3 PhD senior lecturers and health-related practitioners.</p><p>For the face validation, 12 nonexpert participants were involved.</p></sec><sec id="s2-3-2"><title>Recruitment</title><p>For the content validation, the 10 expert participants were carefully selected in order to adequately cover all areas of expertise involved. After being informed of the study&#x2019;s objective, all participants signed the corresponding informed consent form.</p><p>For the face validation, users were randomly selected from an openly chosen sample. The inclusion criteria were as follows: (1) native Spanish speaker, (2) older than 18 years, and (3) familiar with smartphones. The exclusion criteria were being (1) health-related practitioners, (2) mobile app developers, or (3) computer science students or professionals.</p><p>Participants were asked to complete an anonymous web form that included the informed consent, gender, date of birth, and level of education.</p></sec><sec id="s2-3-3"><title>Setting</title><p>The group of expert participants completed their evaluations remotely and sent them to us via email. The nonexpert participants completed their evaluation online via an anonymous web form.</p></sec><sec id="s2-3-4"><title>Study Procedures</title><p>In the content validation stage, each expert is required to assign a score on a scale of 1 to 5 to each item. A score of 1 indicates that the item was not relevant or clear, while a score of 5 indicates that the item was highly relevant and clear. Subsequently, scores of 1 to 3 were recategorized as 0, indicating irrelevance or unclarity, while scores of 4 and 5 were recategorized as 1, indicating relevance or clarity. The final categorization was conducted with the objective of obtaining dichotomous values. In numerous other studies, the range extends from 1 to 4. In contrast, in our study, the range was from 1 to 5. However, the current quality standards are more demanding, as a rating of 3 was considered unsatisfactory. In addition, there were 3 instances of unsatisfactory performance, as opposed to only 2 instances of acceptable performance.</p><p>On the other hand, in the face validation, which was less demanding with the nonexpert evaluators, the scores ranged from 1 (indicating that the item was not understandable) to 4 (indicating that the item was very understandable). Scores of 1 and 2 were recategorized as 0 (not understandable), and scores of 3 and 4 were recategorized as 1 (understandable). This was less demanding because the chosen scores were taken directly without considering the middle 3 negative values as we did with the experts.</p><p>The calculations for the 2 types of evaluation were as described in the following statements.</p><p>If we have <italic>N</italic> as the number of raters or evaluators; <italic>A<sub>C</sub></italic> as the number of expert raters who concur that the items are relevant, unambiguous, and intelligible; and <italic>A</italic><sub><italic>F</italic></sub> as the number of nonexpert raters who concur that the items are clear and comprehensible, the item-level content validity index (I-CVI) and the item-level face validity index (I-FVI) were calculated by dividing the propoortion of raters who agreed that an item was clear and relevant to the domain by the total number of raters.</p><p>In conclusion, it can be proposed that:</p><p><inline-formula><mml:math id="ieqn1"><mml:mstyle><mml:mrow><mml:mstyle displaystyle="false"><mml:mrow><mml:mi>I</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mi>C</mml:mi><mml:mi>V</mml:mi><mml:mi>I</mml:mi></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:msub><mml:mi>A</mml:mi><mml:mi>C</mml:mi></mml:msub><mml:mi>N</mml:mi></mml:mfrac></mml:mstyle></mml:mrow></mml:mstyle></mml:math></inline-formula> and <inline-formula><mml:math id="ieqn2"><mml:mstyle><mml:mrow><mml:mstyle displaystyle="false"><mml:mrow><mml:mi>I</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mi>F</mml:mi><mml:mi>V</mml:mi><mml:mi>I</mml:mi></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:msub><mml:mi>A</mml:mi><mml:mi>F</mml:mi></mml:msub><mml:mi>N</mml:mi></mml:mfrac></mml:mstyle></mml:mrow></mml:mstyle></mml:math></inline-formula></p><p>Items with an I-CVI or I-FVI of at least 0.79 were relevant, unambiguous, and understandable to the target users, indicating their potential inclusion in the questionnaire [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>].</p><p>The scale content validity index (S-CVI) and scale face validity index (S-FVI) can be calculated as the means of the corresponding I-CVI and I-FVI. This is accomplished by dividing the sum of each item by the total number of items [<xref ref-type="bibr" rid="ref23">23</xref>].</p><p>Moreover, it is essential to determine the level of agreement among the 10 experts. This can be accomplished by calculating the modified kappa statistic [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>], which can be expressed as follows:</p><p><inline-formula><mml:math id="ieqn3"><mml:mstyle><mml:mrow><mml:mstyle displaystyle="false"><mml:msub><mml:mi>&#x03BA;</mml:mi><mml:mrow><mml:mi>C</mml:mi><mml:mi>V</mml:mi><mml:mi>I</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mtext>I-CVI</mml:mtext><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>P</mml:mi><mml:mi>c</mml:mi></mml:msub></mml:mrow><mml:mrow><mml:mn>1</mml:mn><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>P</mml:mi><mml:mi>c</mml:mi></mml:msub></mml:mrow></mml:mfrac></mml:mstyle></mml:mrow></mml:mstyle></mml:math></inline-formula> and <inline-formula><mml:math id="ieqn4"><mml:mstyle><mml:mrow><mml:mstyle displaystyle="false"><mml:msub><mml:mi>&#x03BA;</mml:mi><mml:mrow><mml:mi>F</mml:mi><mml:mi>V</mml:mi><mml:mi>I</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mtext>I-FVI</mml:mtext><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>P</mml:mi><mml:mi>c</mml:mi></mml:msub></mml:mrow><mml:mrow><mml:mn>1</mml:mn><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>P</mml:mi><mml:mi>c</mml:mi></mml:msub></mml:mrow></mml:mfrac></mml:mstyle></mml:mrow></mml:mstyle></mml:math></inline-formula></p><p>In this formula, <italic>P<sub>C</sub></italic> represents the probability of chance occurrence. The initial determination of the probability of agreement by chance for each item was determined using the following formula (the formula for a binomial random variable) [<xref ref-type="bibr" rid="ref21">21</xref>]:</p><disp-formula id="E1"><mml:math id="eqn1"><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mstyle displaystyle="true" scriptlevel="0"><mml:msub><mml:mi>P</mml:mi><mml:mi>c</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mrow><mml:mo maxsize="2.047em" minsize="2.047em">(</mml:mo></mml:mrow><mml:mfrac linethickness="0pt"><mml:mi>N</mml:mi><mml:mi>A</mml:mi></mml:mfrac><mml:mrow><mml:mo maxsize="2.047em" minsize="2.047em">)</mml:mo></mml:mrow></mml:mrow><mml:mo>&#x22C5;</mml:mo><mml:msup><mml:mn>0.5</mml:mn><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:msup><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mi>N</mml:mi><mml:mo>!</mml:mo></mml:mrow><mml:mrow><mml:mi>A</mml:mi><mml:mo>!</mml:mo><mml:mtext>&#x00A0;</mml:mtext><mml:mo stretchy="false">(</mml:mo><mml:mi>N</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mi>A</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>!</mml:mo></mml:mrow></mml:mfrac><mml:mo>&#x22C5;</mml:mo><mml:msup><mml:mn>0.5</mml:mn><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:msup></mml:mstyle></mml:mrow></mml:mstyle></mml:math></disp-formula><p>This equation has its origins in the field of probability theory, specifically in the binomial distribution. The probability of obtaining precisely <italic>A</italic> successes in <italic>N</italic> independent Bernoulli trials (with the same rate <italic>p</italic>, in this case <italic>1/2</italic>) is given by the probability mass function (or discrete probability density function):</p><p><inline-formula><mml:math id="ieqn5"><mml:mstyle><mml:mrow><mml:mstyle displaystyle="false"><mml:msub><mml:mi>P</mml:mi><mml:mi>c</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mrow><mml:mo maxsize="1.2em" minsize="1.2em">(</mml:mo></mml:mrow><mml:mfrac linethickness="0pt"><mml:mi>N</mml:mi><mml:mi>A</mml:mi></mml:mfrac><mml:mrow><mml:mo maxsize="1.2em" minsize="1.2em">)</mml:mo></mml:mrow></mml:mrow><mml:mtext>&#x00A0;</mml:mtext><mml:msup><mml:mi>p</mml:mi><mml:mrow><mml:mi>k</mml:mi></mml:mrow></mml:msup><mml:mo stretchy="false">(</mml:mo><mml:mn>1</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mi>p</mml:mi><mml:msup><mml:mo stretchy="false">)</mml:mo><mml:mrow><mml:mi>N</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mi>A</mml:mi></mml:mrow></mml:msup></mml:mstyle></mml:mrow></mml:mstyle></mml:math></inline-formula> and for p=1/2 &#x2192; <inline-formula><mml:math id="ieqn6"><mml:mstyle><mml:mrow><mml:mstyle displaystyle="false"><mml:msub><mml:mi>P</mml:mi><mml:mi>c</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mrow><mml:mo maxsize="1.2em" minsize="1.2em">(</mml:mo></mml:mrow><mml:mfrac linethickness="0pt"><mml:mi>N</mml:mi><mml:mi>A</mml:mi></mml:mfrac><mml:mrow><mml:mo maxsize="1.2em" minsize="1.2em">)</mml:mo></mml:mrow></mml:mrow><mml:mtext>&#x00A0;</mml:mtext><mml:msup><mml:mn>0.5</mml:mn><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:msup></mml:mstyle></mml:mrow></mml:mstyle></mml:math></inline-formula></p><p>Graphically, the interpretation criteria for the modified kappa statistic, as outlined by Wynd et al [<xref ref-type="bibr" rid="ref26">26</xref>] and Cicchetti and Sparrow [<xref ref-type="bibr" rid="ref27">27</xref>], is shown in <xref ref-type="fig" rid="figure2">Figure 2</xref>.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Interpretation criteria for the modified kappa statistic.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="mhealth_v14i1e64787_fig02.png"/></fig></sec></sec><sec id="s2-4"><title>Reliability (Internal Consistency) Validation</title><sec id="s2-4-1"><title>Participants</title><p>For the internal consistency validation, the participants were selected from among students enrolled in the School of Engineering at the University of Malaga and the Campus of International Excellence (Andaluc&#x00ED;a Tech). The required sample size was calculated as 38 participants for the purposes of reliability testing, with an expected Cronbach &#x03B1; of 0.80 and an expected precision of 0.1 at 95% CI [<xref ref-type="bibr" rid="ref28">28</xref>]. Given the projected rate of nonparticipation of 20%, the final sample size was determined to be 48.</p></sec><sec id="s2-4-2"><title>Recruitment</title><p>Participants were recruited through direct invitations from the involved professors during class time. Those who agreed to take part in the study were required to complete a web-based informed consent form. Inclusion criteria were an absence of any known medical illness and ownership of a smartphone.</p></sec><sec id="s2-4-3"><title>Setting</title><p>Participants performed the tasks on their smartphones and in their own classrooms and used a Google Form to submit their answers to the S-MAUQ.</p></sec><sec id="s2-4-4"><title>Study Procedures</title><p>Participants were instructed to install the Yazio app on their mobile phones. Yazio, a standalone mHealth app for patients, was selected for the usability study due to its popularity. It is one of the most widely used nutrition apps in the world, helping people lead healthier lives globally. Its availability on both Android and iPhone devices [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>] combined with its similarity to MyFitnessPal&#x2014;an app frequently used in previous studies but that requires additional resources to be used&#x2014;made it a suitable choice. A concise overview of the Yazio app, along with the essential steps for preliminary configuration, was displayed on the classroom projector. This procedure should be carried out exclusively at the point of the initial execution of the app following its installation.</p><p>Subsequently, participants were required to undertake the tasks detailed in <xref ref-type="other" rid="box1">Textbox 1</xref>.</p><boxed-text id="box1"><title> Sheet of tasks to be performed using the Yazio app.</title><list list-type="order"><list-item><p>Create initial profile when running the app for the first time (take a screenshot of the screen that appears at the end of the process, after discarding the tutorial)</p></list-item><list-item><p>Use the functions available in the Daily and/or Profile menu to add records or data for today:</p><list list-type="alpha-lower"><list-item><p>Add the following foods consumed during breakfast</p><list list-type="bullet"><list-item><p>1 black coffee</p></list-item><list-item><p>2 slices of bread (bimbo) without crust</p></list-item><list-item><p>Natural orange juice, 200 mL</p></list-item><list-item><p>Olive oil, 1 tablespoon</p></list-item><list-item><p>Product with barcode 8410095040362 (or scan it from the product code photo)</p></list-item></list></list-item><list-item><p>Modify (in the profile) daily water amount goal: 2.5 liters</p></list-item><list-item><p>Add water consumed: 1.75 liters</p></list-item><list-item><p>Add activities (exercise completed) by pressing &#x201C;More&#x201D;</p><list list-type="bullet"><list-item><p>&#x201C;walk, general&#x201D; 30 minutes</p></list-item><list-item><p>&#x201C;fast walk (6 km/h)&#x201D; 10 minutes</p></list-item></list></list-item><list-item><p>Add 2 notes or indications about how your day is going</p><list list-type="bullet"><list-item><p>&#x201C;I slept well&#x201D;</p></list-item><list-item><p>&#x201C;bored&#x201D;</p></list-item></list></list-item><list-item><p>(Finally, take the necessary screenshots, 2 or 3, to collect the data entered)</p></list-item></list></list-item><list-item><p>Identify and note (via screenshot):</p><list list-type="alpha-lower"><list-item><p>The number of calories consumed during the day (due to ingested foods and drinks)</p></list-item><list-item><p>Calories burned (from exercising, etc.)</p></list-item><list-item><p>Calories we have left to consume to reach the day&#x2019;s goal</p></list-item></list></list-item><list-item><p>Explore and find a recipe that meets each of the following conditions:</p><list list-type="alpha-lower"><list-item><p>1 vegan breakfast (between 150 and 200 kcal) and mark it as a favorite</p></list-item><list-item><p>1 vegan lunch (between 350 and 400 kcal) and mark it as a favorite</p></list-item><list-item><p>See the recipes you have marked as favorites (and take a screenshot of them)</p></list-item></list></list-item></list></boxed-text><p>First, it is recommended that an initial profile be created and the desired weight goals be determined. Second, to add records or data pertaining to the current day, the functions available from the Daily and/or Profile menus need to be used. Third, it is requested that the number of calories consumed throughout the day be identified and recorded. This should include the calories derived from food and drink, the calories expended through exercise, and the remaining calories to be consumed to reach the daily goal. Fourth, it is required to conduct a comprehensive investigation and identify a recipe that aligns with the specific criteria outlined in step 4 in <xref ref-type="other" rid="box1">Textbox 1</xref>.</p><p>Following the completion of the tasks, the participants were invited to respond to the S-MAUQ in person using a Google Form.</p><p>The internal consistency of the S-MAUQ was evaluated by calculating the Cronbach &#x03B1; value for the entire questionnaire and its 3 subscales. A higher &#x03B1; value indicates greater internal reliability, and a value of &#x2265;0.70 is generally considered acceptable as an indication of good internal reliability [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. All statistical analyses were conducted using SPSS (IBM Corp), and the results were verified using Excel (Microsoft Corp).</p><p><xref ref-type="fig" rid="figure1">Figure 1</xref> provides an overview of the process of translation and cross-cultural adaptation as well as the subsequent validation stage for S-MAUQ&#x2019;.</p></sec></sec><sec id="s2-5"><title>Ethical Considerations</title><p>No financial compensation was provided to participants at any stage of the study. Participation was voluntary and anonymous, except for members of the expert panel responsible for content validation, who were intentionally selected for their expertise. All participants (including the expert panel) were provided and signed an informed consent online, which included the possibility of opting out. The study adhered to the Declaration of Helsinki and was approved by the Bioethics Committee of the Medical University of M&#x00E1;laga (17&#x2010;2022-H).</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Content Validation</title><p>Please refer to <xref ref-type="table" rid="table1">Table 1</xref>, which presents the calculated values (using Excel) of the I-CVI for relevancy and clarity, the (Pc), and the modified kappa agreement (&#x03BA;) by the 10 experts for each item of the S-MAUQ. The S-CVI was calculated to be 0.778. However, as can be seen, there were 2 items (#3 and #6) with &#x03BA;&#x003C;0.4 (interpreted as poor agreement) and 2 others (#15 and #18) with 0.4&#x003C;&#x03BA;&#x003C;0.6 (interpreted as fair). Considering these findings, we sought to further refine the instrument in accordance with the recommendations of the expert panel.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Content validity index of item relevancy and modified kappa agreement by 10 experts in round 1.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Items</td><td align="left" valign="bottom">Rating of 4 or 5, n</td><td align="left" valign="bottom">Rating of 1 to 3, n</td><td align="left" valign="bottom">Item-level content validity index<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td><td align="left" valign="bottom">Probability of chance occurrence<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup></td><td align="left" valign="bottom">Modified kappa<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup><sup>,<xref ref-type="table-fn" rid="table1fn4">d</xref></sup></td><td align="left" valign="bottom">Interpretation</td></tr></thead><tbody><tr><td align="left" valign="top">1</td><td align="left" valign="top">10</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.001</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">2</td><td align="left" valign="top">9</td><td align="left" valign="top">1</td><td align="left" valign="top">0.900</td><td align="left" valign="top">0.010</td><td align="left" valign="top">0.899</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">3</td><td align="left" valign="top">5</td><td align="left" valign="top">5</td><td align="left" valign="top">0.500</td><td align="left" valign="top">0.246</td><td align="left" valign="top">0.337</td><td align="left" valign="top">Poor</td></tr><tr><td align="left" valign="top">4</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">9</td><td align="left" valign="top">1</td><td align="left" valign="top">0.900</td><td align="left" valign="top">0.010</td><td align="left" valign="top">0.899</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">6</td><td align="left" valign="top">5</td><td align="left" valign="top">5</td><td align="left" valign="top">0.500</td><td align="left" valign="top">0.246</td><td align="left" valign="top">0.337</td><td align="left" valign="top">Poor</td></tr><tr><td align="left" valign="top">7</td><td align="left" valign="top">10</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.001</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">8</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">9</td><td align="left" valign="top">7</td><td align="left" valign="top">3</td><td align="left" valign="top">0.700</td><td align="left" valign="top">0.117</td><td align="left" valign="top">0.660</td><td align="left" valign="top">Good</td></tr><tr><td align="left" valign="top">10</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">11</td><td align="left" valign="top">9</td><td align="left" valign="top">1</td><td align="left" valign="top">0.900</td><td align="left" valign="top">0.010</td><td align="left" valign="top">0.899</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">12</td><td align="left" valign="top">9</td><td align="left" valign="top">1</td><td align="left" valign="top">0.900</td><td align="left" valign="top">0.010</td><td align="left" valign="top">0.899</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">13</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">14</td><td align="left" valign="top">7</td><td align="left" valign="top">3</td><td align="left" valign="top">0.700</td><td align="left" valign="top">0.117</td><td align="left" valign="top">0.660</td><td align="left" valign="top">Good</td></tr><tr><td align="left" valign="top">15</td><td align="left" valign="top">6</td><td align="left" valign="top">4</td><td align="left" valign="top">0.600</td><td align="left" valign="top">0.205</td><td align="left" valign="top">0.497</td><td align="left" valign="top">Fair</td></tr><tr><td align="left" valign="top">16</td><td align="left" valign="top">9</td><td align="left" valign="top">1</td><td align="left" valign="top">0.900</td><td align="left" valign="top">0.010</td><td align="left" valign="top">0.899</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">17</td><td align="left" valign="top">7</td><td align="left" valign="top">3</td><td align="left" valign="top">0.700</td><td align="left" valign="top">0.117</td><td align="left" valign="top">0.660</td><td align="left" valign="top">Good</td></tr><tr><td align="left" valign="top">18</td><td align="left" valign="top">6</td><td align="left" valign="top">4</td><td align="left" valign="top">0.600</td><td align="left" valign="top">0.205</td><td align="left" valign="top">0.497</td><td align="left" valign="top">Fair</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Scale content validity index=0.778.</p></fn><fn id="table1fn2"><p><sup>b</sup>Computed using the formula Pc = [ N! / (A! * (N&#x2013;A)!) ] * 0.5N, where Pc is the probability of chance occurrence, n is the number of experts, and A is the number of experts who agree the items are relevant/clear.</p></fn><fn id="table1fn3"><p><sup>c</sup>Computed using the formula &#x03BA;=(item-level content validity index &#x2013; Pc) / (1 &#x2013; Pc), where Pc is the probability of chance occurrence. </p></fn><fn id="table1fn4"><p><sup>d</sup>Kappa was interpreted according to the following criteria: excellent, &#x03BA;&#x003E;0.74; good, 0.6&#x2264;&#x03BA;&#x2264;0.74; fair, 0.40&#x2264;&#x03BA;&#x2264;0.59; poor, &#x03BA;&#x003C;0.40.</p></fn></table-wrap-foot></table-wrap><p>The results of the second round are presented in <xref ref-type="table" rid="table2">Table 2</xref>, which indicates an S-CVI of 0.850. However, 2 items (#14 and #15) demonstrated a markedly low level of relevance and clarity (I-CVI), accompanied by a similarly low &#x03BA; (0.4&#x2264;&#x03BA;&#x2264;0.6, interpreted as &#x201C;fair&#x201D;). Following a thorough review with our panel of experts, it was determined that both items should be removed from the preliminary Spanish questionnaire (S-MAUQ). In conclusion, the S-CVI was calculated to be 0.881 (without considering the 2 items that were subsequently eliminated).</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Content validity index of item relevancy and modified kappa agreement by 10 experts in round 2.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Items</td><td align="left" valign="bottom">Rating of 4 or 5, n</td><td align="left" valign="bottom">Rating of 1 to 3, n</td><td align="left" valign="bottom">Item-level content validity index<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup></td><td align="left" valign="bottom">Probability of chance occurrence<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup></td><td align="left" valign="bottom">Modified kappa<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup><sup>,</sup><sup><xref ref-type="table-fn" rid="table2fn4">d</xref></sup></td><td align="left" valign="bottom">Interpretation</td></tr></thead><tbody><tr><td align="left" valign="top">1</td><td align="left" valign="top">10</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.001</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">2</td><td align="left" valign="top">9</td><td align="left" valign="top">1</td><td align="left" valign="top">0.900</td><td align="left" valign="top">0.010</td><td align="left" valign="top">0.899</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">3</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">4</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">10</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.001</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">6</td><td align="left" valign="top">10</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.001</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">7</td><td align="left" valign="top">10</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.001</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">8</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">9</td><td align="left" valign="top">7</td><td align="left" valign="top">3</td><td align="left" valign="top">0.700</td><td align="left" valign="top">0.117</td><td align="left" valign="top">0.660</td><td align="left" valign="top">Good</td></tr><tr><td align="left" valign="top">10</td><td align="left" valign="top">9</td><td align="left" valign="top">1</td><td align="left" valign="top">0.900</td><td align="left" valign="top">0.010</td><td align="left" valign="top">0.899</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">11</td><td align="left" valign="top">10</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.001</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">12</td><td align="left" valign="top">10</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.001</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">13</td><td align="left" valign="top">9</td><td align="left" valign="top">1</td><td align="left" valign="top">0.900</td><td align="left" valign="top">0.010</td><td align="left" valign="top">0.899</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">14</td><td align="left" valign="top">6</td><td align="left" valign="top">4</td><td align="left" valign="top">0.600</td><td align="left" valign="top">0.205</td><td align="left" valign="top">0.497</td><td align="left" valign="top">Fair</td></tr><tr><td align="left" valign="top">15</td><td align="left" valign="top">6</td><td align="left" valign="top">4</td><td align="left" valign="top">0.600</td><td align="left" valign="top">0.205</td><td align="left" valign="top">0.497</td><td align="left" valign="top">Fair</td></tr><tr><td align="left" valign="top">16</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">17</td><td align="left" valign="top">8</td><td align="left" valign="top">2</td><td align="left" valign="top">0.800</td><td align="left" valign="top">0.044</td><td align="left" valign="top">0.791</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">18</td><td align="left" valign="top">7</td><td align="left" valign="top">3</td><td align="left" valign="top">0.700</td><td align="left" valign="top">0.117</td><td align="left" valign="top">0.660</td><td align="left" valign="top">Good</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>Scale content validity index=0.850.</p></fn><fn id="table2fn2"><p><sup>b</sup>Computed using the formula Pc = [ N! / (A! * (N&#x2013;A)!) ] * 0.5N, where Pc is the probability of chance occurrence, n is the number of experts, and A is the number of experts who agree the items are relevant/clear.</p></fn><fn id="table2fn3"><p><sup>c</sup>Computed using the formula &#x03BA;=(item-level content validity index &#x2013; Pc) / (1 &#x2013; Pc), where Pc is the probability of chance occurrence. </p></fn><fn id="table2fn4"><p><sup>d</sup>Kappa was interpreted according to the following criteria: excellent, &#x03BA;&#x003E;0.74; good, 0.6&#x2264;&#x03BA;&#x2264;0.74; fair, 0.40&#x2264;&#x03BA;&#x2264;0.59; poor, &#x03BA;&#x003C;0.40.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2"><title>Face Validation</title><p>Please refer to <xref ref-type="table" rid="table3">Table 3</xref> for the calculated values of the I-FVI, the Pc, and the modified kappa agreement (&#x03BA;) for each item. These were determined by the 12 target users. The S-FVI was calculated to be 0.927. A score &#x003E;0.79 indicates that the items in the questionnaire are sufficiently clear and understandable for the nonexpert target user [<xref ref-type="bibr" rid="ref27">27</xref>]. Furthermore, the modified kappa agreement for each item in S-MAUQ demonstrated excellent concordance (&#x03BA;&#x003E;0.74).</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Face validity index of item understandability and modified kappa agreement by 12 target users.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Items</td><td align="left" valign="bottom">Rating of 3 or 4, n</td><td align="left" valign="bottom">Rating of 1 or 2, n</td><td align="left" valign="bottom">Item-level face validity index<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="left" valign="bottom">Probability of chance occurrence<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup></td><td align="left" valign="bottom">Modified kappa<sup><xref ref-type="table-fn" rid="table3fn3">c</xref></sup></td><td align="left" valign="bottom">Interpretation</td></tr></thead><tbody><tr><td align="left" valign="top">1</td><td align="left" valign="top">12</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.000</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">2</td><td align="left" valign="top">12</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.000</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">3</td><td align="left" valign="top">9</td><td align="left" valign="top">3</td><td align="left" valign="top">0.750</td><td align="left" valign="top">0.054</td><td align="left" valign="top">0.740</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">4</td><td align="left" valign="top">11</td><td align="left" valign="top">1</td><td align="left" valign="top">0.917</td><td align="left" valign="top">0.003</td><td align="left" valign="top">0.916</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">11</td><td align="left" valign="top">1</td><td align="left" valign="top">0.917</td><td align="left" valign="top">0.003</td><td align="left" valign="top">0.916</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">6</td><td align="left" valign="top">11</td><td align="left" valign="top">1</td><td align="left" valign="top">0.917</td><td align="left" valign="top">0.003</td><td align="left" valign="top">0.916</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">7</td><td align="left" valign="top">11</td><td align="left" valign="top">1</td><td align="left" valign="top">0.917</td><td align="left" valign="top">0.003</td><td align="left" valign="top">0.916</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">8</td><td align="left" valign="top">11</td><td align="left" valign="top">1</td><td align="left" valign="top">0.917</td><td align="left" valign="top">0.003</td><td align="left" valign="top">0.916</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">9</td><td align="left" valign="top">10</td><td align="left" valign="top">2</td><td align="left" valign="top">0.833</td><td align="left" valign="top">0.016</td><td align="left" valign="top">0.831</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">10</td><td align="left" valign="top">10</td><td align="left" valign="top">2</td><td align="left" valign="top">0.833</td><td align="left" valign="top">0.016</td><td align="left" valign="top">0.831</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">11</td><td align="left" valign="top">12</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.000</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">12</td><td align="left" valign="top">12</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.000</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">13</td><td align="left" valign="top">12</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.000</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">14<sup><xref ref-type="table-fn" rid="table3fn5">e</xref></sup></td><td align="left" valign="top">&#x2014;<sup><xref ref-type="table-fn" rid="table3fn6">f</xref></sup></td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">15<sup><xref ref-type="table-fn" rid="table3fn5">e</xref></sup></td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">16</td><td align="left" valign="top">12</td><td align="left" valign="top">0</td><td align="left" valign="top">1.000</td><td align="left" valign="top">0.000</td><td align="left" valign="top">1.000</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">17</td><td align="left" valign="top">11</td><td align="left" valign="top">1</td><td align="left" valign="top">0.917</td><td align="left" valign="top">0.003</td><td align="left" valign="top">0.916</td><td align="left" valign="top">Excellent</td></tr><tr><td align="left" valign="top">18</td><td align="left" valign="top">11</td><td align="left" valign="top">1</td><td align="left" valign="top">0.917</td><td align="left" valign="top">0.003</td><td align="left" valign="top">0.916</td><td align="left" valign="top">Excellent</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>Scale face validity index=0.927.</p></fn><fn id="table3fn2"><p><sup>b</sup>Computed using the formula Pc = [ N! / (A! * (N&#x2013;A)!) ] * 0.5N, where Pc is the probability of chance occurrence, n is the number of users, and A is the number of users who agree the items are understandable.</p></fn><fn id="table3fn3"><p><sup>c</sup>Computed using the formula: =(item-level face validity index &#x2013; Pc) / (1 &#x2013; Pc), where Pc is the probability of chance occurrence.</p></fn><fn id="table3fn4"><p><sup>d</sup>Kappa was interpreted according to the following criteria: excellent, &#x03BA;&#x003E;0.74; good, 0.6&#x2264;&#x03BA;&#x2264;0.74; fair, 0.40&#x2264;&#x03BA;&#x2264;0.59; poor, &#x03BA;&#x003C;0.40.</p></fn><fn id="table3fn5"><p><sup>e</sup>Removed from the questionnaire.</p></fn><fn id="table3fn6"><p><sup>f</sup>Not applicable.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-3"><title>Reliability (Internal Consistency) Validation</title><p>A total of 61 participants completed the web-based consent form and the S-MAUQ questionnaire for the purposes of the reliability study (the calculated sample size was 48). The participants were between the ages of 18 years and 22 years, and all were students (41 men, 20 women). The mean usability score (normalized to 1) for the Yazio app, as determined by the S-MAUQ, was 0.855 (SD 0.088). This indicates a high level of usability.</p><p>The Cronbach &#x03B1; value for the entire S-MAUQ was 0.87, and the values for the 3 subscales were 0.74 for the ease of use dimension (Q1-Q5), 0.74 for the interface and satisfaction dimension (Q6-Q12), and 0.64 for the usefulness dimension (Q13-Q16). The new numbering scheme was used for Q13-Q16, omitting the 2 deleted items.</p><p>Furthermore, the Cronbach &#x03B1; value for the complete questionnaire remained highly consistent when an item was deleted (see <xref ref-type="table" rid="table4">Table 4</xref>), indicating that the S-MAUQ exhibited good internal reliability.</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>The internal consistency of the item&#x2019;s total statistics.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Items</td><td align="left" valign="bottom">Scale mean if item deleted<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup></td><td align="left" valign="bottom">Scale variance if item deleted</td><td align="left" valign="bottom">Corrected item total correlation</td><td align="left" valign="bottom">Cronbach &#x03B1; if item deleted<sup><xref ref-type="table-fn" rid="table4fn2">b</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">1</td><td align="left" valign="top">89.46</td><td align="left" valign="top">87.086</td><td align="left" valign="top">0.532</td><td align="left" valign="top">0.854</td></tr><tr><td align="left" valign="top">2</td><td align="left" valign="top">89.07</td><td align="left" valign="top">85.129</td><td align="left" valign="top">0.635</td><td align="left" valign="top">0.850</td></tr><tr><td align="left" valign="top">3</td><td align="left" valign="top">89.10</td><td align="left" valign="top">85.190</td><td align="left" valign="top">0.570</td><td align="left" valign="top">0.852</td></tr><tr><td align="left" valign="top">4</td><td align="left" valign="top">89.07</td><td align="left" valign="top">87.562</td><td align="left" valign="top">0.470</td><td align="left" valign="top">0.857</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">89.15</td><td align="left" valign="top">84.061</td><td align="left" valign="top">0.462</td><td align="left" valign="top">0.859</td></tr><tr><td align="left" valign="top">6</td><td align="left" valign="top">88.90</td><td align="left" valign="top">89.323</td><td align="left" valign="top">0.345</td><td align="left" valign="top">0.863</td></tr><tr><td align="left" valign="top">7</td><td align="left" valign="top">89.49</td><td align="left" valign="top">87.754</td><td align="left" valign="top">0.439</td><td align="left" valign="top">0.858</td></tr><tr><td align="left" valign="top">8</td><td align="left" valign="top">88.97</td><td align="left" valign="top">89.432</td><td align="left" valign="top">0.403</td><td align="left" valign="top">0.860</td></tr><tr><td align="left" valign="top">9</td><td align="left" valign="top">89.13</td><td align="left" valign="top">87.949</td><td align="left" valign="top">0.436</td><td align="left" valign="top">0.858</td></tr><tr><td align="left" valign="top">10</td><td align="left" valign="top">89.28</td><td align="left" valign="top">85.404</td><td align="left" valign="top">0.593</td><td align="left" valign="top">0.851</td></tr><tr><td align="left" valign="top">11</td><td align="left" valign="top">89.74</td><td align="left" valign="top">79.797</td><td align="left" valign="top">0.599</td><td align="left" valign="top">0.851</td></tr><tr><td align="left" valign="top">12</td><td align="left" valign="top">89.13</td><td align="left" valign="top">85.949</td><td align="left" valign="top">0.702</td><td align="left" valign="top">0.849</td></tr><tr><td align="left" valign="top">13</td><td align="left" valign="top">89.20</td><td align="left" valign="top">88.294</td><td align="left" valign="top">0.442</td><td align="left" valign="top">0.858</td></tr><tr><td align="left" valign="top">14<sup><xref ref-type="table-fn" rid="table4fn3">c</xref></sup></td><td align="left" valign="top">&#x2014;<sup><xref ref-type="table-fn" rid="table4fn4">d</xref></sup></td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">15<sup><xref ref-type="table-fn" rid="table4fn3">c</xref></sup></td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">16</td><td align="left" valign="top">89.20</td><td align="left" valign="top">87.961</td><td align="left" valign="top">0.451</td><td align="left" valign="top">0.858</td></tr><tr><td align="left" valign="top">17</td><td align="left" valign="top">90.00</td><td align="left" valign="top">85.033</td><td align="left" valign="top">0.429</td><td align="left" valign="top">0.860</td></tr><tr><td align="left" valign="top">18</td><td align="left" valign="top">89.33</td><td align="left" valign="top">85.324</td><td align="left" valign="top">0.525</td><td align="left" valign="top">0.854</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>Overall scale mean=95.21.</p></fn><fn id="table4fn2"><p><sup>b</sup>Overall scale Cronbach &#x03B1;=0.87 (high internal consistency); ease of use subscale (Q1..Q5) Cronbach &#x03B1;=0.74; interface and satisfaction subscale (Q6..Q12) Cronbach &#x03B1;=0.74; usefulness subscale (Q13, Q16..Q18) Cronbach &#x03B1;=0.64.</p></fn><fn id="table4fn3"><p><sup>c</sup>Removed from the questionnaire.</p></fn><fn id="table4fn4"><p><sup>d</sup>Not appliclable.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>Ensuring optimal usability of Spanish mobile apps is one of the most crucial factors for their use. Questionnaires are a common method for evaluating usability. This study outlined the process of translating, adapting, and validating the English version of the standalone MAUQ questionnaire for the patient into Spanish.</p><p>To this end, we followed the 4-step process proposed by Sousa and Rojjanasrirat [<xref ref-type="bibr" rid="ref20">20</xref>], as it was outlined in the Methods section.</p><p>During the translation and adaptation phase, several meetings were held to ensure conceptual and linguistic equivalence for key terms such as interface, consistency, coherence, social setting, and health and well-being services. Final wording was established by consensus, often in consultation with the original questionnaire&#x2019;s authors.</p><p>In the content validation phase, the expert panel initially did not reach full agreement on several items. A second round of review narrowed the discrepancies but left 2 items (#14 and #15) unresolved. Both items were judged to be conceptually ambiguous and difficult to interpret, even for experts. Following a series of email consultations with the original authors on the meaning of and convenience of these items and their overlap with others, we confirmed the experts&#x2019; results and their suggestions that these items could be removed from the final Spanish version.</p><p>During the face validation phase, the calculated FVI and &#x03BA; coefficient yielded an S-FVI that substantially exceeded the recommended threshold, thereby ensuring the quality of the translation. The results of the study indicated that the items on the questionnaire were comprehensible and suitable for the target population.</p><p>Finally, the reliability analysis demonstrated strong internal consistency, with an overall Cronbach &#x03B1; of 0.87. The Spanish version maintained the original 3-dimensional structure of the English questionnaire, permitting direct cross-language comparison. Only the &#x201C;usefulness&#x201D; dimension was slightly affected, with an acceptable Cronbach &#x03B1; of 0.64 for exploratory studies. Overall, the S-MAUQ exhibited sound psychometric properties, indicating that it is a reliable and valid tool for assessing the usability of mobile health apps among Spanish-speaking patients. The final iteration of the S-MAUQ is presented in <xref ref-type="table" rid="table5">Table 5</xref> for reference.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>The final Spanish version of the mHealth App Usability Questionnaire (S-MAUQ).</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Item number</td><td align="left" valign="bottom">Question</td></tr></thead><tbody><tr><td align="left" valign="top">1</td><td align="left" valign="top">La aplicaci&#x00F3;n era f&#x00E1;cil de usar.</td></tr><tr><td align="left" valign="top">2</td><td align="left" valign="top">Me result&#x00F3; f&#x00E1;cil aprender a utilizar la aplicaci&#x00F3;n.</td></tr><tr><td align="left" valign="top">3</td><td align="left" valign="top">Al pasar de una pantalla a otra, la navegaci&#x00F3;n era consistente, similar, previsible.</td></tr><tr><td align="left" valign="top">4</td><td align="left" valign="top">La aplicaci&#x00F3;n me permiti&#x00F3; usar todas las funciones que necesit&#x00E9; (tales como visualizar e introducir informaci&#x00F3;n, responder a recordatorios, etc).</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">Cuando comet&#x00ED; un error usando la aplicaci&#x00F3;n, fue f&#x00E1;cil y r&#x00E1;pido deshacerlo y volver a intentarlo.</td></tr><tr><td align="left" valign="top">6</td><td align="left" valign="top">Me gusta el dise&#x00F1;o y aspecto de la aplicaci&#x00F3;n.</td></tr><tr><td align="left" valign="top">7</td><td align="left" valign="top">La presentaci&#x00F3;n de la informaci&#x00F3;n en la aplicaci&#x00F3;n estaba bien organizada, y me permiti&#x00F3; encontrar lo que buscaba.</td></tr><tr><td align="left" valign="top">8</td><td align="left" valign="top">La aplicaci&#x00F3;n mostraba adecuadamente el progreso de mi actividad mientras interactuaba con ella.</td></tr><tr><td align="left" valign="top">9</td><td align="left" valign="top">Me sentir&#x00ED;a c&#x00F3;modo/a utilizando esta aplicaci&#x00F3;n en p&#x00FA;blico, delante de otras personas.</td></tr><tr><td align="left" valign="top">10</td><td align="left" valign="top">El tiempo invertido en realizar las tareas deseadas me ha parecido adecuado.</td></tr><tr><td align="left" valign="top">11</td><td align="left" valign="top">Volver&#x00ED;a a utilizar esta aplicaci&#x00F3;n.</td></tr><tr><td align="left" valign="top">12</td><td align="left" valign="top">En general, estoy satisfecho/a con esta aplicaci&#x00F3;n.</td></tr><tr><td align="left" valign="top">13</td><td align="left" valign="top">Creo que la aplicaci&#x00F3;n puede ser &#x00FA;til para mi salud y bienestar.</td></tr><tr><td align="left" valign="top">14 (#16 in MAUQ)</td><td align="left" valign="top">Esta aplicaci&#x00F3;n tiene todas las funciones que esperaba.</td></tr><tr><td align="left" valign="top">15 (#17 in MAUQ)</td><td align="left" valign="top">He podido realizar algunas tareas incluso cuando la conexi&#x00F3;n a internet era mala o no estaba disponible.</td></tr><tr><td align="left" valign="top">16 (#18 in MAUQ)</td><td align="left" valign="top">Esta aplicaci&#x00F3;n me proporcion&#x00F3; una forma aceptable de recibir servicios de salud, tales como el acceso a material educativo, el seguimiento de mis actividades, o la realizaci&#x00F3;n de autoevaluaciones.</td></tr></tbody></table></table-wrap></sec><sec id="s4-2"><title>Comparison With Prior Research</title><p>Our findings align with prior validations of the MAUQ conducted to assess a variety of mobile apps developed for different purposes and user groups, including the MyFitnessPal in Malaysia for evaluating caloric intake, weight goals, and nutritional guidance [<xref ref-type="bibr" rid="ref16">16</xref>]; the Left-Handed Doctor mHealth app in China for medical consultations and public health guidance [<xref ref-type="bibr" rid="ref33">33</xref>]; the Enable app in Germany for cancer patients to register electronic patient-reported outcomes and monitor treatment side effects [<xref ref-type="bibr" rid="ref17">17</xref>]; and the DIGICOG-MS app in Italy for cognitive assessment of individuals with multiple sclerosis [<xref ref-type="bibr" rid="ref18">18</xref>] and patients with osteoporosis in the Persian study [<xref ref-type="bibr" rid="ref34">34</xref>]. Collectively, our findings suggest that both the MAUQ and S-MAUQ demonstrate stable content validity across diverse contexts and could be applied to a wide range of mHealth and eHealth applications designed for different populations.</p><p>It is noteworthy that a Spanish adaptation [<xref ref-type="bibr" rid="ref19">19</xref>] developed in parallel with our own work has not adhered to the MAUQ standard; instead, it was adapted for breastfeeding. Several items have undergone alterations and been reordered, and one item was eliminated. The original dimensions were modified from 3 to 4, but the results indicate a significant lack of internal consistency in 2 final subscales. Furthermore, there was an erroneous interpretation and implementation of the formula applied to calculate the level of relevance and clarity of the questionnaire items. Consequently, it was not possible to achieve comparable outcomes in different languages.</p><p>We also compared our work with the aforementioned studies that focus on the &#x201C;standalone, for patients&#x201D; version of the MAUQ. The Malaysian version of the MAUQ [<xref ref-type="bibr" rid="ref16">16</xref>] underwent an analysis similar to ours, maintaining the 3-dimensional structure but without eliminating any element. The German version of the MAUQ [<xref ref-type="bibr" rid="ref17">17</xref>] also performed a study similar to ours and to that of the Malaysian version. However, the creators of the German version considered eliminating 1 item but finally decided not to do so in order to maintain consistency with the original. The Italian version [<xref ref-type="bibr" rid="ref18">18</xref>] did not undergo content or face validation; they had a panel of 6 experts who directly compared a translated version with the original questionnaire and made modifications to have a more understandable Italian version.</p></sec><sec id="s4-3"><title>Limitations</title><p>In our study, as in other similar work [<xref ref-type="bibr" rid="ref16">16</xref>], we surveyed a large sample of native Spanish-speaking students to provide a representative sample of the young adult demographic. In future research, criterion validation studies should be conducted to predict different outcomes for different domains and types of users of the S-MAUQ.</p></sec><sec id="s4-4"><title>Conclusions</title><p>We addressed a significant gap in the field of health app evaluation in Spanish by translating and adapting the MAUQ, one of the most recognized usability questionnaires in this area. Despite the need to eliminate 2 items due to their lack of relevance and demonstrated confusion, S-MAUQ is a reliable tool in Spanish for evaluating the usability of mHealth apps.</p></sec></sec></body><back><ack><p>We would like to thank Dr. L. Zhou for granting us permission to translate the mHealth App Usability Questionnaire (MAUQ) into the Spanish version, his help during the translation process, and clarifying some of the items in the questionnaire. Thank you also for conveying to us the interest and the various requests that he received from individuals and research groups interested in having the questionnaire available in Spanish. We also thank the panel of experts and the other participants involved in this study.</p></ack><notes><sec><title>Funding</title><p>Funding for the open access charge (article processing fee [APF]): Plan Propio de la UMA - Grupo de investigaci&#x00F3;n SICUMA (TIC160) - M&#x00E1;ster de Formaci&#x00F3;n Permanente de Fisioterapia en Disfunciones de Suelo P&#x00E9;lvico (Master Ref. 81424587), Universidad de M&#x00E1;laga.</p></sec><sec><title>Data Availability</title><p>The datasets generated or analyzed during this study are available from the corresponding author on reasonable request.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization - ALCL, JFC, EDM</p><p>Formal analysis - ALCL, JFC, EDM</p><p>Investigation - ALCL, JFC, EDM</p><p>Methodology - ALCL, JFC, EDM</p><p>Supervision - ALCL, JFC, EDM</p><p>Validation - ALCL, JFC, EDM</p><p>Writing &#x2013; original draft - ALCL, JFC</p><p>Writing &#x2013; review &#x0026; editing - ALCL, JFC, EDM</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">I-CVI</term><def><p>item-level content validity index</p></def></def-item><def-item><term id="abb2">I-FVI</term><def><p>item-level face validity index</p></def></def-item><def-item><term id="abb3">MARS</term><def><p>Mobile App Rating Scale</p></def></def-item><def-item><term id="abb4">MAUQ</term><def><p>mHealth App Usability Questionnaire</p></def></def-item><def-item><term id="abb5">mHealth</term><def><p>mobile health</p></def></def-item><def-item><term id="abb6">Pc</term><def><p>probability of chance occurrence</p></def></def-item><def-item><term id="abb7">S-CVI</term><def><p>scale content validity index</p></def></def-item><def-item><term id="abb8">S-FVI</term><def><p>scale face validity index</p></def></def-item><def-item><term id="abb9">S-MAUQ</term><def><p>Spanish version of the MAUQ</p></def></def-item><def-item><term id="abb10">uMARS</term><def><p>MARS user version</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Adibi</surname><given-names>S</given-names> </name></person-group><article-title>A technology road map</article-title><source>Mobile health</source><year>2015</year><volume>5</volume><publisher-name>Springer</publisher-name><pub-id pub-id-type="doi">10.1007/978-3-319-12817-7</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>Pimmer</surname><given-names>C</given-names> </name><name name-style="western"><surname>Tulenko</surname><given-names>K</given-names> </name></person-group><article-title>The convergence of mobile and social media: affordances and constraints of mobile networked communication for health workers in low- and middle-income countries</article-title><source>Mobile Media &#x0026; Communication</source><year>2016</year><month>05</month><volume>4</volume><issue>2</issue><fpage>252</fpage><lpage>269</lpage><pub-id pub-id-type="doi">10.1177/2050157915622657</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>Ali</surname><given-names>EE</given-names> </name><name name-style="western"><surname>Chew</surname><given-names>L</given-names> </name><name name-style="western"><surname>Yap</surname><given-names>KYL</given-names> </name></person-group><article-title>Evolution and current status of mhealth research: a systematic review</article-title><source>BMJ Innov</source><year>2016</year><month>01</month><volume>2</volume><issue>1</issue><fpage>33</fpage><lpage>40</lpage><pub-id pub-id-type="doi">10.1136/bmjinnov-2015-000096</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Lunden</surname><given-names>I</given-names> </name></person-group><article-title>6.1B Smartphone users globally by 2020, overtaking basic phone subscriptions</article-title><source>TechCrunch</source><year>2015</year><month>06</month><day>2</day><access-date>2023-08-10</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://techcrunch.com/2015/06/02/6-1b-smartphone-users-globally-by-2020-overtaking-basic-fixed-phone-subscriptions/?guccounter=12015">https://techcrunch.com/2015/06/02/6-1b-smartphone-users-globally-by-2020-overtaking-basic-fixed-phone-subscriptions/?guccounter=12015</ext-link></comment></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>de la Torre-D&#x00ED;ez</surname><given-names>I</given-names> </name><name name-style="western"><surname>L&#x00F3;pez-Coronado</surname><given-names>M</given-names> </name><name name-style="western"><surname>Vaca</surname><given-names>C</given-names> </name><name name-style="western"><surname>Aguado</surname><given-names>JS</given-names> </name><name name-style="western"><surname>de Castro</surname><given-names>C</given-names> </name></person-group><article-title>Cost-utility and cost-effectiveness studies of telemedicine, electronic, and mobile health systems in the literature: a systematic review</article-title><source>Telemed J E Health</source><year>2015</year><month>02</month><volume>21</volume><issue>2</issue><fpage>81</fpage><lpage>85</lpage><pub-id pub-id-type="doi">10.1089/tmj.2014.0053</pub-id><pub-id pub-id-type="medline">25474190</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>Ball</surname><given-names>E</given-names> </name><name name-style="western"><surname>Newton</surname><given-names>S</given-names> </name><name name-style="western"><surname>Rohricht</surname><given-names>F</given-names> </name><etal/></person-group><article-title>mHealth: providing a mindfulness app for women with chronic pelvic pain in gynaecology outpatient clinics: qualitative data analysis of user experience and lessons learnt</article-title><source>BMJ Open</source><year>2020</year><month>03</month><day>12</day><volume>10</volume><issue>3</issue><fpage>e030711</fpage><pub-id pub-id-type="doi">10.1136/bmjopen-2019-030711</pub-id><pub-id pub-id-type="medline">32165550</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>Zhou</surname><given-names>L</given-names> </name><name name-style="western"><surname>Bao</surname><given-names>J</given-names> </name><name name-style="western"><surname>Setiawan</surname><given-names>IMA</given-names> </name><name name-style="western"><surname>Saptono</surname><given-names>A</given-names> </name><name name-style="western"><surname>Parmanto</surname><given-names>B</given-names> </name></person-group><article-title>The mHealth App Usability Questionnaire (MAUQ): development and validation study</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>04</month><day>11</day><volume>7</volume><issue>4</issue><fpage>e11500</fpage><pub-id pub-id-type="doi">10.2196/11500</pub-id><pub-id pub-id-type="medline">30973342</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Nielsen</surname><given-names>J</given-names> </name></person-group><source>Usability Engineering</source><year>1993</year><publisher-name>Morgan Kaufmann</publisher-name><pub-id pub-id-type="other">0-12-518405-0</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhang</surname><given-names>D</given-names> </name><name name-style="western"><surname>Adipat</surname><given-names>B</given-names> </name></person-group><article-title>Challenges, methodologies, and issues in the usability testing of mobile applications</article-title><source>Int J Hum Comput Interact</source><year>2005</year><month>07</month><volume>18</volume><issue>3</issue><fpage>293</fpage><lpage>308</lpage><pub-id pub-id-type="doi">10.1207/s15327590ijhc1803_3</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>Harrison</surname><given-names>R</given-names> </name><name name-style="western"><surname>Flood</surname><given-names>D</given-names> </name><name name-style="western"><surname>Duce</surname><given-names>D</given-names> </name></person-group><article-title>Usability of mobile applications: literature review and rationale for a new usability model</article-title><source>J Interact Sci</source><year>2013</year><volume>1</volume><issue>1</issue><fpage>1</fpage><pub-id pub-id-type="doi">10.1186/2194-0827-1-1</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>Stoyanov</surname><given-names>SR</given-names> </name><name name-style="western"><surname>Hides</surname><given-names>L</given-names> </name><name name-style="western"><surname>Kavanagh</surname><given-names>DJ</given-names> </name><name name-style="western"><surname>Zelenko</surname><given-names>O</given-names> </name><name name-style="western"><surname>Tjondronegoro</surname><given-names>D</given-names> </name><name name-style="western"><surname>Mani</surname><given-names>M</given-names> </name></person-group><article-title>Mobile app rating scale: a new tool for assessing the quality of health mobile apps</article-title><source>JMIR Mhealth Uhealth</source><year>2015</year><month>03</month><day>11</day><volume>3</volume><issue>1</issue><fpage>e27</fpage><pub-id pub-id-type="doi">10.2196/mhealth.3422</pub-id><pub-id pub-id-type="medline">25760773</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>Stoyanov</surname><given-names>SR</given-names> </name><name name-style="western"><surname>Hides</surname><given-names>L</given-names> </name><name name-style="western"><surname>Kavanagh</surname><given-names>DJ</given-names> </name><name name-style="western"><surname>Wilson</surname><given-names>H</given-names> </name></person-group><article-title>Development and validation of the user version of the Mobile Application Rating Scale (uMARS)</article-title><source>JMIR Mhealth Uhealth</source><year>2016</year><month>06</month><day>10</day><volume>4</volume><issue>2</issue><fpage>e72</fpage><pub-id pub-id-type="doi">10.2196/mhealth.5849</pub-id><pub-id pub-id-type="medline">27287964</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Brooke</surname><given-names>J</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Jordan</surname><given-names>PW</given-names> </name><name name-style="western"><surname>Thomas</surname><given-names>B</given-names> </name><name name-style="western"><surname>Weerdmeester</surname><given-names>BA</given-names> </name><name name-style="western"><surname>McClelland</surname><given-names>AL</given-names> </name></person-group><article-title>SUS&#x2014;a quick and dirty usability scale</article-title><source>Usability Evaluation in Industry</source><year>1996</year><publisher-name>Taylor and Francis</publisher-name><pub-id pub-id-type="doi">10.1201/9781498710411</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>Lewis</surname><given-names>JR</given-names> </name></person-group><article-title>The System Usability Scale: past, present, and future</article-title><source>International Journal of Human&#x2013;Computer Interaction</source><year>2018</year><month>07</month><day>3</day><volume>34</volume><issue>7</issue><fpage>577</fpage><lpage>590</lpage><pub-id pub-id-type="doi">10.1080/10447318.2018.1455307</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>Lewis</surname><given-names>JR</given-names> </name></person-group><article-title>Psychometric evaluation of the PSSUQ using data from five years of usability studies</article-title><source>Int J Hum Comput Interact</source><year>2002</year><month>09</month><volume>14</volume><issue>3-4</issue><fpage>463</fpage><lpage>488</lpage><pub-id pub-id-type="doi">10.1080/10447318.2002.9669130</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>Mustafa</surname><given-names>N</given-names> </name><name name-style="western"><surname>Safii</surname><given-names>NS</given-names> </name><name name-style="western"><surname>Jaffar</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Malay version of the mHealth App Usability Questionnaire (M-MAUQ): translation, adaptation, and validation study</article-title><source>JMIR Mhealth Uhealth</source><year>2021</year><month>02</month><day>4</day><volume>9</volume><issue>2</issue><fpage>e24457</fpage><pub-id pub-id-type="doi">10.2196/24457</pub-id><pub-id pub-id-type="medline">33538704</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>Moorthy</surname><given-names>P</given-names> </name><name name-style="western"><surname>Weinert</surname><given-names>L</given-names> </name><name name-style="western"><surname>Harms</surname><given-names>BC</given-names> </name><name name-style="western"><surname>Anders</surname><given-names>C</given-names> </name><name name-style="western"><surname>Siegel</surname><given-names>F</given-names> </name></person-group><article-title>German version of the mHealth App Usability Questionnaire in a cohort of patients with cancer: translation and validation study</article-title><source>JMIR Hum Factors</source><year>2023</year><month>11</month><day>1</day><volume>10</volume><fpage>e51090</fpage><pub-id pub-id-type="doi">10.2196/51090</pub-id><pub-id pub-id-type="medline">37910144</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Podda</surname><given-names>J</given-names> </name><name name-style="western"><surname>Grange</surname><given-names>E</given-names> </name><name name-style="western"><surname>Susini</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Italian version of the mHealth App Usability Questionnaire (Ita-MAUQ): translation and validation study in people with multiple sclerosis</article-title><source>JMIR Hum Factors</source><year>2024</year><month>09</month><day>30</day><volume>11</volume><fpage>e58079</fpage><pub-id pub-id-type="doi">10.2196/58079</pub-id><pub-id pub-id-type="medline">39347625</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Quifer-Rada</surname><given-names>P</given-names> </name><name name-style="western"><surname>Aguilar-Camprub&#x00ED;</surname><given-names>L</given-names> </name><name name-style="western"><surname>G&#x00F3;mez-Sebasti&#x00E0;</surname><given-names>I</given-names> </name><name name-style="western"><surname>Padr&#x00F3;-Arocas</surname><given-names>A</given-names> </name><name name-style="western"><surname>Mena-Tudela</surname><given-names>D</given-names> </name></person-group><article-title>Spanish version of the mHealth App Usability Questionnaire (MAUQ) and adaptation to breastfeeding support apps</article-title><source>Int J Med Inform</source><year>2023</year><month>06</month><volume>174</volume><fpage>105062</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2023.105062</pub-id><pub-id pub-id-type="medline">37037124</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sousa</surname><given-names>VD</given-names> </name><name name-style="western"><surname>Rojjanasrirat</surname><given-names>W</given-names> </name></person-group><article-title>Translation, adaptation and validation of instruments or scales for use in cross-cultural health care research: a clear and user-friendly guideline</article-title><source>J Eval Clin Pract</source><year>2011</year><month>04</month><volume>17</volume><issue>2</issue><fpage>268</fpage><lpage>274</lpage><pub-id pub-id-type="doi">10.1111/j.1365-2753.2010.01434.x</pub-id><pub-id pub-id-type="medline">20874835</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Polit</surname><given-names>DF</given-names> </name><name name-style="western"><surname>Beck</surname><given-names>CT</given-names> </name><name name-style="western"><surname>Owen</surname><given-names>SV</given-names> </name></person-group><article-title>Is the CVI an acceptable indicator of content validity? Appraisal and recommendations</article-title><source>Res Nurs Health</source><year>2007</year><month>08</month><volume>30</volume><issue>4</issue><fpage>459</fpage><lpage>467</lpage><pub-id pub-id-type="doi">10.1002/nur.20199</pub-id><pub-id pub-id-type="medline">17654487</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Polit</surname><given-names>DF</given-names> </name><name name-style="western"><surname>Beck</surname><given-names>CT</given-names> </name></person-group><article-title>The content validity index: are you sure you know what&#x2019;s being reported? Critique and recommendations</article-title><source>Res Nurs Health</source><year>2006</year><month>10</month><volume>29</volume><issue>5</issue><fpage>489</fpage><lpage>497</lpage><pub-id pub-id-type="doi">10.1002/nur.20147</pub-id><pub-id pub-id-type="medline">16977646</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zamanzadeh</surname><given-names>V</given-names> </name><name name-style="western"><surname>Ghahramanian</surname><given-names>A</given-names> </name><name name-style="western"><surname>Rassouli</surname><given-names>M</given-names> </name><name name-style="western"><surname>Abbaszadeh</surname><given-names>A</given-names> </name><name name-style="western"><surname>Alavi-Majd</surname><given-names>H</given-names> </name><name name-style="western"><surname>Nikanfar</surname><given-names>AR</given-names> </name></person-group><article-title>Design and implementation content validity study: development of an instrument for measuring patient-centered communication</article-title><source>J Caring Sci</source><year>2015</year><month>06</month><volume>4</volume><issue>2</issue><fpage>165</fpage><lpage>178</lpage><pub-id pub-id-type="doi">10.15171/jcs.2015.017</pub-id><pub-id pub-id-type="medline">26161370</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Fleiss</surname><given-names>JL</given-names> </name></person-group><source>Statistical Methods for Rates and Proportions</source><year>1981</year><edition>2</edition><publisher-name>John Wiley</publisher-name><pub-id pub-id-type="other">0471064289</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cohen</surname><given-names>J</given-names> </name></person-group><article-title>A coefficient of agreement for nominal scales</article-title><source>Educ Psychol Meas</source><year>1960</year><month>04</month><volume>20</volume><issue>1</issue><fpage>37</fpage><lpage>46</lpage><pub-id pub-id-type="doi">10.1177/001316446002000104</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wynd</surname><given-names>CA</given-names> </name><name name-style="western"><surname>Schmidt</surname><given-names>B</given-names> </name><name name-style="western"><surname>Schaefer</surname><given-names>MA</given-names> </name></person-group><article-title>Two quantitative approaches for estimating content validity</article-title><source>West J Nurs Res</source><year>2003</year><month>08</month><volume>25</volume><issue>5</issue><fpage>508</fpage><lpage>518</lpage><pub-id pub-id-type="doi">10.1177/0193945903252998</pub-id><pub-id pub-id-type="medline">12955968</pub-id></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>Cicchetti</surname><given-names>DV</given-names> </name><name name-style="western"><surname>Sparrow</surname><given-names>SA</given-names> </name></person-group><article-title>Developing criteria for establishing interrater reliability of specific items: applications to assessment of adaptive behavior</article-title><source>Am J Ment Defic</source><year>1981</year><month>09</month><volume>86</volume><issue>2</issue><fpage>127</fpage><lpage>137</lpage><pub-id pub-id-type="medline">7315877</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>Arifin</surname><given-names>WN</given-names> </name><collab>Unit of Biostatistics and Research Methodology, School of Medical Sciences, Universiti Sains Malaysia, Kelantan, MALAYSIA</collab></person-group><article-title>A web-based sample size calculator for reliability studies</article-title><source>EIMJ</source><year>2018</year><volume>10</volume><issue>3</issue><fpage>67</fpage><lpage>76</lpage><comment><ext-link ext-link-type="uri" xlink:href="http://eduimed.usm.my/index.php/eimj/issue/view/29">http://eduimed.usm.my/index.php/eimj/issue/view/29</ext-link></comment><pub-id pub-id-type="doi">10.21315/eimj2018.10.3.8</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>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="ref30"><label>30</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Fakih El Khoury</surname><given-names>C</given-names> </name><name name-style="western"><surname>Karavetian</surname><given-names>M</given-names> </name><name name-style="western"><surname>Halfens</surname><given-names>RJG</given-names> </name><name name-style="western"><surname>Crutzen</surname><given-names>R</given-names> </name><name name-style="western"><surname>Khoja</surname><given-names>L</given-names> </name><name name-style="western"><surname>Schols</surname><given-names>J</given-names> </name></person-group><article-title>The effects of dietary mobile apps on nutritional outcomes in adults with chronic diseases: a systematic review and meta-analysis</article-title><source>J Acad Nutr Diet</source><year>2019</year><month>04</month><volume>119</volume><issue>4</issue><fpage>626</fpage><lpage>651</lpage><pub-id pub-id-type="doi">10.1016/j.jand.2018.11.010</pub-id><pub-id pub-id-type="medline">30686742</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Allen</surname><given-names>P</given-names> </name><name name-style="western"><surname>Bennett</surname><given-names>K</given-names> </name><name name-style="western"><surname>Heritage</surname><given-names>B</given-names> </name></person-group><source>SPSS Statistics Version 22: A Practical Guide</source><year>2014</year><publisher-name>Cengage Learning Australia</publisher-name><pub-id pub-id-type="other">9780170348973</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>Onwuegbuzie</surname><given-names>AJ</given-names> </name><name name-style="western"><surname>Daniel</surname><given-names>LG</given-names> </name></person-group><article-title>A framework for reporting and interpreting internal consistency reliability estimates</article-title><source>Meas Eval Couns Dev</source><year>2002</year><month>07</month><day>1</day><volume>35</volume><issue>2</issue><fpage>89</fpage><lpage>103</lpage><pub-id pub-id-type="doi">10.1080/07481756.2002.12069052</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>Shan</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Ji</surname><given-names>M</given-names> </name><name name-style="western"><surname>Xie</surname><given-names>W</given-names> </name><etal/></person-group><article-title>Chinese version of the Mobile Health App Usability Questionnaire: translation, adaptation, and validation study</article-title><source>JMIR Form Res</source><year>2022</year><month>07</month><day>6</day><volume>6</volume><issue>7</issue><fpage>e37933</fpage><pub-id pub-id-type="doi">10.2196/37933</pub-id><pub-id pub-id-type="medline">35793132</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>Moulaei</surname><given-names>K</given-names> </name><name name-style="western"><surname>Dinari</surname><given-names>F</given-names> </name><name name-style="western"><surname>Sheikhtaheri</surname><given-names>A</given-names> </name><name name-style="western"><surname>Bahaadinbeigy</surname><given-names>K</given-names> </name><name name-style="western"><surname>Hajesmaeel-Gohari</surname><given-names>S</given-names> </name></person-group><article-title>The Persian version of mhealth App Usability Questionnaire (MAUQ) for patients: a psychometric assessment study</article-title><source>BMC Med Inform Decis Mak</source><year>2025</year><month>01</month><day>23</day><volume>25</volume><issue>1</issue><fpage>38</fpage><pub-id pub-id-type="doi">10.1186/s12911-025-02882-3</pub-id><pub-id pub-id-type="medline">39849456</pub-id></nlm-citation></ref></ref-list></back></article>