Interaction design IS 403: User Interface Design Shaun Kane.

44
Interaction design IS 403: User Interface Design Shaun Kane

Transcript of Interaction design IS 403: User Interface Design Shaun Kane.

Page 1: Interaction design IS 403: User Interface Design Shaun Kane.

Interaction design

IS 403: User Interface Design

Shaun Kane

Page 2: Interaction design IS 403: User Interface Design Shaun Kane.

Today

• More on interaction design• Getting started with user testing

Page 3: Interaction design IS 403: User Interface Design Shaun Kane.

Check-in on A6

• How is everybody doing?• Problems? Need feedback?

• A7 posted

Page 4: Interaction design IS 403: User Interface Design Shaun Kane.

Interaction design

“Most people make the mistake of thinking design is what it looks like. People think it’s this veneer – that the designers are handed this box and told, ‘Make it look good!’ That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.” – Steve Jobs

Page 5: Interaction design IS 403: User Interface Design Shaun Kane.

What makes a good design?

• What skills have we picked up so far?

Page 6: Interaction design IS 403: User Interface Design Shaun Kane.

What makes a good design?

• Requirements gathering• Good information design and architecture (IS 387)• Good interaction design• Testing, iteration, improvement

Page 7: Interaction design IS 403: User Interface Design Shaun Kane.

Some recap from IS 387

Page 8: Interaction design IS 403: User Interface Design Shaun Kane.

Consider a web site…

What questionsmight a user have?

Page 9: Interaction design IS 403: User Interface Design Shaun Kane.

Consider a web site…

What questionsmight a user have?

Where am I?Where can I go?What can I do here?What did I just do?

Page 10: Interaction design IS 403: User Interface Design Shaun Kane.

Tools from IS 387

• Site ID• Global / persistent navigation• “You are here”• Breadcrumbs

Page 11: Interaction design IS 403: User Interface Design Shaun Kane.
Page 12: Interaction design IS 403: User Interface Design Shaun Kane.

Site ID

• The main site, brand identity• Click to go home

Page 13: Interaction design IS 403: User Interface Design Shaun Kane.

Global navigation

• It should be persistent• 5 elements

Page 14: Interaction design IS 403: User Interface Design Shaun Kane.

Utilities

• Site-wide elements that are not part of the content hierarchy

• Separate them, so we don’t have to shoehorn them into content

Page 15: Interaction design IS 403: User Interface Design Shaun Kane.

“You are here”

• Show user’s position in hierarchy• Helps user understand hierarchy• Can be shown in several ways

Page 16: Interaction design IS 403: User Interface Design Shaun Kane.

BreadcrumbsHierarchical vs. chronological

Page 17: Interaction design IS 403: User Interface Design Shaun Kane.

Buttons and links

• Make them actions

Page 18: Interaction design IS 403: User Interface Design Shaun Kane.

More about interaction design

Page 19: Interaction design IS 403: User Interface Design Shaun Kane.

The holy texts of usability

Page 20: Interaction design IS 403: User Interface Design Shaun Kane.

The holy texts of usability

<- how people think

tools, methods ->processes

Page 21: Interaction design IS 403: User Interface Design Shaun Kane.

Norman

• You’ve probably read it before

• Worth a reread– Now you have fun projects to apply it to

Page 22: Interaction design IS 403: User Interface Design Shaun Kane.

Important ideas from Norman

• It’s not the user’s fault• Affordances• Conceptual models• Make things visible (system status, feedback)• Feedback• Mapping• Constraints

• Next time: execution and evaluating

Page 23: Interaction design IS 403: User Interface Design Shaun Kane.

Affordances

• Examples in everyday life/this class?

Page 24: Interaction design IS 403: User Interface Design Shaun Kane.

Affordances

Jared Sinclair, “Untouchtable”. http://blog.jaredsinclair.com/post/64880801326/untouchable

Page 25: Interaction design IS 403: User Interface Design Shaun Kane.

Perceived vs. actual affordance

Affords sitting Affords pushing Perceived affordance

Page 26: Interaction design IS 403: User Interface Design Shaun Kane.

Affordances vs. convention

• What does this do?

Page 27: Interaction design IS 403: User Interface Design Shaun Kane.

Affordances vs. convention

• What does this do?

• A cultural convention: blue underlined things are web links

Page 28: Interaction design IS 403: User Interface Design Shaun Kane.

Conceptual models

• How the system works vs. how the user thinks it works

• Examples?

Page 29: Interaction design IS 403: User Interface Design Shaun Kane.

Conceptual models

Page 30: Interaction design IS 403: User Interface Design Shaun Kane.

Conceptual models

• Good conceptual models aren’t always the same as the system model

Page 31: Interaction design IS 403: User Interface Design Shaun Kane.

System status and feedback

• What’s going on?• What did I just do?

Page 32: Interaction design IS 403: User Interface Design Shaun Kane.

System status

Page 33: Interaction design IS 403: User Interface Design Shaun Kane.

System status

Good?Bad?

Page 34: Interaction design IS 403: User Interface Design Shaun Kane.

System status

Good?- Tells me I need to wait

Bad?- Why?- How long?- What is it doing?

Page 35: Interaction design IS 403: User Interface Design Shaun Kane.

Feedback

Page 36: Interaction design IS 403: User Interface Design Shaun Kane.

Mapping

• What is it?• What is a good mapping?

Page 37: Interaction design IS 403: User Interface Design Shaun Kane.

Mapping

Page 38: Interaction design IS 403: User Interface Design Shaun Kane.

Mapping

Natural mapping

Arbitrary mapping

Page 39: Interaction design IS 403: User Interface Design Shaun Kane.
Page 40: Interaction design IS 403: User Interface Design Shaun Kane.

Constraints

• What are they?• Good/bad?

Page 41: Interaction design IS 403: User Interface Design Shaun Kane.

Constraints

Page 42: Interaction design IS 403: User Interface Design Shaun Kane.

Don’t do this

Phone number:

Phone number MUST be formatted XXX-YYY-ZZZZ

Page 43: Interaction design IS 403: User Interface Design Shaun Kane.

Class activity

• Take out your phones (no really!)

• In groups of two, find good and bad examples of:– Affordances, mapping, feedback, constraints

Page 44: Interaction design IS 403: User Interface Design Shaun Kane.

Next time

• Norman, model of execution• Usability heuristics (Nielsen)