App UI checks
Use at most one action on the screen that is highlighted as the most likely for the user. (Example: in iOS a blue button represents the default or most likely action).
To keep controls as unobtrusive as possible for instance by fading them out if they are not used for a while.
Make it possible for users to go back to a previous screen for instance by adding a back or cancel button
The main function of the app should be apparent immediately. It should speak for itself.
If the app is stopped at an unexpected time, user data should be saved locally and available at start-up.
Do not use standard buttons for other functions then that they are normally used for
Users should be warned of the consequences of deleting a document Keyboard adjusts to expected input (for instance numbers/letters when expected).
Are inactive buttons clearly distinguished from active buttons?
Minimize user actions by using a picker or a table view where users can select a certain choice over a data entry field where users have to type a choice
In an app, the user should not be able to store files locally, outside the app sandbox.
In an app, the user should not be exposed to the permissions of a specific file
Tapable elements should be about 7x7 mm in size, using the pixel density of the target device you can calculate the amount of pixels (chapter documentation contains a link to different devices compared).
Do not redefine gestures in your app that have a standard meaning (example:swiping from top to bottom enables the notification center)
Requirement to login is delayed in the app as long as possible
In case of ‘live’ filtering of data while the user enters his search query, verify the performance.
The appearance of buttons that perform standard actions are not altered in the app (for instance: refresh, organize,trash, Reply, back, etc.)
If there is a long list of data to scroll trough, provide a search option above the list.
If performance is slow, indicate a progress status icon (“Loading…”), preferably with specific message.
The app should respond to all changes in device orientation, as per the design
Use at most one action on the screen that is highlighted as the most likely for the user. (Example: in iOS a blue button represents the default or most likely action).
To keep controls as unobtrusive as possible for instance by fading them out if they are not used for a while.
Make it possible for users to go back to a previous screen for instance by adding a back or cancel button
The main function of the app should be apparent immediately. It should speak for itself.
If the app is stopped at an unexpected time, user data should be saved locally and available at start-up.
Do not use standard buttons for other functions then that they are normally used for
Users should be warned of the consequences of deleting a document Keyboard adjusts to expected input (for instance numbers/letters when expected).
Are inactive buttons clearly distinguished from active buttons?
Minimize user actions by using a picker or a table view where users can select a certain choice over a data entry field where users have to type a choice
In an app, the user should not be able to store files locally, outside the app sandbox.
In an app, the user should not be exposed to the permissions of a specific file
Tapable elements should be about 7x7 mm in size, using the pixel density of the target device you can calculate the amount of pixels (chapter documentation contains a link to different devices compared).
Do not redefine gestures in your app that have a standard meaning (example:swiping from top to bottom enables the notification center)
Requirement to login is delayed in the app as long as possible
In case of ‘live’ filtering of data while the user enters his search query, verify the performance.
The appearance of buttons that perform standard actions are not altered in the app (for instance: refresh, organize,trash, Reply, back, etc.)
If there is a long list of data to scroll trough, provide a search option above the list.
If performance is slow, indicate a progress status icon (“Loading…”), preferably with specific message.
The app should respond to all changes in device orientation, as per the design
