In order to pass the Mobile Community of Excellence's (MCoE's) Certification process, your application will need to pass a UI/UX review. We have provided a checklist below that shows, at-a-glance, each of the concepts or elements we will be looking for during this review. The checklist has been broken down into three primary areas: Foundational Elements, User Interface (UI) and User Experience (UX) & Interaction.
The links provided throughout the checklist will give more detail or context that you may find helpful.
WHO IS THIS DOCUMENT FOR?
Business Stakeholders, Product Owners, Designers
TABLE OF CONTENTS
Foundational Elements
Description | YES | NO | N/A | |
---|---|---|---|---|
1 | The app has a clear purpose or task that can be described in one sentence. | |||
2 | The app has a defined audience. | |||
3 | The appropriate mobile platforms are supported based on the defined audience. | |||
4 | The UI/UX is consistent throughout the app. | |||
5 | The app is either branded or white-labeled. | |||
6 | An organized repository of known issues exists. |
User Interface (UI)
Description | YES | NO | N/A | |
---|---|---|---|---|
1 | If the app is branded, the appropriate brand guidelines have been followed. | |||
2 | If the app is white-labeled, there are no elements reflecting a certain brand. | |||
3 | If the app is white-labeled, customizable elements have been specified. | |||
4 | The UI is modern and designed for the latest version of each supported mobile platform(s). | |||
5 | The UI aims to be beautiful and pleasing to its intended audience. | |||
6 | All accessibility requirements have been met. | |||
7 | Content utilizes a hierarchical system to promote readability and understanding. | |||
8 | Only brand and/or default mobile platform fonts for iOS and/or Android are being used. | |||
9 | No underlined links. | |||
10 | No unapproved iconography. | |||
11 | Icons are accompanied by labels where appropriate. | |||
12 | App icons for iOS and/or Android have been created and follow good design practices. | |||
13 | All other required design assets for submission to Apple and/or Google have been created. | |||
14 | Images and assets have been provided for all required screen densities for each supported mobile platform (iOS and/or Android). | |||
15 | At least two iterative rounds of user research have been conducted and all 1, 2 and 3 issues have been resolved or addressed (see Severity Scale). | |||
16 | A plan for regular and routine user research has been implemented and is being executed (see Research Schedule). |
User Experience (UX) & Interaction
Description | YES | NO | N/A | |
---|---|---|---|---|
1 | Standard gestures and interactions specific to each supported mobile platform are being utilized. | |||
2 | Justification and/or positive user testing results have been provided if custom gestures and/or interactions are being implemented. | |||
3 | Interactive elements are readily apparent (not hidden). | |||
4 | Interactive elements are sized for fingers. | |||
5 | Critical functionality is not hidden. | |||
6 | If hidden shortcuts are used, the same action is available for non-power users. | |||
7 | Input fields are properly labeled and aim to reduce typing and errors. | |||
8 | When in focus, input fields summon the correct keyboard or picker based on the input required. | |||
9 | Input fields use validation (immediate is preferred) and provide users with appropriate error messages. | |||
10 | Temporary views are used appropriately (alerts, modal views, new screens, etc.). | |||
11 | If embedded web views are used, they are optimized for mobile. | |||
12 | A versioned editorial document has been created (or documented as part of Epics/User Stories in JIRA) and includes error messaging. | |||
13 | At least two iterative rounds of user research have been conducted and all 1, 2 and 3 issues have been resolved or addressed (see Severity Scale). | |||
14 | A plan for regular and routine user research has been implemented and is being executed. (see Research Schedule). |
Last Reviewed/Updated: March 2018