Patrick Binkley beta
pjbinkley.iweb.bsu.edu/flash/fullblast.html
Labels: Patrick Binkley
Interactive Video Design
Current working build is here:
Labels: Jacob Barnard
Labels: Jacob Barnard
On the thought of multitasking, because I'm so boring and can't find anything else particularly interesting about the chapter, it's interesting how people today seem to be so overwhelmed that multitasking has become a learned defense as a way to absorb all the information which is constantly being fed to us. It's not a negative or positive reaction, it's just the way it is and the way our society is changing. An interesting product of multitasking, though, is how customization has become a beneficiary of it, in that we are very selective about the information we reach out to understand. The selection of product and information that people choose to expose themselves to is more interesting to me than the fact that we are so constantly trying to do everything at once.
I liked the section in chapter seven about designing for adaptation. This is a huge part of interaction for me. When someone goes on to msn, yahoo, or gmail, they're able to give their homepage a custom fit. Even inside Blackboard your able to adapt the site to what you feel is most important. I think it would be cool to give every webpage this sort of interaction. For instance, you could change the color scheme to something more pleasing to you.
Labels: James Frye
Like many of the other comments I also found the section of the chapter on multi-tasking to be very interesting. It seems like we have kind of become numb to the amount of multi-tasking we do on an everyday basis to the point where I do not think we perceive it as multi-tasking. As Christian stated how often do we see someone on chatting on Facebook, listening to their IPOD, writing a paper, and talking on their cell phone all at the same time. Our generation is maybe the first to adapt, and we had to adapt, to these new technologies. In the future we will be designing for our generation as well as the younger generation, who have grown up with multi-tasking and who are very efficient at it. Therefore it is important to take this into account whenever we are designing a new media element.
Labels: Andrew Lewis
I thought the section on Multitasking has some interesting ideas. The author talked about how he frequently misspelled the word "ubiquitous" and how he thought that computers connected to the internet should be able to somehow take misspellings and share them with the world. So if one person anywhere around the world misspells a word, and corrects that misspelling, every other person connected to the internet who made the same mistake would be automatically corrected.
The book mentioned one of the drawbacks of customization being that users have to enter in information they may not want everyone to know. Privacy concerns are growing larger, especially with recent events like Facebook trying to say they'll own all data you enter into their site, even if you delete your profile later. I think when you create a device that allows information based customization, you need to make sure the users' privacy rights are protected
Labels: Bryanna Homeier
The book was talking about how "the internet will move from behind computer monitors and into the objects and buidlings all around us". This also concerns me because of the direction that country is going because the government is putting their hand into more and more things. One thing that is does not have its hand in, is the internet. When it was talking about RFID chips, I have a concern because you can use those to track items, and/or people. It is a possibility that those devices might have to registered with the government and that is not appealing to me one bit. I don't like the idea of people knowing everything about me and knowing where I am, and what I buy. I especially do not want the government knowing these things about me.
Labels: Scott Loy
When the book mentioned that traffic maps could sense the traffic conditions based on the information coming from cars, that made me worry a bit. There would have to be some sort of device that tells the program of where and how fast you are traveling. I do not think this would be a good idea. I would not want to tracked of where I am going and how fast I am driving. It reminds me of Big Brother. I don't want people to be able to track where I am going and how fast I am driving. That is a concern to me because people can use that information for other things that I do not even know about.
Labels: Scott Loy
In this chapter, the author of the book talks about multitasking. I understand what multitasking means, but I never really thought something like Amazon showing the “People who bought this also bought…” could be considered multitasking, but it actually is multitasking when I think about it. I really want to make my project for this course interactive and multitasking, but I am not quite sure if I can achieve them in a flash video or swf.
Labels: Tetta Oyama
I thought the sections on flow and adaptation were useful. Saffer mentioned that it is important to keep in mind that there is a back and forth between the user and the product. He used an example of how a user learns a drawing application. At first, the design is simple. As the user becomes more familiar, the product seems to be able to do all kinds of advanced things. Saffer explains that the two entities react and respond with each other. An application that is too challenging produces anxiety, an application that is not creates boredom.
Labels: Chris Richardson
I think if people are able to customize their interface, it generates more interest for them in the product. Even if the look of the interface isn't the primary function of the product, I think if something is personalized, people will want to come back. As far as multitasking goes, I disagree with Saffer about the automatic spell check. I'm not so sure that would work correctly in certain situations. For example, sometimes when I'm trying to format something in Word on my own, Word decides it knows what I'm trying to do and formats it for me. Unfortunately, most of the time it is wrong. Of course, that could just be a Microsoft problmem. Until I'm convinced it could be done correctly, I'd rather just run a manual spell check.
Labels: Evan Bell
The section I found to be very interesting from these two chapters was the part on Designing for Multitasking. From the title, I figured it would be discussing how these days everyone seems to be doing so many things at the same time. Like when you walk on campus, very rarely do you ever see someone either A) not on their phone, B) not with an ipod, or C) a combination of the two. This section actually talked about how all web pages and computerized devices should (and for the most part could) be personalized based on user preferences. I especially found it interesting when it talked about web page layouts being tailored to individual users and changing over time. Think of how much time and effort this would save if web pages changed their own design and layout based on how the user interacted with the site. This would optimize the usability of the site. I would like to see our future head in this direction of more personalized media.
Labels: Christian Long
The part about this chapter that really interested me was the discussion of spimes.
Labels: Jacob Barnard
I liked the section of chapter 7 that talked about designing for multitasking. Saffer mentioned how Amazon made completing tasks in the future easier and more interesting for users. When you check out and make a purchase, your information would be saved, making the next purchase very fast and easy to do. I'm not sure how much multitasking would benefit my website for this class, but it's a good idea to keep in mind for the future. Anytime something can me made easier for the user, you should take advantage of that to keep the users coming back.
Labels: Patrick Binkley
I think one thing we need to notice from this chapter is how Saffer defines smart applications and clever devices. These devices talk with one another (i.e. the laptop feature that talks with a traffic server about your car's speed, etc.) and are able to relate to each other.
Labels: Jacob Barnard
Reading chapter 9 an idea occurred to me. Why don't we see more products that can interact with each other? Right now there are many products that do interact with each other on a sub level to a whole level. Ex: An iPod will sub interact with a xbox 360 to play music but you can't load music on to an iPod like you can do on a whole level with a computer. That's software, hardware still lags a little behind. Though USB's are the most universal .
Labels: Michael Kujawski
Reading this chapter brought back memories form the web design class I'd taken last year, and amongst other things, the idea of text and its usefulness or creative flexibility recurred to me. On that note, I'll just post a link to a site that I've contributed to, but regard highly in its layout. Thunderbolt is a very text-based website, which alludes to a more journalistic and sophisticated take on the world of video game sites, and has a great sense of usability and guidance for the end use. It's just a site I think about whenever web design becomes the topic of discussion.
When I was reading this chapter, I was thinking about how web design has evolved and become more sophisticated in such a short period of time, in comparison with other forms of media. What I mean is that newspapers and television (especially news) has been presented in basically the same way since their inception. However, the internet is constantly changing. Remember when websites with frames were all the rage? Now if you come across a page that uses frames you just assume it hasn't been updated since 1998. Also the internet is incorporating more and more multimedia as people get faster connections. I like to browse through waybackmachine (http://www.archive.org/web/web.php) to see how websites used to be. For example, ESPN.com is barely recognizable in 2000 compared to today. But, the Sportscenter broadcasts are basically the same, except for a ticker on the side that lets you know what's coming. And BSU's webpage in 2000 looks like it was designed to be viewed on a PDA. So I guess my point is, it's becoming standard to assume that our users are going to be using decent sized monitors with fast connections, and as interaction designers, we facilitate the growth of technology by basically forcing users to either upgrade their systems or not use our design.
This chapter was full of alot of good information for creating projects. One thing that the author mentioned that I've heard too many times to count is about typography. Although everyone by now should know about the good and bad font types to use, we still see websites that are hard to read. Making sure to have the right type of font, size of font, alignment, etc is a big part of creating a successful project and is just one of many aspects to think about when creating projects.
Labels: JGeisler
I really liked how this chapter mentioned the over-use/under-use of sound on the web. I think that sound can really help develop a particular applications interactivity. The book mentions how some websites can suddenly start blasting music at you while others use sound to subtly enhance an interface. And referring back to the previous chapter when it spoke about designing through emotion, I think sound is a must. It can definitely take a feeling that a developer it trying to create to the next level.
Labels: James Frye
When reading chapter 6 of the book, I found the section about visual flow to be helpful and interesting. Saffer mentioned that in the western world, the eye generally travels from left to right, top to bottom. The diagram in the book with the squares seems pleasing and easy to follow because of the visual flow that the designer kept in mind. Using subtleties like this can easily help the usability of your design.
Labels: Patrick Binkley