Developing a functional UI (Showing the outputs (Its useful to consider…
Developing a functional UI
Showing the outputs
Its useful to consider what outputs your interface needs to give out. Once clearly defined you can work backwards to find out what inputs are required.
Error messages - when will they be displayed and what do they look like. They should clearly tell the user what the error is and give guidance in how to overcome it.
Sounds - will any sounds be played to the user after doing something and what will it sound like.
Sense - will the device vibrate after doing something, and what for.
Showing the navigation methods
Your user interface needs to show how the user is going to navigate around it. you need to carefully examine what methods of input are available for the device the interface is on.
Using the keyboard or on screen key to enter keyboard shortcuts.
Saying commands verbally and using a natural voice.
Clicking or tapping buttons or hyperlinks.
Showing the inputs
The user interface must show all the different inputs.You need to show which need to show which areas of the interface require the use of different inputs.
Key presses - which areas of the UI require keyboard to select items or input typed data.
Touch - which areas of the UI require the use of the finger to carry out gestures.
Mouse clicks - what areas of the UI require the mouse to select items using the cursor.
The user inputs data such as a command into the system using a user interface.
A user interface does not process data. This will collect data from the input stage, process them away from the user interface and then send the processed data back to the interface.
The processed data is displayed on the user interface for the user to see, hear or feel.