| Literature DB >> 29764800 |
Otis L Owens1, Jenay M Beer2,3, Ligia I Reyes4, David G Gallerani5, Amanda R Myhren-Bennett5, Karen K McDonnell5.
Abstract
BACKGROUND: Up to 70% of lung cancer survivors are affected by chronic obstructive pulmonary disease (COPD), a common, debilitating, comorbid disease. Lung cancer and COPD are both characterized by symptoms such as breathlessness, fatigue, and psychological distress. These distressing chronic symptoms are exacerbated by stress and detract from an individual's quality of life.Entities:
Keywords: chronic obstructive pulmonary disease; lung neoplasms; mindfulness; mobile apps; review
Year: 2018 PMID: 29764800 PMCID: PMC5974462 DOI: 10.2196/mhealth.9831
Source DB: PubMed Journal: JMIR Mhealth Uhealth ISSN: 2291-5222 Impact factor: 4.773
Figure 1App review steps. COPD: chronic obstructive pulmonary disease.
Figure 2App inclusion flow.
Usability heuristics for user interface design.
| Heuristica,b | Definition | Questionnaire items |
| Visibility | The system should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time | Does every screen begin with a title or header? It is obvious to the user what is going on? Is the font large enough? |
| Match between system and real world | The system should speak the users’ language, with words, phrases, and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order | Are menu choices and information ordered in a logical way? Do related and interdependent information appear together? Is language clear and concise (terminology familiar to users)? |
| Consistency | Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions | Does the app use a minimal number of colors (ie, color consistency)? Is there a consistent design scheme across the app? Do online instructions/information appear in a consistent location across screens? |
| User control and freedom | Users often choose system functions by mistake and will need a clearly marked emergency exit to leave an unwanted screen without having to go through an extended dialogue. Support undo and redo actions | Is there navigation on the homepage of the app? Can users easily reverse their actions? Is the app explore-able and easy to navigate? |
| Error prevention | Even better than good error messages is a careful design that prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to an action | Are menu choices logical, distinctive, and mutually exclusive? Are buttons/commands placed a good distance from one another? Does the system prevent users from making errors whenever possible? |
| Recognition rather than recall | Minimize the users’ memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate | Are instructions visible? Is it obvious what is clickable? Does the app require high levels of concentration? |
| Flexibility and efficiency of use | Accelerators—unseen by the novice user—may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions | Does the app provide function keys for high-frequency commands? Does the app allow for customization (eg, settings, search)? Does the app provide customization for frequency users (eg, log in, saves data)? |
| Aesthetic and minimalist design | Dialogues should not contain information that is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with and diminishes the visibility of relevant information | Is the layout clearly designed avoiding visual noise? Does the use of images and multimedia content add value? Are images well sized and is the resolution appropriate? |
| Error recovery | Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution | Are there error messages? Is sound, images, or haptics used to signal an error? Are error messages worded so the user understands the problem and what to do next? |
| Help and documentation | Ideally, the system can be used without documentation, but in the case of questions or confusion, it’s important to provide help and documentation. Any such information should be easy to search, focused on the user’s needs, list concrete steps to be carried out, and not be too lengthy | Are there instructions/help/documentation? Are navigation and instructions easy to find? Are navigation and instructions procedural (how do I use the app)? |
aHeuristics are not mutually exclusive.
bAll questionnaire items ranked on the following scale: 1=cosmetic problem only, 2=minor usability problem, 3=major usability problem, and 4=catastrophic usability problem.
Average usability heuristic scores across apps.
| Appa | Heuristicb | Mean (SD)c | ||||||||||
| V | M | CS | CT | EP | R | F | A | ER | H | |||
| 1 | 3.00 | 3.50 | 1.17 | 2.17 | 2.67 | 3.33 | 2.83 | 2.00 | 0.67 | 2.83 | 2.42 (0.92) | |
| 2 | 1.50 | 0 | 0 | 0.17 | 0.67 | 0.67 | 2.00 | 0 | 1.83 | 0.17 | 0.70 (0.79) | |
| 3 | 3.00 | 3.00 | 2.20 | 3.00 | 3.00 | 3.20 | 2.60 | 3.20 | 1.00 | 3.00 | 2.72 (0.67) | |
| 4 | 1.80 | 2.00 | 2.00 | 0.80 | 1.40 | 2.40 | 0.80 | 2.00 | 0 | 2.40 | 1.56 (0.79) | |
| 5 | 3.50 | 3.50 | 3.00 | 3.50 | 3.50 | 3.33 | 2.50 | 2.33 | 3.17 | 3.83 | 3.22 (0.48) | |
| 6 | 1.83 | 2.17 | 2.00 | 1.83 | 2.50 | 2.33 | 1.50 | 2.00 | 2.67 | 2.83 | 2.17 (0.42) | |
| 7 | 0.80 | 1.20 | 0 | 0 | 0.40 | 0.80 | 0.60 | 0 | 0 | 1.20 | 0.50 (0.49) | |
| 8 | 2.20 | 3.20 | 3.00 | 3.20 | 2.80 | 3.00 | 1.00 | 0 | 2.40 | 2.40 | 2.32 (1.05) | |
| 9 | 0.50 | 0.50 | 2.50 | 1.75 | 1.25 | 2.25 | 0.50 | 1.25 | 1.50 | 1.50 | 1.35 (0.71) | |
| Mean (SD)c | 2.01 (1.02) | 2.12 (1.31) | 1.76 (1.14) | 1.82 (1.29) | 2.02 (1.11) | 2.37 (1.02) | 1.59 (0.92) | 1.42 (1.18) | 1.47 (1.15) | 2.24 (1.11) | — | |
aApps: 1=COPD Disease (Droid Clinic, United States); 2=Lung+ Pioneering Healthcare (Roche, Indianapolis, Indiana, United States), 3=COPD (Health Tips, United States), 4=Pranayama Free (Sagaara, Ann Arbor, Michigan, United States), 5=Breathcount (Segfoltas, Kaunas, Lithuania), 6=Asthma Tracker and Log (Roving Reptiles Software, Castle Rock, Colorado, United States), 7=My Breathfree (Cipla Digital. Sussex, England), 8=7Pranayama—Yoga Breath Calm (Pixel Point Technology, Jaipur, India), and 9=Loving Meditations—Bring Calm To Cancer (Loving Meditations, New York, New York, United States).
bV: visibility; M: match between system and real world; CS: consistency; CT: user control and freedom; EP: error prevention; R: recognition rather than recall; F: flexibility and efficiency of use; A: aesthetic and minimalist design; ER: error recovery; H: help and documentation.
cHigher score indicated a greater frequency, impact, and persistence of usability issue. All questionnaire items were ranked on the following scale: 1=cosmetic problem only, 2=minor usability problem, 3=major usability problem, and 4=catastrophic usability problem. Mean and SD were calculated based on average score (1-4) across all heuristics and within each separate heuristic.
Grade-level reading scores. COPD: chronic obstructive pulmonary disease.
| App name | Grade-level reading score |
| My Breathefree | 7.4 |
| COPD Disease | 12.6 |
| Lung+ Pioneering Healthcare | 9.4 |
| COPD | 9.2 |
| Pranayama Free | 12.5 |
| Asthma Tracker & Log | 9.1 |
| 7pranayama—Yoga Breath Calm | 10.5 |
| Loving Meditations—Bring Calm to Cancer | 12.8 |
| Breathcount | Unable to calculate |