For my article “Mobile PHRs compliance with Android and iOS usability guidelines”, a short mobile usability survey was conducted to validate the questionnaire in the article. The survey was created online using Google Forms and it was published on my Twitter account. Since some participants asked me if I could publish the results, here they are. The survey contained 13 questions that participants had to evaluate on a scale of 1-5 regarding their interaction with mobile applications.
Participants’ age: between 18 and 51.
|Simple writing style. Everything is understandable and simple, avoid unexplained terms or acronyms.||3.64|
|Pictures used to explain concepts. Pictures to support text for a faster and easier navigation.||3.95|
|Known icons used for common actions. Same icons for same actions in different apps.||4.18|
|Vertical and horizontal orientations. Adaptation to different device orientations.||3.59|
|Preferences are learned over time. Store settings, logs, search history, autocomplete fields, etc.||3.45|
|Reactions of interactive items. Change color or illumination after the user interacts with an element.||3.64|
|Messages showing information related to actions that the user needs to consider.||3.55|
|Acknowleding messages to let you know that an action has been completed. e.g. after updating a set of data a message saying “Updated”.||4.23|
|Activity indicators for long tasks. e.g. progress bars.||4.27|
|Fast load of the app. e.g. immediate startup with no splash.||4.00|
|Delay login/register. Let you test some functionalities of the app before requiring login or register.||3.59|
|Known structure patterns. Tabs (on the bottom or top), Navigation Drawer (e.g. Facebook mobile app), etc.||3.73|
|Navigation consistent between hierarchical screens. e.g. Hitting the back button will lead you to the previous page rather than the home screen.||4.23|