Final Project thoughts:
I actually really enjoyed working on the final project for the most part. Considering the amount of time that we had to work on it and the amount of things that we wanted to get done, it got a little stressful toward the end, but I believe everything worked out in the end. I believe that my group worked very well together, as well. We had disagreements like any other group, but I think we were able to work through those well. I mentioned this in class, but I feel like this project would have gone over even better if the CS people had access to the software that ID students have. I know this varies by project, but our personal project was definitely more ID heavy than CS heavy, which put a lot of weight onto the ID students. Of course the CS students did their parts, but I feel like a lot of the pressure would have been taken off of the ID students if we had, had the option to use their software.
UX Class Experience:
To be completely honest, I did not know what to expect from this class. I didn’t even know what it was when I signed up. My adviser told me that I need a 3xxx class and suggested this one since she had good things about both professors. Since I didn’t come in with any expectations, I can’t say that it did or didn’t meet my expectations. I can say, however, that I thoroughly enjoyed this class. I liked being able to actually work and do things with my hands, instead of coding all day long. As I said in my above paragraph, my project was definitely more ID heavy, so I was able to do a bit more on the ID side than what some other students did. This was also my first integrated course, and I found that I liked it a lot better than what I thought. I was a little concerned about working with students from a different major. I know that CS students have a particular way of working, and I was concerned that CS students’ way of working and ID students’ way of working would clash and cause problems, but I am very glad to say it didn’t turn out that way.
As other students said in class, I kind of wish that we had, had more time to work on the big project longer. Other than that, I don’t really have any kind of constructive criticism. I personally liked having the class one day week. It did make travelling for weekends difficult, but that’s more of personal problem. I really enjoyed this class and have recommended it to all students who are looking for a 3xxx class.
Intelligence on Tap:
I really enjoyed this article. I like reading any article that discusses the evolution of AI and what it could be in the future. While I do like the concept of AI, the thought of where AI could advance kind of worries me. I believe that the advancement of AI could bring a lot of ethical conundrums into play because in a sense AI is giving a machine a brain of its own. But how is that brain any different than that of a human? I feel with the advances that AI is making that soon humans and AI will soon be indistinguishable, so will we have to make new ethical laws for AI or will they have to abide by human laws?
Machines Learning Culture:
I found this article to be very interesting. I am actually in the Creative Computing Capstone right now, so I like to see the ways that Machine learning was integrated into the arts. I never considered Machine learning to play a role in the visual arts, but this article proved me wrong. Knowing that now that it can play roles like this, I would like to see other ways that Machine learning can be implemented.
UX Design Innovation
Machine learning is a fascinating topic to me. I’ve seen how it is used and implemented, and I believe that it is a great advancement in technology. My only concern is that it may be integrated into a part of human society that does not require the technology. At some point, humans need to realize that all things must be automated.
We decided to come up with ideas for Design for Disability.
- A mouse free computer for those who suffer from Carpel Tunnel.
- A phone app that would be able to read aloud to those with hearing disabilities or are blind.
- An app that would help you set up doctor’s appointments if you’re new to an area or need a new/special doctor.
Our interview group was looking for a wallet that had preventative measures of losing the wallet. It also needed aspects of mobility and security that would keep the wallet easy to carry but had some level of peace in mind. We created a wallet that could easily blend into the everyday life by having it placed on the wrist of each user. This could guarantee that losing the wallet is much more difficult because it is physically part of the user’s outfit.
We decided that our target end-user should be an athlete. After the presentation, we realized that athletes would get the most use out of our product and that they would benefit the most from it. It would allow athletes to have their important personal effects on-hand without the annoying weight of a wallet in his/her pocket or the swinging that occurs while running with a wallet in your pocket.
The one comment that we wanted to address about our wallet was the concern about card organization. We completely agree that our design lacks a way to organize cards. If given the opportunity to continue with this project, we would add a feature so that cards would be organized because we all know how frustrating it can be to find a specific card.
We had three ideas for the Wallet Prototypes.
We had the idea of an arm sleeve. This came from the idea that many girls either don’t have pockets to carry a wallet or the pockets are insufficient. It allows the user to not have to worry about carrying a wallet or even losing one because it would be a sleeve on your arm. The design could be as intricate as the user wants it to be. In the design in the following figure, you can see that this design looks like the user is wearing multiple bracelets on his/her arm; however, flipping the individual’s arm would show a small pocket where cards can be placed. This pocket would also have a small flap to close the opening so that cards would not fall out. The material would be soft and stretchy so that it could be worn by any user. We also felt like this would be the best to prototype, so we have figure below, as well.
We had another idea of creating a very small, but durable design. This wallet would be just large enough to fit cards and a bit of cash in it. The wallet would unzip fully so that the user would not be blindly placing cards in the wallet or reaching for the wrong card. It would also have a strap that would function similarly to a Wii-Remote strap. It would allow the user to tighten or loosen the strap so that the user wouldn’t even have to worry about carrying it. As you can see, there is also a small shield on the inside of the wallet. This indicates a tracking device in case you do lose your wallet.
The solution to the problem at hand that we had was the loss of the wallet. The first idea that was given was a string that is attached to the wrist and the the wallet so that with a push of the button the wallet can be summoned and never be lost. We thought that more could be done with the idea and have more futuristic options like having QR codes that can pay or a connection with apple pay so that the user can pay electronically through their wrists.
I found it interesting in the first reading by Sengers that she believes because engineers follow a Taylor-like way of solving problems, they are not having fun with the work that they do. I don’t completely agree that engineers follow that mindset all the time, but from a personal perspective, when I do follow that strategy, I enjoy it. I like following a routine of doing certain procedures to follow a problem. In the other text by Blythe, I do like how he mentions how people should design to appeal to the different senses of experience. I think what Blythe mentions is important to take into consideration when designing a system.