Practitioners-Guide-User-Experience-Design

Recommendations

Info

you’ve completed is struck through; the color behind it changes briefly from red, which is the background color for active list items, to green; and a check mark briefly appears. When you release your swipe gesture from the screen to complete the action, the phone vibrates and the finished item moves to the bottom of the list and becomes grayed out (so you can still see the items you’ve crossed out). If you cross out an item by mistake, all you have to do is swipe to the left on the now-crossed-out item and it is reinstated (you learn this in the to-do list tutorial, too). The only change I’d be interested in testing would be to make the text read “Swipe me to the right!,” deleting “to complete.” I would add the word me in order to personify the command and create a deeper connection with the user. Ideally we want the dialogue between a system and the person using it to be as rich as those we have in the real world. I would delete “to complete” because I think performing the action makes what it does so obvious that you don’t really need to spell it out. Learnability integrated as content in this way tests well with the users I’ve studied. This may not be an option, though, and if no other alternative than an overlay is available, the lesson from video games can still be applied. Instead of saying everything at once, show users functionality that might be somewhat new or unfamiliar when they express a desire or need for it. For example, if the business I work for wants to educate its employees to become more efficient with their computers by learning keyboard shortcuts, I would write a program that required users to try to find the right shortcut several times within a certain period of time before they would be shown an overlaid tip with the corresponding key command.
THE GIFT OF CONSTRAINTS This chapter has given you a first basic set of guidelines for being responsive to users’ needs in your designs. These guidelines have been focused on the constraints involved with users’ familiarity with the features you’d like to design into your product and with the business’s mandates in terms of time, money, and novelty. But there is another fundamental set of constraints that UX designers should become intimately aware of and learn as much about as they practically can, which are the constraints of the system you’ve got to work with. Back-end systems creators and front-end interface creators can seem to be working in separate worlds. The push and pull between back and front end is endemic in web development. You could say it’s built into the system. But I have found that developing a good understanding of the system I’m designing for and its constraints has not only saved me a great deal of time and frustration, but actually helped me create better designs. That’s the subject we’ll turn to next.
Page 2 and 3: Also from General Assembly The Prac
Page 4 and 5: CONTENTS ALSO FROM GENERAL ASSEMBLY
Page 6 and 7: INTRODUCTION This is a great time t
Page 8 and 9: goals. And one of the most pressing
Page 10 and 11: YOU’RE NOT DESIGNING FOR YOU The
Page 12 and 13: A I think I spoke to it occasionall
Page 14 and 15: a user is through GPS. This app, wh
Page 16 and 17: I responded. “I care!” I tried
Page 18 and 19: WHAT IS UX, EXACTLY? That experienc
Page 20 and 21: GETTING TO KNOW YOUR USERS The prac
Page 22 and 23: content in the iPhone app according
Page 24 and 25: A Little Listening Goes a Long Way
Page 26 and 27: Sending Out Surveys Surveys aren’
Page 28 and 29: WSJ Live iPad app article continuat
Page 30 and 31: DESIGN FOR CORE USER’S NEEDS With
Page 32 and 33: PRIVILEGE THE USER’S TIME It’s
Page 34 and 35: users at the top of their feeds of
Page 38 and 39: Seeing Through Users’ Eyes: POINT
Page 40 and 41: pager, a fax machine, and a persona
Page 42 and 43: advantage of CSS3 to increase respo
Page 44 and 45: UX designers are often not programm
Page 46 and 47: THE NEW SYSTEMS SMORGASBORD These d
Page 48 and 49: A tracing of the Spotify app. Objec
Page 50 and 51: make interactions familiar and acce
Page 52 and 53: AUGMENTED REALITY FOR FINGERNAILS N
Page 54 and 55: Trade-offs Both web and native tech
Page 56 and 57: Top: Desktop navigation module with
Page 58 and 59: Creativity Loves Constraints POINTS
Page 60 and 61: tools for bringing digital products
Page 62 and 63: make decisions with the tools or ut
Page 64 and 65: ehind the weather information. For
Page 66 and 67: GUIDING YOUR EVERY STEP It seems th
Page 68 and 69: DON’T BREAK A STORY’S SPELL Con
Page 70 and 71: personality and storytelling qualit
Page 72 and 73: A rough sketch visualizing an app
Page 74 and 75: User flows of the first time a user
Page 76 and 77: do note if one flow is part of a la
Page 78 and 79: Start with Quick and Dirty Minifram
Page 80 and 81: high-level decisions for the produc
Page 82 and 83: Full wireframe for a video website
Page 84 and 85: MAKING A DESIGN MOVE Prototyping is
Page 86 and 87:
ig improvements over these others t
Page 88 and 89:
STAKEHOLDERS AND THE SIXTH FINGER A
Page 90 and 91:
A PICTURE IS WORTH A THOUSAND WORDS
Page 92 and 93:
HOW DO YOU TELL SOMEONE THEY’VE M
Page 94 and 95:
Chapter 4 INNOVATION IS NOT FOR INN
Page 96 and 97:
TAKING WORK AWAY One of the few rel
Page 98 and 99:
BUSINESS GOALS WILL OFTEN OVERSHADO
Page 100 and 101:
A SMALLER USER BASE TENDS TO MAKE I
Page 102 and 103:
SOMETIMES IT’S BETTER TO ASK FORG
Page 104 and 105:
and open to changing or abandoning
Page 106 and 107:
of twenty TV stations, shows, and g
Page 108 and 109:
GRAB PEOPLE IN THE HALLWAY During m
Page 110 and 111:
CLARIFYING YOUR PRIORITIES The resu
Page 112 and 113:
TESTING THE COMPETITION Another gre
Page 114 and 115:
RELEASE, FIX, RELEASE There is one
Page 116 and 117:
Chapter 5 GOOD UX COMES FROM BEING
Page 118 and 119:
YOU’RE NOT THE OWNER OF THE UX In
Page 120 and 121:
course, this is just not the way th
Page 122 and 123:
(Courtesy Shutterstock) Well, sure,
Page 124 and 125:
pieces of images peeking out from t
Page 126 and 127:
knowledge that data can have about
Page 128 and 129:
Frequency vs. Importance: Give a se
Page 130 and 131:
COLLABORATION GOES BOTH WAYS Always
Page 132 and 133:
MAKING IT LEAN Fitting the parts of
Page 134 and 135:
SEEK INSPIRATION EVERYWHERE Just as
Page 136 and 137:
screen maps that show where gates a
Page 138 and 139:
SHOW, DON’T TELL In the beginning
Page 140 and 141:
POINTS TO REMEMBER Good UX Comes fr
Page 142 and 143:
November 16, 2012, http://managemen
Page 144 and 145:
Bulwer-Lytton, Edward, 78 business
Page 146 and 147:
size of user base and, 121-22 user
Page 148 and 149:
Qu, Hong, 158 Rams, Dieter, 117-18
Page 150 and 151:
UX design, 1-4, 62, 19, 33, 148, 16
show all

Practitioners-Guide-User-Experience-Design

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?