Page 0: Page 1: user experience, pain-free well, or almost, anyway mostly. amy hoy, http://www.slash7.com Page 2: user experience? or, what the heck are we aiming at? what is Page 3: interface expectations interaction behavior Page 4: interface expectations interaction behavior + user emotions associations integration Page 5: research has shown: when computers “misbehave,” people blame themselves Page 6: when your products help people feel good, that positive feeling rubs off on you research has shown: Page 7: success spectrum or, four key results the Page 8: i love what i can do! it’s so awesome! >< | :| :) :D oh no! feelings! Page 9: I can do everything i need. It’s pretty cool. >< | :| :) :D oh no! feelings! Page 10: It’s ok, I guess. sometimes i have problems. >< | :| :) :D oh no! feelings! Page 11: it makes me feel stupid. I hate it and you. >< | :| :) :D oh no! feelings! Page 12: your goals or, what the heck do you want from your interface? Page 13: repeat business? repeat taskoriented use? advertising / information resource? one-time conversion thing? Page 14: must withstand re-use different experiences for first time and later visits design for recognize & firstreward loyalty repeat timers must not business? help users cripple customize their repeats experience acknowledge that you want a relationship build incentives for them to return Page 15: first and foremost: what’s the focus? make it dead let the user simple. big know what the button. big one-time goal is prices. conversion be honest. thing? keep text be forthcoming. brief. don’t waste anyone’s time give multiple ways to execute the goal Page 16: focus: learnability rather than absolute first time obviousness create a flexible help system don’t hide from your users. the product repeat must grow taskwith the user’s experiece oriented use? plan for chaos be there. let them know you recognize them what are the tasks? must they be in order? Page 17: focus: communication about your product/company you better make it offer crossworth advertising / referencing information reading information what does the user want to know? resource? don’t hide pricing don’t deny you have competitors Page 18: thinking and if you can’t, you’ll just have to learn. or get outside help. like a user Page 19: think the right direction bottom up: list of features technical requirements how long would it take to code? which is easier for me? let’s do ajax! our widget lets the user.... key phrase: Page 20: think the right direction top down: what the user wants what the user doesn’t know he wants, but probably really does how this will affect/improve his/ her life how he thinks it will affect/ improve... etc. our widget helps the user.... key phrase: Page 21: find the focus what does the whole thing revolve around? the calendar date... or the event itself? the to-do item... or who owns it? what you want to talk about... or what your user wants to know? the photo... or what people are saying about it? the movies... or the people behind them? we cannot survive without this... key phrase: Page 22: Page 23: Page 24: Page 25: Page 26: Page 27: scenario: web browser shopping for a new goals: find out what’s out there compare features i care about download Page 28: scenario: web browser shopping for a new goals: find out what’s out there compare features i care about download Page 29: find site does it cost? what browser is it? can I download it? what's the version? is it safe? why should I consider it? will it run on my computer? does it look nice? Page 30: Page 31: Page 32: Page 33: Page 34: aggregating URLs from content (text) files and manipulating them scenario: goals: upload or choose a file select certain URL(s) in file apply a behavior to selected URL(s) Page 35: go to page do I have any already uploaded? which file should I use? how do I choose it? what URLs does it have? have I already used this file? does it even have URLs in it? are they duplicated in the system? can I use that file? can I use it again? have I used them before for anything? Page 36: bottom up way Choose an existing file from a select menu, hit a button Pull content into a textarea Get user to scroll through text area, select a URL and click a button Use Javascript to apply behavior to a URL and encode it into text back in the textarea Page 37: top down way Click an existing file to edit Pull contents into a textarea Use Javascript or server-side language to RegEx out URLs Build list of URLs above textarea with controls next to them Controls reflect whether or not a URL has had a behavior applied already Click the controls to apply or unapply behaviors Page 38: visiting some guy’s tech web site and looking for articles relevant to your non-time-specific problem scenario: goals: locate a web site through a search engine land on a relevant article look for more content by that person about a given topic Page 39: knock-out you didn’t have to be born with a silver paintbrush in one little hand and a tiny beret on your soft baby head visuals Page 40: Page 41: Page 42: typography & spacing it can make or break a design more above than below key phrase: Page 43: color can send messages key phrase: subtlety, repetition, and context Page 44: Page 45: Page 46: Page 47: Page 48: Page 49: consistency it doesn’t happen on its own key phrase: you need to make it look easy Page 50: Page 51: Page 52: Page 53: making it waste as little time as possible happen Page 54: paper prototypes will save your butt key phrase: you have to do it. seriously. Page 55: Page 56: Page 57: resources or, visit my web site for a list of these things so you don’t have to remember them all more Page 58: Books Page 59: Sites & Blogs Creating Passionate Users Kathy Sierra LukeW Interface Designs Luke Wroblewski UsabilityWorks Matthew Oliphant UXD - User eXperience Design Sholom Sandalow, et al UIE - User Interface Engineering Page 60: www.slash7.com Page 61: