1/30/12  

1  

CS160: User Interface Design Critique and In Class Brainstorm 01/30/12

Berkeley U N I V E R S I T Y O F C A L I F O R N I A

1/30/12  

2  

EECS Colloquium Exploring the Universe with ���Interactive Art San Francisco artist and entrepreneur Scott Snibbe will present selections from twenty years of interactive exhibits, interactive art, and interactive music. He will show many examples of interactive media with technologies including computer vision, haptics, multitouch, and iPads, including recent work creating the first app album with Björk: Biophilia; and the recent interactive exhibits for James Cameron's movie Avatar. He will discuss the educational and societal benefits of interactivity; and the joys, challenges, and research involved in the creation and distribution of interactive media on the cutting edge of interactive technology. 

Wed Feb 1, 4-5pm Soda 306

Sco*  Snibbe  

Due Today (before class) Individual Programming Assignment 1 Individual Design Exercise 1 ���Grades on bSpace soon…

1/30/12  

3  

Group Project Constraints Must make use of Kinect in a non-trivial way

Think about why Kinect provides an appropriate interface��� Target specific users

Target specific applications

Must solve a real-world problem Not simply a game, especially if similar game already exists

Target user group cannot be overly broad College students is too broad a group

Can’t just implement a Media Browser

Groups 20 groups ���4-5 students per group ���You cannot change groups

!

GROUP B Lingbo Zhang lindazhang@berkeley.edu

Ken Yu

kencyu@berkeley.edu

Yuki O'Brien yukiob@berkeley.edu

Sherman Ng shermanlng@berkeley.edu

Alvin Chang alvinchang@berkeley.edu

!

GROUP A Raphael Townshend raphtown@berkeley.edu

Chenkai Gao chenkai@berkeley.edu

Jingwei QI seven.qi@berkeley.edu

Benjamin Coleman benjamin.coleman@berkeley.edu

Shu-Chen Chen joannechen94720@berkeley.edu

!

GROUP C Peter Beardshear pbeardshear@berkeley.edu

Huan Do y0i@berkeley.edu

Kate Greenwood kate_elizabeth@berkeley.edu

Minzhi Zhao zhminzhi@berkeley.edu

Andrew Wun andrewwun@berkeley.edu

GROUP D Lichen Han thisislichen@berkeley.edu

Kaiyuan (Jack) Deng kaiyuandeng@berkeley.edu

Adam Braman glyoko@berkeley.edu

Camilo King camilo@berkeley.edu

Rohan Cribbs rohan.cribbs@berkeley.edu

GROUP E Elena Gasparini

egasparini@berkeley.edu

Danube Phan danubevictoria@berkeley.edu

Rohan Ramakrishnan rohan.ramakrishnan@berkeley.edu

Timothy Zhu timothy.zhu@berkeley.edu

Danny Tan dantan@berkeley.edu

GROUP F Lu Cheng

lu.cheng@berkeley.edu

Victor Kmita vkmita@berkeley.edu

Eugenia Lee eugenialee@berkeley.edu

Jessica Miller jvmiller@berkeley.edu

Huyson Lam huysonlam@berkeley.edu

GROUP G Douglas Treadwell

douglas.treadwell@berkeley.edu

Christopher Nguyen cnguyen13@berkeley.edu

Kenny Shiu k.y.shiu@berkeley.edu

Sylvain Royer s_royer@berkeley.edu

Raj Khare rajkhare@berkeley.edu

GROUP H Lida Wang

l.wang@berkeley.edu

Matthew Leung mleung975@berkeley.edu

Connie Guo connie.guo@berkeley.edu

Bernard Julve bjjulve@berkeley.edu

Can Zhang can.zhang@berkeley.edu

GROUP I Bhavik Singh

bhaviksingh@berkeley.edu

Kenneth Do kennydo@berkeley.edu

Brennan Polley bspolley@berkeley.edu

Samuel Zhu sjzhu@berkeley.edu

Joseph Schadlick joseph_schadlick@berkeley.edu

GROUP J Paige Dunn-Rankin paigedr@berkeley.edu

Dorcas Ashley Hsu ashleyhsu@berkeley.edu

Adib Kashem adibkashem@berkeley.edu

Jessica Chou jessicachou@berkeley.edu

Matthew Chan mac2492@berkeley.edu

GROUP K Pedro Tanaka pedrotanaka@berkeley.edu

Jeffrey Yu

jyu192@berkeley.edu

Sally Lee

slee307@berkeley.edu

Juan Banda Jr juan_banda@berkeley.edu

!GROUP L Benjamin Shapiro

