TABLE 1.

Summary of mHealth design guidelines

Vision	Features should include the use of large navigational buttons, a shallow navigational hierarchy, pop-up menus that appear when hovering above with cursor (28), variable font size and type, variable light and contrast settings, and adaptations to the type of interface based on user preferences (29, 30).
Cognitive	Text content should be written at a reading level and in the language of its intended users and should use explicit or concrete wording for headings (28). Further, text should avoid jargon and diagnostic labels (31), use simple sentence structure and common terms, focus on a single topic at a time, set minimal time frames for in-app tasks, and allow the user to set a self-adopted pace (29, 30).
Auditory	Features should include in-app volume control, closed captioning, voice command, and video-to-video for people who may not be able to read or write (32).
Memory	Build in repetition to facilitate retention; enable a self-adopted pace and the capacity to review; ensure variability in the presentation of information, summaries, prompts, and reminders; and include suggestions to engage in nontechnical activities to encourage multiple forms of learning and retention (3).
Mobility	Allow for short interactions with technologies, such as 2-minute time frames, and provide reasonable accommodations when using technologies. For example, do not require a camera to be on during videoconferencing in cases where a service user may be bedbound.