# Design guidelines of mobile applications for elderly In this repository, we provide a review of studies in cognition-related guidelines for mobile applications for older users. This review is part of research aimed at improving the user experience in using technology titled "Senior-Centered Design for User Interfaces of Mobile Medication Adherence Applications Based on Cognitive and Technology Attributes" [[ref](https://studylinkhere.com/)]. Based on the review of 48 studies, the authors elicited validated guidelines and recommendations targeting older people. In the primary search, 48 studies were reviewed and identified 46 targeting older people. In the next step, a full article analysis was performed and excluded 10 articles that did not contain actual guidelines or recommendations. This phase resulted in 36 articles marked as containing guidelines or recommendations for older people. As a final step, all studies that contained invalidated guidelines or recommendations were excluded, resulting in 17 articles. The final set of 17 articles was reviewed and analyzed to extract guidelines and recommendations. A total of 63 [guidelines](#Guidelines) were extracted from the 17 [studies](#Guidelines) and classified according to the cognitive attribute taxonomy related to designing UI for older people [[paper](https://dl.acm.org/doi/fullHtml/10.1145/512526.512528)]. The PRISMA flow diagram below illustrates the process followed when reviewing articles to select the relevant studies. Studies such as [[paper](https://doi.org/10.1109/ACCESS.2019.2898467)] and [[paper](https://doi.org/10.1007/978-3-030-23570-3_31)] have provided different taxonomies to classify design guidelines. Nonetheless, there is no standard or widely recognized taxonomy. ## Guidelines | **Design Guidelines for Cognitive Attributes** | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Attention** | | 1.1 Use content-oriented navigation design (e.g., lists, cards, gallery, grids) instead of menu-oriented design [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] 1.2 Use one-level navigation instead of menu structures [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] 1.3 Make navigation menu visible at all times [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 1.4 Use static menus and avoid fly-out, pull-down, dropdown, or transparent menus [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 1.5 Decrease number of dominant menus used in the same application [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] 1.6 Avoid using scroll [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](http://journalarticle.ukm.my/10051/1/10154-30688-1-PB.pdf)] 1.7 Provide an option for users to jump to the top instantly [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] 1.8 Avoid using multiple gestures in the same interface [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] 1.9 Use consistent navigation throughout interfaces (e.g., similar fonts, colors, and sizes and same set of buttons, icons, and menus) [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](https://doi.org/10.1007/978-3-319-08596-8_60)] 1.10Avoid using any distracting elements, such as ads, banners, and wallpaper [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](https://doi.org/10.1007/978-3-319-08596-8_60)] 1.11Avoid pop-up or multiple overlapping windows [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] 1.12Avoid animations, such as animated images and moving text [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 1.13Categorize information visually using different colors [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 1.14Use colorful buttons [[paper](http://journalarticle.ukm.my/10051/1/10154-30688-1-PB.pdf)] 1.15Minimize number of navigation elements [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] [[paper](https://doi.org/10.14236/ewic/HCI2011.79)] | | **Perception and recognition** | | 2.1 Provide descriptive links [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 2.2 Provide an indication of whether the device is in ring or vibration mode [[paper](https://doi.org/10.1007/s10209-013-0321-4)] 2.3 Avoid using Roman numerals [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 2.4 Clearly define mandatory versus optional fields [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] 2.5 Provide clear, continuous [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](https://doi.org/10.1007/978-3-319-08596-8_60)] [[paper](https://doi.org/10.1109/ACCESS.2018.2827358)], and consistent [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](https://doi.org/10.1109/ACCESS.2018.2827358)] feedback, whether readable [[paper](https://hal.archives-ouvertes.fr/hal-03238198)], visual [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] [[paper](https://doi.org/10.1016/j.intcom.2010.08.005)], audio [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] [[paper](https://doi.org/10.1007/s10209-013-0321-4)] [[paper](https://doi.org/10.1016/j.intcom.2010.08.005)], or vibration [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] 2.6 Define current field clearly in entry forms [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] 2.7 Provide an option to show passwords as plain text [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] 2.8 Provide confirmation of each completed task [[paper](https://doi.org/10.1007/s10209-013-0321-4)] and prior to critical instructions [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 2.9 Reduce keyboard use [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] 2.10Avoid dark, white, and patterned backgrounds as well as background images [[paper](https://hal.archives-ouvertes.fr/hal-03238198) ] 2.11Use high color contrasts between background and foreground [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](https://doi.org/10.1007/978-3-319-08596-8_60)] 2.12*Use icons with text [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](http://journalarticle.ukm.my/10051/1/10154-30688-1-PB.pdf)] [[paper](https://doi.org/10.1109/ACCESS.2018.2827358)] [[paper](https://journals.riverpublishers.com/index.php/JMM/article/view/3793)] 2.13* Use a word-based interface instead of a symbol-based or redundant (text and icon) interface [[paper](https://doi.org/10.1016/j.ijhcs.2019.102385)] 2.14Make clear distinctions between text and symbols and between touchable and non-touchable elements [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] [[paper](https://doi.org/10.1109/ACCESS.2018.2827358)] 2.15Highlight buttons when pressed [[paper](https://doi.org/10.1007/s10209-013-0321-4)] 2.16Make names of items that appear on the screen audible when touched [[paper](https://doi.org/10.1007/s10209-013-0321-4)] 2.17Locate essential supported navigation buttons at the top of the interface [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] 2.18and avoid displaying them at the bottom or on the left side of the screen [[paper](https://doi.org/10.3390/designs3030035)] 2.19Group commonly used [[paper](https://doi.org/10.1007/s10209-013-0321-4)] and semantically similar items [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] together 2.20Make a visual and touchable identification of status of keys accessible, or use locking or toggle controls [[paper](https://doi.org/10.1007/s10209-013-0321-4)] | | **Memory** | | 3.1 Show the user their current location while navigating [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 3.2 Put a title on every page and frame [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 3.3 Allow users to execute tasks in short and simple steps [[paper](https://doi.org/10.1109/ACCESS.2018.2827358)], avoiding deep hierarchies [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 3.4 Avoid unnecessary registration; if registration is necessary, only request absolutely crucial details [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] 3.5 Divide information into separate, small parts [[paper](https://doi.org/10.1007/978-3-319-08596-8_60)] 3.6 Use automatic entries as much as possible [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 3.7 Make the design intuitive to avoid the need for the user to recall information [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] 3.8 *Use grid menu layouts and avoid horizontal menu layouts [[paper](https://doi.org/10.1088/1742-6596/1196/1/012058)] 3.9 * Replace tab menus with vertical menus as possible and provide appropriate visual cues [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] | | **Learning** | | 4.1 Use users’ operation habits for mobile navigation [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] 4.2 Make exploring the screen and menus easy, without the need for excessive searching [[paper](https://doi.org/10.1007/s10209-013-0321-4)] 4.3 Support familiar aspects of visual object manipulation [[paper](https://doi.org/10.14236/ewic/HCI2011.79)] 4.4 Provide an undo button to revert actions [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 4.5 Provide support tutorials [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 4.6 Make registration process clear and self-explanatory [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] | | **Reading, speaking, and listening** | | 5.1 Make text large [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] and suitable [[paper](https://doi.org/10.3923/ajit.2017.38.44)], ranging from 12 to 18 point [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](http://journalarticle.ukm.my/10051/1/10154-30688-1-PB.pdf)] [[paper](https://doi.org/10.1109/GCCE.2017.8229479)] 5.2 Use active rather than passive voice [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 5.3 Reduce number of gestures [[paper](https://doi.org/10.1080/0144929X.2019.1622786)] [[paper](https://hal.archives-ouvertes.fr/hal-03238198)]; some studies prefer clicks [[paper](http://journalarticle.ukm.my/10051/1/10154-30688-1-PB.pdf)] while others prefer drag and pinch [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] as the main gestures for interacting with the user interface 5.4 Provide option to adjust volume [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](https://doi.org/10.1007/s10209-013-0321-4)] 5.5 Provide option to turn off audio feedback [[paper](https://doi.org/10.1007/s10209-013-0321-4)] 5.6 Provide ample time to use or read content [[paper](https://doi.org/10.1109/ICOS.2018.8632701)] [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 5.7 Increase duration of beep sounds [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 5.8 Use a default [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)], non-decorated [[paper](https://hal.archives-ouvertes.fr/hal-03238198)], sans-serif font like Arial [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] [[paper](http://journalarticle.ukm.my/10051/1/10154-30688-1-PB.pdf)] [[paper](https://doi.org/10.3923/ajit.2017.38.44)], Helvetica, or Verdana [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 5.9 Use natural rather than synthetic speech [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 5.10* Use male voices [[paper](https://hal.archives-ouvertes.fr/hal-03238198)] 5.11* Avoid selective attention that distracts from auditory tasks, such as use of opposite-sex voices [[paper](https://doi.org/10.1109/ecti-con49241.2020.9157905)] | | **Problem-solving, planning, reasoning, and decision-making** | | 6.1 Provide options to activate or deactivate support functions or individual assistive technologies [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] 6.2 Avoid providing more detailed information at lower hierarchical levels [[paper](https://doi.org/10.1007/978-3-319-60597-5_22)] | (*) Indicates contradictory guidelines The table above illustrates that there is generally agreement among the guidelines suggested and recommended in previous studies. However, there are contradictions between some guidelines—for example, with regard to the attribute of perception (2.12). ## Authors - [Dr. Reem Alnanih](mailto:ralnanih@kau.edu.sa?subject=[GitHub]%20Elderly%20guidelines) - [Amal Balabid](mailto:amalBalabid@gmail.com?subject=[GitHub]%20Elderly%20guidelines) - [Lina Bahmdean](mailto:lbahmdean@gmail.com?subject=[GitHub]%20Elderly%20guidelines) ## Citation If you use whole or partial these collected and classified guidelines, please cite the paper: ref will be added here.