Multimedia Application Design and Human-Computer Interaction
What this domain tests
How a multimedia product is designed around users: process, interaction styles, usability heuristics and accessibility. Items give a scenario and ask which principle is violated or which design step comes next.
Core rules and concepts
- Design process: user and task analysis, requirements, information architecture, interaction design, visual design, prototype (low then high fidelity), usability testing, iteration.
- Interaction styles: command line, menu and form, direct manipulation (WIMP), natural interaction (touch, voice, gesture), and hypermedia navigation for content-rich products.
- Usability heuristics: visibility of system status, match to the real world, user control and freedom (undo, exit), consistency, error prevention, recognition over recall, minimalist design, flexibility, helpful error messages, documentation.
- Perception and cognition. Response-time thresholds: about 0.1 s feels instantaneous, 1 s preserves flow of thought, 10 s is the limit before attention wanders - hence progress indicators for long operations. Fitts's law (target size and distance govern pointing time) and Hick's law (decision time grows with the number of equally likely choices) justify large buttons and shallow menus. Affordances and signifiers make actions discoverable; mental models explain why metaphors matter.
- Accessibility: WCAG contrast of at least 4.5:1 for normal text, captions and transcripts, keyboard operability, no colour-only encoding, adjustable playback speed.
- Application types: presentation, tutorial/CBT, query/kiosk, simulation, entertainment - each implies different navigation and feedback needs.
Worked example
A video player shows a spinner while buffering, a progress bar with elapsed and total time, a pause control, and an error message with a retry button when the stream fails. Which heuristics are being applied? The spinner and progress bar implement visibility of system status; pause and seek implement user control and freedom; retry with a plain-language message implements helpful error recovery. Naming the heuristic for each element, rather than just praising the interface, is what the marking scheme rewards.
Traps that cost marks
- Choosing visual polish over task completion when the two conflict.
- Adding many options, which increases decision time under Hick's law.
- Conveying state by colour alone, failing colour-blind users.
- Running usability tests after implementation with no plan to act on findings.