benj@berkeley.edu

Jessica Ho jessicaho@berkeley.edu

JinWoo Roh jinu@berkeley.edu

Kelvin Jie Lam kjlam@berkeley.edu

!GROUP M Neel Rao

raoneel@berkeley.edu

Omar Ali

omarali@berkeley.edu

WenJie Zhou wenjiezhou980434@gmail.com

Brandon Young brandonyoung@berkeley.edu

!GROUP N Michael Greenwald

michael.greenwald@berkeley.edu

Xiaohan Zhang zhangxiaohan@berkeley.edu

Rosette Su su.rosette@berkeley.edu

Jonathan Sulistio jonathansulistio@berkeley.edu

!GROUP O Mark Peng

mahkuh@berkeley.edu

Bei He

beihe@berkeley.edu

Yian Shang yian.shang@berkeley.edu

Eric Mao

eric.mao@berkeley.edu

!GROUP P Sahana Rajasekar

shnraj@berkeley.edu

Robert Marks robert.j.marks@berkeley.edu

Ahmed Afifi aafifi@berkeley.edu

Ritu Kiragi

ritu.kiragi@berkeley.edu

!GROUP Q Jeremy Rios-Martinez jeremy.rios@berkeley.edu

Shuqun Zhang shuqunzhang@berkeley.edu

Arturo Wu-Zhou arturowuzhou90@berkeley.edu

David Squeri dhsqueri@berkeley.edu

!GROUP R Kurtis Freedland

kfreedland@berkeley.edu

Benjamin Le kantas92@berkeley.edu

Jacob Rashoff jacobrashoff@berkeley.edu

Darren Sue aueft@berkeley.edu

!GROUP S Whitney Lai

whitlai@berkeley.edu

Yu Gan

frank_gan@berkeley.edu

Erik Gui

erik.gui@berkeley.edu

Hywel Lo

hywello@berkeley.edu

!GROUP T Praneet Wadge

praneetwadge@berkeley.edu

Tobit Narciso tjnarciso@berkeley.edu

Varad Kishore varad.kishore@berkeley.edu

Tamzid Islam tamzidislam@berkeley.edu

!

CS160 (Spring 2012) Project Groups

1/30/12  

4  

Groups Peer assessment: your group members will evaluate your effort. Your grade can be (significantly) higher or lower than the group average. Take your commitment to your group seriously.

Due Monday Feb 6

Group Brainstorm Today aim for quantity (at least 50)

Later outside of class Select initial course project idea Specific target users ���(not students)

Be creative! If you already can find your ideas in an existing Kinect app, think harder/more specific.

1/30/12  

5  

Due Mon, Feb 13 Individual Programming Assignment 2 Skeleton Tracking Gesture��� Submit: ��� code + video

Example: Public Transit Storyboard

1/30/12  

6  

Critique this storyboard in two ways: 1)  Formally (i.e., how well does the ���

storyboard itself convey the idea) 2)  Content (i.e., critique the application���

idea itself)

Critique How to give & receive constructive criticism

1/30/12  

7  

What is a critique? Show a project in progress through sketches and prototypes Solicit feedback from peers (small groups work best) History: Studio art education h!p://www.flickr.com/photos/pjchmiel/2972140234/

What is the point of a critique? Show off how great your project is.

Get honest reactions, ask for input on open questions.

Q: How is a critique different from a brainstorm?

h!p://www.flickr.com/photos/ crystiancruz/2353909834/

1/30/12  

8  

Designer: Frame the discussion! State Explicitly: What would you like comments on? •  Overall idea? •  Specific interactions? •  Usability? •  Technical Feasibility? •  Pixel-level graphic design?

Take a dispassionate stance (this is hard!) •  Show alternatives where possible ���

(makes comparison easier)

Critic: How to avoid deaf ears Comments are about the design, not the designer. Point out positive aspects – be specific Not: “I like this, but…” Instead: “The layout effectively communicates the��� hierarchical nature of the data. However, …”

Ask for alternatives instead of offering solutions Not: “You should really change X” Instead: “Have you considered alternatives for X?”

1/30/12  

9  

Next Time Task Analysis and Contextual Inquiry Don’t forget! Read, then write a comment on Google Form Group Brainstorm, Due Feb 6 Programming Assignment 2, Due Feb 13

IDEO’s Brainstorming Rules

1.  Sharpen the Focus

2.  Playful Rules

3.  Number your Ideas

4.  Build and Jump

5.  The Space Remembers

6.  Stretch Your Mental Muscles

7.  Get Physical

Aim for quantity Hope for quality