Prototyping

Last updated Dec 12, 2021 Edit Source

• Seed

The point is to make ideas real. They are (limited) representations of conceptual designs for users to interact with.

Sketching for interaction design

• save time and money → don’t waste time coding/building the wrong thing
• communication → discuss ideas with stakeholders
• evaluate interface effectiveness for communicating conceptual model
• further develop conceptual and physical design

Identify:

• questions that your prototype(s) need to answer
• requirements you need to address
• users and tasks that your prototype(s) will support

Acquiring mental models

1. Using the system (hands-on learning)
2. Observing others using the system
3. Reading about a system (documentation)

Deciding upon which of the interaction types to use, and why, can help designers formulate a conceptual model before committing to a particular interface

1. Instructing: users issue instructions to a system
2. Conversing: users have a dialog with a system
3. Manipulating: users interact with objects in a virtual or physical space by manipulating them
4. Exploring: users move through a virtual environment or a physical space
5. Responding: system initiates the interaction and the user chooses whether to respond

Fidelity is partly a matter of completeness. As you get more hi-fi it become more close to the actual deployment platform

6 dimensions to fidelity → fidelity is a spectrum. It is complicated to prototype multiple dimensions at once, so don’t!

• visual realism: how real it looks. polish, graphic imagery
• physical realism: shape and form for 3D objects; feel
• scope: how many features/functionalities included; horizontal vs. vertical
• data: operates on real vs. faked data
• autonomy: requires “supervision” vs. operates alone
• platform: interim vs. final implementation

Rough (but flexible) proof-of-concept of interface design. Useful for generating or narrowing down requirements.

Benefits

• cheap/easy to make -> intended to be thrown away
• lack of polish → less intimidating for users (surprisingly important!)
  • avoids nitpick feedback
  • inspires more creative feedback
  • more willingness to criticize

Increasing in completeness and detail

• higher degree of functionality
• higher degree of polish

Vertical prototype:

• includes in-depth functionality for only a few selected features
• key design ideas can be tested in depth

Horizontal prototype

• surface layers only: includes the entire user interface with no underlying functionality
• a simulation; no real work can be performed

Method of testing a system that does not yet exist

• human simulates system’s intelligence and interacts with user
• user
  • uses real or mock interface as expected
  • “Pay no attention to the man behind the curtain”
• “wizard” (sometimes hidden):
  • interprets subject’s input according to a preset algorithm
  • has computer/screen behave in appropriate manner

Possible downside is that the human can over-/under-estimate the quality of the actual technology being simulated.