IDEA9105 Chap.1 Interface Lineages and Interaction Paradigms

Interface Lineages and Interaction Paradigms

An interface makes parts of a system perceptible and offers actions through controls, language and spatial arrangement. The user forms an expectation, acts, observes system feedback and updates that expectation. Breakdowns occur when the visible representation does not match the underlying state or when available action is hidden. A beautiful screen can fail if feedback arrives late, labels mislead or recovery is costly.

Evaluate the complete loop: goal, available action, execution, system response, interpretation and next move. A save icon changes colour but gives no confirmation that data reached the server. The user sees a local visual response yet cannot infer persistence. Adding a clear state message repairs the interpretation gap rather than merely intensifying the colour.

Describe the task in verbs and mark where the user must infer hidden state. Then decide whether visibility, mapping, constraint or feedback is the appropriate repair. Interface evidence becomes actionable when action is tied to a user goal, a context and an observable interaction. Convert representation into a design requirement that can be inspected in a wireframe or prototype.

Then define the success and failure states for feedback, including the recovery path. An interface lineage becomes testable only when transition, feedback and access behaviour are explicit. Inventory the entry, available action, system response, next state and recovery route. Link representation to a cue the user can perceive, not an intention visible only to the designer.

Command interfaces let experienced users compose operations precisely and automate sequences, but they demand recall, syntax knowledge and error interpretation. Their efficiency depends on stable grammar, discoverable help and feedback that reveals what the system understood. Completion, history, examples and reversible execution can reduce recall cost without removing expressive control.

The design question is not whether graphical or command interaction is universally better, but which tasks, users and failure costs fit each form. A data analyst repeats a transformation daily. A command can be faster and auditable, while a searchable palette helps occasional users discover the same operation. Both can invoke one underlying action with different entry points.

Observe task frequency, compositional complexity and error consequence. Prototype recovery from an invalid command, not only the successful path, because error language is part of the interface. A designer can test command language by turning the assumption into a task with a clear start state and completion signal.

Observe where a participant hesitates around recall, what they expect next and which cue changes their interpretation. For automation, record behaviour separately from the participant's explanation. The resulting evidence should identify a design decision, not merely produce a list of comments. Turn the assumption about command language into a task protocol.

Give the participant realistic information, avoid coaching the route through recall, and decide in advance which behaviour would support or challenge the design. Direct manipulation represents objects and actions in a visible workspace. Incremental operations and immediate feedback shorten the distance between intention and result.

The benefit depends on good mapping: movement, handles and constraints should correspond to the user's conceptual model. Not every system state can be placed on screen at once. Dense controls can overwhelm novices, while gestures without cues recreate hidden syntax. Designers choose which objects remain visible and which actions need progressive disclosure.

A timeline editor lets a user drag a clip and see adjacent clips shift. The same operation expressed through numerical fields may be more precise but harder to explore. Offering both routes supports different moments in the task. Test whether users can predict the result before release and undo it afterward. A surprising animation may entertain while weakening control if it conceals the new state.

Represent direct manipulation at the lowest fidelity that can answer the current question. Layout sketches expose hierarchy and flow; interactive prototypes expose state, timing and feedback. When evaluating mapping, keep content realistic enough for users to make meaningful choices.

Track reversibility across normal, empty, loading and error conditions so that the design demonstrates a complete interaction rather than one ideal route. Use fidelity as an experimental choice for direct manipulation. A sketch can compare hierarchy and navigation cheaply, while a linked prototype is needed to inspect timing, feedback and state transition around mapping.

Touch removes the separate pointer and makes the user's body part of input. Fingers occlude targets, vary in precision and operate within reach zones. Mobile contexts also involve movement, brief sessions, orientation changes and competing environmental demands. A swipe can be efficient after discovery but invisible beforehand. Critical actions should not depend on an undiscoverable gesture alone.

Target size, spacing, feedback and accidental activation must be considered together. A destructive item action is available only through a left swipe. Experienced users move quickly, while new users cannot find it and motor-impaired users struggle to perform it. A visible menu provides an equivalent path. Prototype on the target device and in realistic posture.

Watch the hand obscure content, record reach and error recovery, and avoid using a desktop cursor simulation as the only evidence. Accessibility belongs inside the interface model. Ask whether touch target remains perceivable and operable with different input, vision and reading conditions.

Apply occlusion through contrast, hierarchy, labelling and focus order, then inspect whether gesture communicates status without relying on colour alone. These checks often reveal general usability defects because explicit structure benefits more than one access need. Audit touch target through keyboard order, focus visibility, readable hierarchy, labels and non-colour feedback.

Ask whether occlusion remains understandable at magnification and whether controls expose name, role, state and error recovery. Accessibility evaluation combines standards, inspection and use by people with relevant access needs.

What this chapter covers

• 01

  An interface mediates action and interpretation

• 02

  Command interfaces trade visibility for expressive precision

• 03

  Direct manipulation makes state tangible

• 04

  Touch interaction changes the body's role

Worked application: An interface mediates action and interpretation

Key terms

Interface action cycle

An interface mediates action and interpretation — An interface makes parts of a system perceptible and offers actions through controls, language and spatial arrangement. The user forms an expectation, acts, observes system feedback and updates that expectation. Breakdowns occur when the visible representation does not match the underlying state or when available action is hidden. Describe the task in verbs and mark where the user must infer hidden state. Then decide whether visibility, mapping, constraint or feedback is the appropriate repair.

Command-interface trade-offs

Command interfaces trade visibility for expressive precision — Command interfaces let experienced users compose operations precisely and automate sequences, but they demand recall, syntax knowledge and error interpretation. Their efficiency depends on stable grammar, discoverable help and feedback that reveals what the system understood. Observe task frequency, compositional complexity and error consequence. Prototype recovery from an invalid command, not only the successful path, because error language is part of the interface.

Direct manipulation

Direct manipulation makes state tangible — Direct manipulation represents objects and actions in a visible workspace. Incremental operations and immediate feedback shorten the distance between intention and result. The benefit depends on good mapping: movement, handles and constraints should correspond to the user's conceptual model. Test whether users can predict the result before release and undo it afterward. A surprising animation may entertain while weakening control if it conceals the new state.

Interface Lineages and Interaction Paradigms FAQ

Assessment move

Maintain a decision trail for Interface Lineages and Interaction Paradigms. Connect each user observation to a requirement, interface state, prototype change and next test. Begin with action and reconstruct the reasoning without looking at the worked response. Then change one condition in the example and decide whether representation still explains the outcome.

Use the chapter questions to compare direct observation with inference, and write the strongest rival account in full. Before closing the chapter, return to gesture and state the precise boundary it places on transfer. Check that every conclusion names an observable consequence and that uncertainty is attached to the step it affects.

A final retrieval pass should be fast enough to reproduce the method from headings and diagrams while leaving the detailed prose for checking nuance.

IDEA9106 Design Programming · DESN1001 Design Process · INFO5990 Professional Practice