HCDE 210- Interaction Design
By Ha Jung Nolte
This week in studio, we further worked with the process of Interaction Design and learned the importance of it. What is Interaction Design? It is the process of creating an interface with interactions that users can easily use while at the same time thinking about how to accommodate and heighten users’ experience. Our given task for this week was to create a mobile data collecting app for a user of our choice. The data collected had to be on an animal (also of our choice) that could help build researchers’ data collection and studies. The animal that I had chosen was a BEE and the centered users were gardeners. I had named my app “Bee-Yourself” and it is an app that directs you to take a picture of a bee sitting on a flower and through a senor, it detects the number of bees in your snapshot. You can then jot down details of your surrounding and of course about the bee. The reason why I had chosen bees as my choice of animal was because the importance of bees for our environment is not widely understood. By creating a prototype of an app that is meant to be fun and interactive, especially for gardeners, hopefully it could branch out the importance of bees for everyone.
During studio time, I had brainstormed ideas that would fall under as the motivation and purpose of the app as well as what features of interactions of a notebook to keep records and to take a photo. On my own time, I sketched out a flow chart of my prototype to layout the interaction of it. The main screen of my prototype is simply a main screen to get started and also for more information. I had kept it simple because it is easier to navigate for users that are busy outside gardening. The final low-fidelity prototype was hand-drawn on notecards and further came to life with the help of the Marvel App.
Something I liked about the process of Interaction Design was getting to use the Marvel app on my mobile phone. It is a nifty design app that really makes your work come to life without having to use advanced coding and technical skills. I enjoyed how easy it was to use and fit well with the concept of low-fidelity prototyping. I think it was great for drafts, and hope to use it more often in the future. Another thing I thought was enjoyable about this week’s task was being able to come up with ideas and create a prototype that were of my own. As much as I like working with classmates, I think it is satisfying to see a product of your own imagination and dedication.
Where to Next?
As far I know, I do not think I will be using the process of Interaction Design as much as I hope I could. I could see myself using this process again in the near future of this class and maybe for fun to show off to my friends. If I were to get more into HCDE, I could see myself working with classmates and coming up with ideas using low-fidelity prototyping to sketch out drafts of an app as we had done for this weeks task. For my intended major of Health Informatics and Health Information Management, I do not know what the program entails, but if there are ever a time when we would need to produce a interaction design based prototype, I could definitely use the skills I have learned and apply it there.
As a I had mentioned last week for the UCD Charrette process, an inappropriate time to use Interaction Design would be when working with engineering and art centered work. If I wanted to design the mechanics of an elevator, a low-fidelity prototype of that would not be sufficient.