Chapter 14
After taking so many cognitive science classes, it seems to me that usability testing could be abandoned, and evaluation would depend more on field studies. Usability testing doesn't seem like it would provide much information in addition to field studies. People are rarely going to be using a product in a controlled environment, so testing in one wouldn't have much use, other than possibly identifying MAJOR problems with a design, but those problems would probably be discovered in the field study anyway.
I got a kick out of reading about the Tracksys 'lab-in-a-box'. I think it's amusing that something was designed specifically for studying the study of design. Then again, designers and researchers are people too, and I'm sure having all their tools in one easy (hopefully?) to use box is nice. From the look of it, maybe the Tracksys could undergo a redesign, as it's beginning to look a bit dated.
I like the example the book used, MedlinePlus, to serve as a basis for usability testing and field studies. Mainly due to the fact that it's a large website, and the redesign would impact a large number of people. So seeing real application on a large scale in the real world was appreciated.
Chapter 15
Analytical evaluation almost seems silly to me, because as the introduction says, the researcher is role-playing as the user. If products are designed with the user in mind, shouldn't the user be the one to evaluate whether or not s/he likes the interface? However, I guess I can see a couple advantages to this approach. The first one being that it's simply more testing. If designers can predict what the user may or may not like before the product is given to the user, maybe they can make evaluations simpler for the user. More importantly though, I don't think users always know what they like or don't like, but more importantly, the user may not be able to aptly convey that (such as why or how). By having an expert posing as a user, the expert will be more easily able to determine what makes the interface good or bad, and be able to explain why, so that it can be fixed.
I did enjoy reading about the REI website, and thinking about it analytically. Mainly due to the fact I'd been to the website before, so it was neat to see it in the book, and think about its redesign :)
I also liked reading about Fitts' Law, because I never knew that such an idea existed, but now after having read about it, and looking at buttons on various things, it does hold up. It's interesting looking at its application on various things (and whether designers actually took it into account when designing a product, or the face that the law holds is just a coincidence).
Lecture
If there's any topic I really enjoyed in this class, it was ubiquitous computing. I really do think that computers are eventually going to be anywhere and everywhere (even more so than they are now), and it's also inevitable. In my opinion, this is a great thing. I really enjoy technology and computers, and I think they make life much easier and much more enjoyable. The idea that one day they're really going to... permeate life is awesome. Definitely not anything like the Borg, but just being able to have a supercomputer always at hand.
I also really liked being able to see some of the more cutting edge research going on, and also being able to see where to go to do some more research on my own.
I know, it's nerdy, but technology is exciting.
Sunday, December 9, 2007
Sunday, December 2, 2007
Week 9
Chapter 10
The first thing I really liked about chapter was the picture on pg. 475, because I think that's how design for users' needs really does happen 95% of the time. If determining good design wasn't so difficult, then so much research and analysis wouldn't currently be going into it. I think the requirements phase is probably one of the most difficult phases of design, because most of the time the customer doesn't even know what THEY want. So trying to explain what they want to a designer can be very frustrating. Sometimes they do know what they want, but they do a poor job of conveying that, and end up with a product that isn't what they had imagined.
I liked that this chapter also had many real world examples. I find it much more useful to see techniques already discussed being applied somewhere, rather than reading something that's as dry as stereo instructions. For example, reading about the task descriptions or the Web Fun Central, were actually interesting because they apply to something a little more concrete.
Chapter 11
I think that prototyping is probably the most enjoyable part of design; especially after watching the video in IDEO in class several weeks ago. This is probably so, because prototyping involves the most amount of imagination and creativity. Being able to brainstorm with a group of people, then design some of those ideas just sounds... fun! Not to mention while trying to design one thing, you may end up designing something entirely different than what was planned, but can be extremely useful somewhere. It's also good to see work going into making prototypes of new interfaces for systems already in place, such as the eSpace project.
It was also interesting to read about the tool support, such as DENIM. I think an entire chapter should be devoted to tools used by designers to make their jobs easier. Not only that thought, I just enjoy reading about new programs I haven't heard about before. Who knows, maybe I could use one of the programs for something entirely different than what IT was designed for, such as Thoughtless Acts.
Chapter 12
After reading chapter 12, evaluation sounds like it would be a fun part of design as well. Hearing about why users did or didn't like your product will help you in future designs, as well as possibly understanding more about what users like and dislike when it comes to interfaces. Additionally, after some field work has been done, and the prototype has been evaluated by users, the prototype may need to be redesigned, which leads us back to the fun stuff!
Chapter 13
This was a rather short chapter, which really just wrapped up the basics of interaction design using the DECIDE framework. I suppose it was nice of the authors to provide us with an easy to remember acronym for working on a design project, even if it is overly simplified.
It really seems like the past few chapters have had largely redundant information. For example, chapter 10 had a large amount of data analysis, interpretation, and presentation information, even though an earlier chapter was already covered much of that. Also, chapter 13 provided the DECIDE framework, which is just a simple acronym for everything covered in previous chapters (although I think it was the first time informed consent and ethics were discussed).
Overall I think the book has been interesting, but the past... 5 or so chapters could have been mostly eliminated. The new information in each of those chapters could simply be inserted into their respective chapters.
Class Discussion
I really enjoyed Tuesday's lecture, specifically the mention of Spore and Will Wright. I've been following Spore for some time now, and think it's not only going to be a great game, but also a great leap in interaction design (just as his previous games, such as The Sims, have been). I also enjoy listening to Will's speeches, because he's such an intuitive and inspiring person. He's the kind of person that makes others really think and do. Also, I'd never heard of TED, and after browsing their website they're something else to keep an eye on.
Listening to Professor Hollan discuss Beyond Being There was also interesting, but I have to admit, in my opinion I don't think any sort of interface will ever be able to replicate (or even improve on) face-to-face interaction. There's something about actually being next to a person you're talking to that I don't think can be reproduced by any interface.
The guest lecturer on Thursday was also intriguing, because everyone loves music, and mixing music with new technology and interfaces can only make both of them better (or so I think).
The first thing I really liked about chapter was the picture on pg. 475, because I think that's how design for users' needs really does happen 95% of the time. If determining good design wasn't so difficult, then so much research and analysis wouldn't currently be going into it. I think the requirements phase is probably one of the most difficult phases of design, because most of the time the customer doesn't even know what THEY want. So trying to explain what they want to a designer can be very frustrating. Sometimes they do know what they want, but they do a poor job of conveying that, and end up with a product that isn't what they had imagined.
I liked that this chapter also had many real world examples. I find it much more useful to see techniques already discussed being applied somewhere, rather than reading something that's as dry as stereo instructions. For example, reading about the task descriptions or the Web Fun Central, were actually interesting because they apply to something a little more concrete.
Chapter 11
I think that prototyping is probably the most enjoyable part of design; especially after watching the video in IDEO in class several weeks ago. This is probably so, because prototyping involves the most amount of imagination and creativity. Being able to brainstorm with a group of people, then design some of those ideas just sounds... fun! Not to mention while trying to design one thing, you may end up designing something entirely different than what was planned, but can be extremely useful somewhere. It's also good to see work going into making prototypes of new interfaces for systems already in place, such as the eSpace project.
It was also interesting to read about the tool support, such as DENIM. I think an entire chapter should be devoted to tools used by designers to make their jobs easier. Not only that thought, I just enjoy reading about new programs I haven't heard about before. Who knows, maybe I could use one of the programs for something entirely different than what IT was designed for, such as Thoughtless Acts.
Chapter 12
After reading chapter 12, evaluation sounds like it would be a fun part of design as well. Hearing about why users did or didn't like your product will help you in future designs, as well as possibly understanding more about what users like and dislike when it comes to interfaces. Additionally, after some field work has been done, and the prototype has been evaluated by users, the prototype may need to be redesigned, which leads us back to the fun stuff!
Chapter 13
This was a rather short chapter, which really just wrapped up the basics of interaction design using the DECIDE framework. I suppose it was nice of the authors to provide us with an easy to remember acronym for working on a design project, even if it is overly simplified.
It really seems like the past few chapters have had largely redundant information. For example, chapter 10 had a large amount of data analysis, interpretation, and presentation information, even though an earlier chapter was already covered much of that. Also, chapter 13 provided the DECIDE framework, which is just a simple acronym for everything covered in previous chapters (although I think it was the first time informed consent and ethics were discussed).
Overall I think the book has been interesting, but the past... 5 or so chapters could have been mostly eliminated. The new information in each of those chapters could simply be inserted into their respective chapters.
Class Discussion
I really enjoyed Tuesday's lecture, specifically the mention of Spore and Will Wright. I've been following Spore for some time now, and think it's not only going to be a great game, but also a great leap in interaction design (just as his previous games, such as The Sims, have been). I also enjoy listening to Will's speeches, because he's such an intuitive and inspiring person. He's the kind of person that makes others really think and do. Also, I'd never heard of TED, and after browsing their website they're something else to keep an eye on.
Listening to Professor Hollan discuss Beyond Being There was also interesting, but I have to admit, in my opinion I don't think any sort of interface will ever be able to replicate (or even improve on) face-to-face interaction. There's something about actually being next to a person you're talking to that I don't think can be reproduced by any interface.
The guest lecturer on Thursday was also intriguing, because everyone loves music, and mixing music with new technology and interfaces can only make both of them better (or so I think).
Sunday, November 18, 2007
Week 7
Chapter 8
In my opinion, most of chapter 8 should be omitted from the book. Although, that's a heavily biased opinion. I've already taken statistics and many cognitive science courses, so I've heard data analysis techniques many times over. What I haven't heard about before are the theories, like the grounded theory or active theory. I had heard of distributed cognition before. It was interesting reading about them, as they were something practical that data analysis could be applied to - something more than just pouring over qualitative and quantitative data.
Something else I found interesting were the examples used in the book, such as the MMORPG example. It's interesting to read about other people's findings, and to see the book use what they're teaching in a real world application.
A section I thought they could have made longer is the one where they mentioned tools to support data analysis. There are many tools out there, and to only cover a few of them seems like a shame.
Chapter 9
Chapter 9 really just seemed like a recap of everything that was discussed in the previous eight chapters. Only instead of discussing each part of interaction design in detail, the authors brought all of the previous ideas together into one big idea of how interaction design actually takes place. I suppose it's useful to see the bigger picture, although the chapter does seem a big redundant already having seen all of the finer details previously. What was useful were the new models that were discussed, and also seeing the practical applications of interaction design, such as the Microsoft XP example.
In-Class Discussions
Chumby is awesome! Except for the pricetag...
This week's technology overview was very interesting. Probably due to the fact that I had seen a lot of it before, and was already interested in it (the wii remote, chumby, having a tablet pc myself, etc). What was really interesting was SOAP. I'm actually considering building one when I get the chance. They're inexpensive, and look like a lot of fun to use. Plus, having a mouse you can use as a "pointer" from almost anywhere is awesome.
Assignment 2
For Assignment 2 we decided to do the self-checkout lanes at the Ralphs in La Jolla.
Assignment 2 turned out very well, considering there are only two of us in the group. The other members dropped after the midterm, and the students that Professor Hollan emailed about not having a group seemed uninterested in joining, so we were rather stuck. However, it turned out for the better, because it created plenty of brain-storming time for the two of us.
As far as specific contributions, I interviewed two of the four people used in our project. The two of us also spent a significant amount of time meeting out of class, and exchanging emails full of ideas - so many of the ideas developed in our project were a joint effort. However, one of the design improvements in the project was mine, which I thought was rather clever. All in all it was a very joint effort, from deciding on what we were going to examine, to conducting interviews, to examining data, and to brainstorming over design issues. The actual essay almost wrote itself near the end.
In my opinion, most of chapter 8 should be omitted from the book. Although, that's a heavily biased opinion. I've already taken statistics and many cognitive science courses, so I've heard data analysis techniques many times over. What I haven't heard about before are the theories, like the grounded theory or active theory. I had heard of distributed cognition before. It was interesting reading about them, as they were something practical that data analysis could be applied to - something more than just pouring over qualitative and quantitative data.
Something else I found interesting were the examples used in the book, such as the MMORPG example. It's interesting to read about other people's findings, and to see the book use what they're teaching in a real world application.
A section I thought they could have made longer is the one where they mentioned tools to support data analysis. There are many tools out there, and to only cover a few of them seems like a shame.
Chapter 9
Chapter 9 really just seemed like a recap of everything that was discussed in the previous eight chapters. Only instead of discussing each part of interaction design in detail, the authors brought all of the previous ideas together into one big idea of how interaction design actually takes place. I suppose it's useful to see the bigger picture, although the chapter does seem a big redundant already having seen all of the finer details previously. What was useful were the new models that were discussed, and also seeing the practical applications of interaction design, such as the Microsoft XP example.
In-Class Discussions
Chumby is awesome! Except for the pricetag...
This week's technology overview was very interesting. Probably due to the fact that I had seen a lot of it before, and was already interested in it (the wii remote, chumby, having a tablet pc myself, etc). What was really interesting was SOAP. I'm actually considering building one when I get the chance. They're inexpensive, and look like a lot of fun to use. Plus, having a mouse you can use as a "pointer" from almost anywhere is awesome.
Assignment 2
For Assignment 2 we decided to do the self-checkout lanes at the Ralphs in La Jolla.
Assignment 2 turned out very well, considering there are only two of us in the group. The other members dropped after the midterm, and the students that Professor Hollan emailed about not having a group seemed uninterested in joining, so we were rather stuck. However, it turned out for the better, because it created plenty of brain-storming time for the two of us.
As far as specific contributions, I interviewed two of the four people used in our project. The two of us also spent a significant amount of time meeting out of class, and exchanging emails full of ideas - so many of the ideas developed in our project were a joint effort. However, one of the design improvements in the project was mine, which I thought was rather clever. All in all it was a very joint effort, from deciding on what we were going to examine, to conducting interviews, to examining data, and to brainstorming over design issues. The actual essay almost wrote itself near the end.
Friday, November 9, 2007
Week 6
Chapter 7
This chapter provided some useful information in getting the Assignment 2 wheels churning. It helped to see some sample questions, how to design them, and what types of questions to avoid.
I think most importantly it showed how many types of interviews there are, and how many ways those interviews can be conducted. The interview type to be used is dependant on what the interview situation is going to be like. However, I think using multiple methods is probably always the best idea. For example, doing audio recording and writing, or video taping and writing, etc etc. The more ways information is recorded, the more likely nothing is going to be missed. I also think that questionnaires would be highly useful in many situations. It would allow the interviewee some additional comments that may have not been covered in the interview. It would also ease some of the cognitive strain on the interviewer by not having to worry about forgetting important questions.
As an interesting thought in regards to the book's design, I wonder which is better - Presenting all the information on interaction design in chapters 1-6 first, as an introduction to how to conduct interviews, or presenting interview techniques first, so readers can think about them while learning about interaction design. I think that learning about interviews first would be more beneficial... But that's just my opinion.
Update on Assignment 2
We had a solid group, but it's inevitable that people drop after a midterm, and our group kinda fell apart. We're trying to find new members at the moment. On the bright side, before the midterm the group was able to meet several times, and came up with a pretty solid idea for the assignment, along with some preliminary questions to ask interviewees. I think we're pretty ahead of the game thus far. We have a solid idea and some ideas for interviewing already - things seem to be coming together nicely.
This chapter provided some useful information in getting the Assignment 2 wheels churning. It helped to see some sample questions, how to design them, and what types of questions to avoid.
I think most importantly it showed how many types of interviews there are, and how many ways those interviews can be conducted. The interview type to be used is dependant on what the interview situation is going to be like. However, I think using multiple methods is probably always the best idea. For example, doing audio recording and writing, or video taping and writing, etc etc. The more ways information is recorded, the more likely nothing is going to be missed. I also think that questionnaires would be highly useful in many situations. It would allow the interviewee some additional comments that may have not been covered in the interview. It would also ease some of the cognitive strain on the interviewer by not having to worry about forgetting important questions.
As an interesting thought in regards to the book's design, I wonder which is better - Presenting all the information on interaction design in chapters 1-6 first, as an introduction to how to conduct interviews, or presenting interview techniques first, so readers can think about them while learning about interaction design. I think that learning about interviews first would be more beneficial... But that's just my opinion.
Update on Assignment 2
We had a solid group, but it's inevitable that people drop after a midterm, and our group kinda fell apart. We're trying to find new members at the moment. On the bright side, before the midterm the group was able to meet several times, and came up with a pretty solid idea for the assignment, along with some preliminary questions to ask interviewees. I think we're pretty ahead of the game thus far. We have a solid idea and some ideas for interviewing already - things seem to be coming together nicely.
Sunday, November 4, 2007
Week 5
No readings this week. Midterm review was on Tuesday and midterm was on Thursday.
So far Assignment 2 is coming along nicely. Our group already has an idea of what we want to do, and already coming up ideas of how to go about running interviews and collecting data.
So far Assignment 2 is coming along nicely. Our group already has an idea of what we want to do, and already coming up ideas of how to go about running interviews and collecting data.
Sunday, October 21, 2007
Week 3
Chapter 5
I think reading chapter 5 before doing the Hall of Shame/Fame nomination would have been very useful. Then again, reading the entire book before doing the essay probably would have been very useful. Chapter 5 discusses "affective behavior," and how it's becoming more important in the field of interaction design. If people don't feel good while using a well designed interface, then the fact that it is a well designed may not matter - people won't use it because they don't enjoy using it. Conversely, if people enjoy using an interface, they're more likely to continue using it.
Out of the three models of affective aspects, I think that the pleasure model is probably the most important. While it doesn't describe affectiveness biologically, I don't think it's necessarily important in interaction design. It's certainly interesting what is going on biologically, but perhaps the best way to gauge whether someone likes in interface is to have them use it and provide feedback - not have them sit in an MRI while using the interface. The pleasure model does however take into account four types of pleasure, which are all important for affectiveness.
In regards to anthropomorphism, my opinion is that computers are presently better off being limited in how they use human-like reactions. Unless of course there comes a time in the near future where computers can mimic humans so well that the difference is almost indiscernible (although I highly doubt this will happen, as there are many problems with A.I.). As for right now, I haven't seen one anthropomorphic application that I enjoyed using. Usually they're just very irritating, and I'd rather a computer's messages be short. However, with that being said, anthropomorphism is never going to get a an indiscernible point unless people continue to make better applications out of the many failures.
An interesting question I found to be unanswered, which do humans prefer: a fantastically designed interface that really irritates people when using it, or a poorly designed interface that people love using (if such scenarios can be devised)?
Chapter 6
Chapter 6 is a descriptive, although not exhaustive, list of many types of interfaces and the evolution of them - starting in the 1980s and moving through the 2000s. It's obvious that interfaces have come a long way in their design, but it's also obvious that they have much farther to go. I find the newest forms of interaction, such as tangible, shareable, and multimodal interfaces to be the most interesting. I'm sure this is probably because they are the most original ideas in a while. The 1980s and much of the 1990s all consisted of the same things, such as WIMPs. Instead of creating something new, designers only improved on old ideas. Not that I think there is anything wrong with this, in fact I think it's primarily how new ideas, such as tangible interfaces, are born. The newer interfaces are nice simply because they're something fresh.
The book makes mention in the 'augmented and mixed reality interfaces' section about an augmented map that shows flooded areas at high water areas, and what evacuation might look like during a flood. With the fires burning in L.A. and Ramona today it would be interesting to see an application developed for a similar use. I think it would also be worthwhile to design a new interface to get information to people more quickly and efficiently in case of future disasters. It's unfortunate things have to get out of hand before a solution arises.
I also agree with the conclusion of the chapter. Many of the interfaces being researched today are very interesting, but the implementation of them will depend on the situation in which they are used. I'm sure some interfaces will generally work the best as a command line, and some may eventually work the best as a robotic design. However, I think for the most part a mix of several interfaces will always yield the best result. For example, present an interface that includes command line processing and a choice of icons. Multimodal and multimedia presentations present far better options than sticking to just one interface.
I think reading chapter 5 before doing the Hall of Shame/Fame nomination would have been very useful. Then again, reading the entire book before doing the essay probably would have been very useful. Chapter 5 discusses "affective behavior," and how it's becoming more important in the field of interaction design. If people don't feel good while using a well designed interface, then the fact that it is a well designed may not matter - people won't use it because they don't enjoy using it. Conversely, if people enjoy using an interface, they're more likely to continue using it.
Out of the three models of affective aspects, I think that the pleasure model is probably the most important. While it doesn't describe affectiveness biologically, I don't think it's necessarily important in interaction design. It's certainly interesting what is going on biologically, but perhaps the best way to gauge whether someone likes in interface is to have them use it and provide feedback - not have them sit in an MRI while using the interface. The pleasure model does however take into account four types of pleasure, which are all important for affectiveness.
In regards to anthropomorphism, my opinion is that computers are presently better off being limited in how they use human-like reactions. Unless of course there comes a time in the near future where computers can mimic humans so well that the difference is almost indiscernible (although I highly doubt this will happen, as there are many problems with A.I.). As for right now, I haven't seen one anthropomorphic application that I enjoyed using. Usually they're just very irritating, and I'd rather a computer's messages be short. However, with that being said, anthropomorphism is never going to get a an indiscernible point unless people continue to make better applications out of the many failures.
An interesting question I found to be unanswered, which do humans prefer: a fantastically designed interface that really irritates people when using it, or a poorly designed interface that people love using (if such scenarios can be devised)?
Chapter 6
Chapter 6 is a descriptive, although not exhaustive, list of many types of interfaces and the evolution of them - starting in the 1980s and moving through the 2000s. It's obvious that interfaces have come a long way in their design, but it's also obvious that they have much farther to go. I find the newest forms of interaction, such as tangible, shareable, and multimodal interfaces to be the most interesting. I'm sure this is probably because they are the most original ideas in a while. The 1980s and much of the 1990s all consisted of the same things, such as WIMPs. Instead of creating something new, designers only improved on old ideas. Not that I think there is anything wrong with this, in fact I think it's primarily how new ideas, such as tangible interfaces, are born. The newer interfaces are nice simply because they're something fresh.
The book makes mention in the 'augmented and mixed reality interfaces' section about an augmented map that shows flooded areas at high water areas, and what evacuation might look like during a flood. With the fires burning in L.A. and Ramona today it would be interesting to see an application developed for a similar use. I think it would also be worthwhile to design a new interface to get information to people more quickly and efficiently in case of future disasters. It's unfortunate things have to get out of hand before a solution arises.
I also agree with the conclusion of the chapter. Many of the interfaces being researched today are very interesting, but the implementation of them will depend on the situation in which they are used. I'm sure some interfaces will generally work the best as a command line, and some may eventually work the best as a robotic design. However, I think for the most part a mix of several interfaces will always yield the best result. For example, present an interface that includes command line processing and a choice of icons. Multimodal and multimedia presentations present far better options than sticking to just one interface.
Monday, October 15, 2007
Steam - Hall of Fame
Many people enjoy playing video games; a portion of which play on personal computers. With so many games, and other computer applications, available today, it becomes difficult to keep track of them all. This is what a once small company, Valve, noticed a few years ago. At the beginning, they were solely a game developing company but a few years ago they expanded their application horizon and developed Steam. Since its creation, it has changed significantly. Now people can manage all of their gaming and most of their other software content through Stream. Nearly any software application can be integrated into Steam, thus increasing the user community. However, most people still use it for Valve developed games. Everything else is just a perk. Aside from just keeping track of all games, it also lets your purchase new games through an online store. Also available is a “Friends List” option, which lets you add to a list of people you meet while gaming. Users can either chat with these friends, or join a game that the friend is playing in. Steam allows various other functionalities but these are the things that really appeal to its user community. 
Among what Steam offers is a great user interface. As Steam has been continually updated and developed by Valve, it clearly shows a lot of thought has gone into its design. It is easy to use, easy to learn to use, aesthetically pleasing, and its application toward gaming is very flexible. This does not mean that it is perfect, as there are a few things that could be improved. Most of this paper is going to concentrate on one aspect of the Steam interface, although several others also get mention. Overall, it well deserves a nomination to the Hall of Fame.
The first thing to notice is the logon screen. It is very simplistic and consistent with many other logon screens – making it more familiar to users. All a users needs to input is a username and password. There is also an option to save the password, so users don’t need to be burdened with entering their password each time; usernames are automatically saved. This is beneficial for users because they already have to remember so many usernames and passwords for other programs. Users can only remember so much information. Incase of a lost username and/or password, the option to recover them is available. Users can also create a new account if they do not already have one. All of these options are similar to other logon screens, making it familiar to users. The way the buttons are laid out also makes things easy on the user, as they are clearly marked, and areas are not overcrowded. Also included is error prevention and feedback. If a user logs in by mistake they have the option to cancel the login process. If the user enters a username that does not exist or an incorrect password, they are prompted with a message indicating so. The only poorly designed thing about this, is that if the user is entering a username they think to be correct, the error message only responds saying “that username may not exist.” To be more useful to the user, the message should indicate whether or not the username really does exist or not.
Another simplistic and consistent part is the Windows system tray icon, which is always displayed. Aside from being familiar to users, it also provides feedback to the user about Steam’s current status. If the user’s internet connection goes down the tray icon turns from a white box into a white box with a red X in it, to indicate loss of connection. This not only provides the user with information about Steam but also provides useful information that the internet is down in general. However, in the event that the internet is up, and everything is working correctly, a right click on the icon brings up a menu with several options. The option most important for Hall of Fame nomination is “Games.”
The “My games” section is perhaps the best designed part of Steam. As depicted in the picture above it comes first on the tray icon list, as it is probably the more frequently used. This is helpful to the user because they do not have to scan a list of items – they need only to glance at the top one. Once in the “My games” section, there are many things a user can choose to do. To make things easy on the user Steam has everything labeled, and has applications categorized so they can be easily recognized. This not only makes Steam aesthetically pleasing but allows for cognitive offloading because users do not have to remember where everything is. They can simply glance at the interface, and easily determine what they want to know. It also makes for much less memorization by the user because everything is labeled and has a natural feel. With only a few glances the interface is comfortably recognizable.
As mentioned previously, every application is categorized. They categories are: installed, not installed, and favorites. The applications in categories are alphabetically listed, which makes searching for them much easier. Each category is also collapsible, so users do not have to sift through a large numbers of applications. They can simply go to which category they want and then the application name. To make it even easier, users can add games to their favorites list, which puts them in a separate category located at the top of the Steam interface. This is much like the real world – people tend to keep things they use often in the most easily accessible area.
Moving applications into a favorite category is not the only control and freedom Steam offers users. Users can do almost anything they want regarding games and applications. They can install or uninstall anything, activate products not purchased through the online stores, create desktop shortcuts for games, view help and documentation about specific games - the list goes on and on. Unfortunately the interface itself is not customizable but it would be unwise to change anything anyway. Everything is designed well already, including if a user happens to make an error while customizing their application needs. It is difficult to get lost in a loop of errors within Steam. Almost every button press presents a conformation window, or with other important information about what might happen. Some may think this would get irritating after a while, but it is far better than having no error protection whatsoever.
While on the subject of errors, there are some Valve should fix regarding the few poor design flaws Steam does have. The first of which, is that no help or documentation is available to the user when the internet connection is down. Applications can still be used, but there is no documentation incase something unexpected might happen within Steam, or if the user needs help figuring something out. However, considering Steam is rather intuitive for new users, this is only a minor problem. A more important design flaw has to do with the “My games” section. Consider a user with five-hundred applications installed. Although applications are categorized and alphabetized, searching for a specific one could take some time for the user. By implementing a search function, such as Apple’s Spotlight, this could be fixed.
In conclusion, I believe that Steam is well worthy of admittance to the Hall of Fame for its interface design. It seems obvious that much thought has been put into it to make the users’ experience as enjoyable and as painless as possible. Out of the things that could be improved for the interface, none of them are that significant and could probably be easily fixed. Overall it is a very solid design, well worth entry into the Hall of Fame.
Thursday, October 11, 2007
Week Two
Chapter 3
Chapter 3 began to make it apparent how poorly designed many interfaces are. Even though many interfaces are poorly designed, I think it would be difficult to hold anyone really accountable for it - unless the design is just blatantly bad. I say this because interaction design is a relatively new field; just as cognitive science. In my opinion, this chapter shows that it's really not known what's exactly going on in the mind/brain. We have a pretty good understanding of what we think is going on, and plenty of great theories that are probably correct, but plenty of things aren't complete fact yet. Most importantly, we don't know why something is happening, or why some design looks better than another. Otherwise there wouldn’t be so many models and theories of cognition – many of which are mentioned in this chapter. So if the brain hasn’t been figured out yet, how can we expect someone who doesn't understand the mind/brain to design something that will appeal to it?
It’s interesting that the most important part of cognition in regards to interaction design is memory. While memory is important, it seems to me that attention, perception, learnability, and many other factors are just as important. Although, I suppose it does depend on how information is presented. The phone example in the chapter does make a strong argument for memory being very important, however the Google and Apple’s Spotlight search tool make a strong argument that attention and perception are important. The difference between the phone and Google is that one is spoken and the other is graphical. I think I would argue that all aspects of cognition are equally important in regards to interaction design, although it largely depends on the situation in which the information was presented.
The wide array of theories of cognition are also interesting, considering they range from the theory of action to distributed cognition. ie: Things happen sequentially in the brain, or things happen across a larger cognitive unit.
Chapter 4Chapter 4 discusses communication and collaboration, and outlines just how important it is to society. It seems that distributed cognition should have also been integrated into this chapter, as it can be applied as a theory to most of the topics covered.
After reading the chapter I think there is a long way to go with electronic and technological mediums in communication. Things like electronic whiteboards, videophones, and BiReality may all be impressive communication and collaboration ideas, the authors make them out to be inadequate. However, that being said, the authors also discuss how face-to-face and telephone communication can be just as difficult.
What really intrigues me is how much people communicate indirectly; without even really knowing they are. The book provides examples, such as leaving an office door open to indicate you can be approached, or how a person might stare at their watch to indicate they need to leave a conversation. It would be interesting to give people some sort of feedback mechanism, that would show them all of their own mannerisms. Then to see how the people would react, and possibly even change how they act and respond to similar situations.
Communication breakdown and its repair mechanisms are also interesting. I think the most interesting part is what causes them. Why is it that some information may not be recalled, even though it's clear that someone knows what they're talking about? Or why is it easier to recognize something, and put a name to it, than try to recall something outright? It's fascinating how someone can quickly repair a hiccup in the conversation, without it causing any sort of disruption. Generally the problem is remedied quickly, and the conversation just continues as if nothing had happened.
In summation, people are always going to need to communicate and collaborate on many different things. The farther technology comes, and the more interaction design helps it, the easier it's going to be on people to do these things. Since communication and collaboration are inherent human traits, the more help they can get while performing them, the better they're going to be.
Sunday, October 7, 2007
Week One
While browsing through various internet websites today, I came across Perceptive Pixel’s Interactive Media Wall, which was presented in class by Professor Hollan. Apparently the Wall is going to be available for purchase through Nieman Marcus for around $100,000. (http://www.engadget.com/2007/10/07/nieman-marcus-to-sell-perceptive-pixels-interactive-media-wall/). It’s nice to see that some of the neat, new technology is finally becoming purchasable (albeit very expensive). Hopefully in the next several years the same technology will be about 1/10 of the cost (Microsoft Surface, also presented in class: http://www.engadget.com/2007/05/31/microsoft-surface-hands-on/). It’s unfortunate that so many great gadgets are still prototypes and/or very expensive, and won’t be available for many years to come.
Reading chapter 1 of Interaction Design provided a great overview of what HCI and interaction design in. I thought that human-computer interface was a self-explanatory term, but apparently I was wrong. I had no idea how much effort is currently going into interaction design, and that companies are beginning to take such an interest in it. I also had no idea that there are so many professional fields that participate in interaction design. It takes a little help from a diverse array of knowledge to create something “user friendly.”
The way the authors laid out specific parts of what comprises interaction design really helped in understanding it. In my opinion, even the explanations of design principals and usability goals incorporated interaction design. For example: “effectiveness,” “efficiency,” and “safety” all provide an easy understanding of what each term means.
The interview at the end of the chapter was also interesting. With companies like Swim Interaction Design Studio emerging, corporations may no longer need to worry about their own user interfaces anymore. They can simply develop their product, and do all of the other required work, but leave the user interface design to someone else. I wonder how long it will be before most corporations begin to hire their own staff devoted to interaction design.
Chapter 2 was a bit more difficult to follow; not because it was difficult to understand what was being said, but trying to think in such a general/abstract way is difficult. Trying to think broadly enough about conceptual models and problem spaces is difficult when unaccustomed to doing so. The Xerox and VisiCalc examples did help with understanding though. Speaking of which, it’s unfortunate the Xerox and VisiCalc never got the recognition they deserved. I suppose it just goes to show how far interaction design has come, and how people are continuously building upon it.
It seems to me that most of the ideas in chapter 2 overlap somewhat. Each concept in the chapter differs from the other in only a small way; they’re all closely related. I think this is what’s most difficult. All of the models blend in with one another, and it’s difficult to distinguish one metaphor from another.
I’m also trying to narrow down what I’m going to nominate for the Hall of Fame/Shame. I think I’ve narrowed it down to a category: computer applications. Now I just have to decide which one…
Subscribe to:
Posts (Atom)