MATcH Checklist

MATcH
Checklist for Evaluating the Usability of Aplications for Mobile Touchscreen Phones

Do you want to evaluate the usability of an application for touchscreen phones, but you can't perform a usability test?
You can do a heuristic evaluation filling out this form. As a result, you will know the usability rating of your application
and its position in the ranking of applications that have already been evaluated. More information here.

Application	*	Version
Phone model		Platform	*	Android	iOS	Other
E-mail			* required fields

You have to check Yes (if the application satisfies the question), No (if it does not satisfy the question) or Not applicable (if it does not cover the item evaluated by the question).

Heuristic 1: Visibility of system status

1. For each user action, the application provides immediate and appropriate feedback on their status?

For example, after some tasks, like sending an email, file upload or deletion, a message like “email sent” or “file deleted” is shown.

Yes
No
Not applicable

2. Interactive components being selected are clearly distinct from others?

For example, the state of buttons changes when pressed or the menu tab being viewed is highlighted.

Sim
No
Not applicable

3. Messages about the status of the application use a clear and concise language?

For example, screen titles or error messages are easy to understand.

Yes
No
Not applicable

4. Provides a status update for slower operations slower?

For example, an indication can be in form of an icon or text about the progress of the system request or a file.

Yes
No
Not applicable

Heuristic 2: Match between system and the real world

5. The meaning of symbols and icons is understandable and intuitive?

Use of icons and symbols that are easy to recognize and that are relate with the task they are associated.

Yes
No
Not applicable

6. Information is arranged in a logical and natural order?

For example, items in a selection list (names, products, etc) are ordered by an appropriate criterion (e.g. alphabetically).

Yes
No
Not applicable

Heuristic 3: User control and freedom

7. It is the user who initiates and terminates tasks and not the application?

For example, wait for the user to type “enter” after having inserted a search term to start the search.

Yes
No
Not applicable

8. It is possible to identify the number of steps required to perform a task?

For example, from a numerical indication (1-5) of the quantity of pages or steps, or presenting a tutorial or dividing the task into tabs.

Yes
No
Not applicable

9. It is possible to return to the previous screen at any time?

For example, by navigating via tabs or in form of a button to return to the main menu or from the device’s menu itself.

Yes
No
Not applicable

10. Applications with logins: allow easy access to more than one user?

For example, a electronic commerce app allows the easy selection of which account to use for shopping.

Yes
No
Not applicable

11. The user can cancel an action in progress?

For example, cancel the download of a file in progress.

Yes
No
Not applicable

12. The application indicates clearly what’s the next step to accomplish a task?

Like a button to advance or an explication note.

Yes
No
Not applicable

Heuristic 4: Consistency and standards

13. Screens with the same type of content have the same title?

For example, all search screens have the same title.

Yes
No
Not applicable

14. Controls and buttons are distinguished from the rest of the layout, making it clear that they are clickable?

For example, differentiate buttons applying shade or other features to simulate depth.

Yes
No
Not applicable

15. All textual information from the application uses the same language?
Yes
No
Not applicable

16. Different functions are presented differently to the user?

For example, different functions like save and cancel are always represented using the same label or icon.

Yes
No
Not applicable

17. Similar functions are presented in a similar way?

For example, using the same icon or button label for the same functionality in different screens or propose the same data entry structure for the same functionality on different screens.

Yes
No
Not applicable

18. Controls that perform the same function are in similar positions on the screen?

For example, if on one screen the button to advance stays on the right side, such a button has to be on the right side on other screens, too.

Yes
No
Not applicable

19. The way of navigation is consistent between screens within the application?

Keep the same type of navigation (vertical scrolling, horizontal scrolling, menus and tabs) on all screens.

Yes
No
Not applicable

20. Links are treated consistently between screens?

Keep the same visual design in terms of color, type and font style (p.eg. bold, underline).

Yes
No
Not applicable

21. Textual information is presented in a standardized way?

