Please enable JavaScript.
Coggle requires JavaScript to display documents.
Coding for user interactions - Coggle Diagram
Coding for user interactions
User input
Managed with button clicks, keyboard entry and mouse clicks
In mobile applications, information is communicated through a small mobile screen, sounds, vibrations and alerts
Input mainly through touchscreen
In some cases, through the microphone or internal phone sensors
When coding for user interaction, it is important to communicate with the user effectively to encourage a response from the user
Communicating effectively with the user
There needs to be a large amount of devices which the digital solution is compatible with
User interfaces:
2 wait for input
A variable value is stored in the computer in the memory
3 process input
1 present infromation
As many actions as possible should be simplified and automated
4 provide feedback
Error messages/sound/colour alerts provide users feedback about their response
Think of someone who is playing a video game: the controller/keyboard/mouse etc collects input and sends it to the computer/PC etc and this information is processed, then sent to the monitor/screen which displays the output
Data validation
Checking that input is of the correct format and accurate to reduce user errors
providing feedback to the user to show them what they are missing in their input which they will need to include upon next entry
length of input
range of input
missing input which they need to re-input
allowed list
data patterns
check digits
Preventing user errors
clear instructions
eg. dd/mm/yy formatting
input constraints
eg. providing limited options so users are able to clearly choose between their input option
proofreading
double entries
eg. to allow the user to input multiple options to allow the user to compare their input and check for inconsistensies
Verifying user input
confirmation code
via email or SMS
lookups
looking up the value entered by the user in the database to ensure it exists (using SQL)