1/9
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
---|
No study sessions yet.
Visibility of system status
The system should always inform users about what is happening (e.g., loading bars, notifications)
Match between system and real world
The system should speak the users' language using familiar concepts and metaphors (e.g., trash can icon for delete)
User control and freedom
Users should be able to undo and redo actions easily (e.g., back button, undo delete)
Consistency and standards
Interfaces should follow platform conventions so users don't have to guess (e.g., same icon behavior across screens)
Error prevention
Prevent errors before they happen with good design (e.g., disable submit button until form is complete)
Recognition rather than recall
Show options instead of making users remember info (e.g., auto-complete, visible menu)
Flexibility and efficiency of use
Allow experienced users to use shortcuts or faster workflows (e.g., keyboard shortcuts, power-user modes)
Aesthetic and minimalist design
Keep design simple and uncluttered — only show what's necessary (e.g., avoid visual noise)
Help users recognize
diagnose, and recover from errors,Use clear error messages and explain how to fix the problem (e.g., "Invalid email, try again")
Help and documentation
Provide accessible help even if it's not needed often (e.g., tooltips, FAQs, support links)