Present similar informative texts in the same way and with the same visual design (font size, type and color).

Yes
No
Not applicable

22. Data and key messages are in the default position for applications of this platform?
Yes
No
Not applicable

23. Input fields make the need for data entry obvious?

For example, putting a cursor inside a textbox.

Yes
No
Not applicable

Heuristic 5: Recognition rather than recall

24. The application uses in its texts and labels an understandable language to the user?

Avoiding technical terms or terminology specific to a certain domain of a certain area.

Yes
No
Not applicable

25. Titles of screens adequately describe their content?
Yes
No
Not applicable

Heuristic 6: Flexibility and efficiency of use

26. The application works correctly during interaction?

For example, the application does not crash and buttons work on the first click.

Yes
No
Not applicable

27. The tasks are relatively simple to be executed?

For example, tasks that can be completed in a few steps.

Yes
No
Not applicable

28. The most used functions are easily accessible?

The most used functions should be accessible without the need to scroll or navigate between many screens.

Yes
No
Not applicable

29. The application uses icons instead of labeled buttons?
Yes
No
Not applicable

30. All screens keep menus and functions that are common to the application accessible?

For example, in email applications, the inbox is accessible from all screens of the application.

Yes
No
Not applicable

Heuristic 7: Aesthetic and minimalist design

31. Only information related to the task being performed is displayed?

For example, on a registration screen, other information shouldn’t be displayed.

Yes
No
Not applicable

32. Texts are only used only when absolutely necessary?

For example, textual instructions shouldn’t be too long.

Yes
No
Not applicable

33. Menus are esthetically simple and clear?

With options easy to find, presented in a logic order and with short titles.

Yes
No
Not applicable

34. Only small amounts of information are displayed on each screen?

Without text or images in excess.

Yes
No
Not applicable

35. Titles and labels are short?
Yes
No
Not applicable

36. Abbreviations are avoided?
Yes
No
Not applicable

Heuristic 8: Minimized human/device interaction

37. The navigation is intuitive?

For example, it is easy to get to the intended screen.

Yes
No
Not applicable

Heuristic 9: Physical interaction and ergonomy

38. Buttons have an adequate size to click?

For example, avoiding very small buttons, which may cause easily the selection of the wrong option.

Yes
No
Not applicable

39. The main navigation is in the default position for applications on this platform?

For example, placing the menu on the bottom bar for iOS applications and on the superior bar for Android applications.

Yes
No
Not applicable

40. Buttons and controls are easily accessible with any hand?
Yes
No
Not applicable

41. The clickable area of links and buttons occupies the whole button/link area?
Yes
No
Not applicable

Heuristic 10: Readability and layout

42. Spacing between rows facilitates reading?

Neither too big, for not increasing unnecessarily the amount of scrolling, nor too little for not difficulty too much the reading.

Yes
No
Not applicable

43. Fonts used facilitate reading?

In terms of size, type and style.

Yes
No
Not applicable

44. Icons have sufficient contrast in relation to the background?
Yes
No
Not applicable

45. Text has enough contrast against the background?

For example, avoiding light gray text on a white background

Yes
No
Not applicable

46. The color and details of images facilitate reading on a small screen?

The resolution must allow easy identification of the elements of the image and icons should not have many details using a more abstract representation.

Yes
No
Not applicable

47. The application highlights the most important content, presenting them in a large, shiny, bold or more detailed way?
Yes
No
Not applicable

48. The alignment used facilitates reading?

For example, giving preference to left or justified alignment for plain text.

Yes
No
Not applicable


	1 \| 2 \| 3 \| 4

	Software Quality Group - GQS National Institute for Research and Technology on Digital Convergence - INCOD Department of Informatics and Statistics - INE Federal University of Santa Catarina - UFSC 88.049-200 Florianopolis - SC Brazil gqs@incod.ufsc.br	SUPPORT
About \| Privacy Policy \| Terms of Service