Interactions Flashcards

1
Q

What is an interaction?

A

Intent + Action + Result

Intent do do something + action to make it happen + a result of action that is successful or unsuccessful.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is a micro-interaction?

A

There is only one intent, action and result involved.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are a product’s elements involved in an interaction?

A

Control + Rule + Feedback

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How does a full interaction play out between a user and the product?

A

Intent > Controls > Action > Rules > Feedback > Results

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are Controls?

A

Objects that allow users to control an object: tabs, radio, checkboxes, buttons, input fields, toggles, ect.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are macro rules?

A

Big rules made up of lots of smaller rules.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are micro rules?

A

Small rules.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What 6 things do rules define?

A
  • How the interface works
  • What it can/can’t do
  • What data is produced and where it goes
  • What happens next
  • Success or failure
  • What feedback is given
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are 3 guidelines your rules should conform to for users (Rules for rules)?

A
  • Must be easy to understand
  • Must be easy to learn
  • Must facilitate the overall flow
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

How do clear rules benefit the product team?

A
  • Everybody knows how it works
  • Reduces guess work
  • Allows developers to focus on development
  • Prevents developers from making design decisions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is Feedback?

A

Communicates what is going on with the software; acts as the polite and helpful voice of the product.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What 3 things does feedback do?

A
  • Confirms an action has taken place
  • Communicates results
  • Tells you what (if anything) you need to do next
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are 4 reasons to wireframe?

A
  • Best for communicating controls, rules and feedback
  • Provides more critical details than prototyping
  • Should be used together wireframe & prototype
  • Not using a wireframe guarantees failure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What 4 things are you doing when you design software?

A
  • Defining how the system behaves
  • How it responds to actions
  • How it communicates results
  • How it helps fulfill intentions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What 3 requirements are needed to be considered a wireframe?

A
  • Needs information that explains each control
  • Outlines rules for each control
  • Defines feedback given each time a control is interacted with successfully and unsuccessfully
How well did you know this?
1
Not at all
2
3
4
5
Perfectly