Sitemap

Interaction Design

5 min readApr 6, 2017

--

In today’s HCDE 210 lab, we did an Interaction Design activity meant to lay the groundwork for our low-fidelity draft sketching skills, as well as get us in the habit of thinking about users throughout our design process.

In this activity, we were given free range on a user base but had to design a mobile application that could help scientists catalog some form of wildlife. A few things we were asked to think about while thinking about our solution included: who is your user base, why should they care about your application, why should they continue to use your application, how will you design your solution to serve your user base, and how will you be recording data to help the scientists?

Given that it is Spring and the University of Washington is home to a lot of ducks, I wanted to center my application around cataloging ducklings in the U-District. There are always ducklings around Drumheller Fountain, Rainier Vista, and the Quad during Spring, so I figured an app that would let students and visitors to the UW help scientists catalog the number of hatchlings would be really cool. To keep users interested, the app offers free bubble tea from Oasis after each 5 unique submissions. Ideally, users would be walking around the U-District and whenever they see a duckling they will pull out their phone to help catalog that specific duckling. To help manage the potential for multiple submissions of the same duckling, the application utilizes a unique algorithm that detects ducklings in each picture and compares it to all other known ducklings so repeats cannot be recorded.

The low-fidelity application I created is very similar to many camera apps, however it does allow users to input more data that the picture alone could offer us.

Press enter or click to view image in full size

As you can see, there are text boxes where users can input things like injuries, discolorations, cuteness factor, and any other notes relevant for scientists to catalog. Many of these may not be noticeable from the picture submitted, so I thought it important to include places for users to input such data. While the cuteness may seem silly, another way we hope to keep users interested is by compiling all of the cutest duckling pictures to start an Instagram to show off some of the data our users are collecting. We hope this will keep users coming back and submitting more photos, and also potentially attract new users who want their pictures featured on our page.

Get Kyle Simpson’s stories in your inbox

Join Medium for free to get updates from this writer.

Another important visualization aspect I wanted to include was a progress bar for users to see how close they are to their next free drink.

Press enter or click to view image in full size

On this page, users can visually see their progress to the 5th submission, as well as interact with our application in a few more ways. First, users can see their past photos so they have access to all their previous submissions. I wanted users to remember the ways they have contributed to our repository, as well as have a way to save old pictures if they ever want them in the future. Second, users can revisit the tutorial to refresh their memory on how to navigate the application because I thought it would be important to users to have the ability to go through this again for any reason. Third, users can view a map with directions to Oasis bubble tea, just in case they didn’t want to open a whole new application to figure out how to get there. And finally, users can return to the camera to take more pictures so we can keep them engaged, as well as have an easy way to return to the main function of the application.

Reflecting on the process we took while designing our applications, I really enjoyed the speed and flexibility paper prototyping brought to interaction design. I have worked through some interaction design using web-based tools before, and it always seemed very slow and clunky to redesign a piece that needed fixing. With paper prototyping, I had the exact opposite experience. Being advised to stay away from technology during this process, I found it very easy to jot down notes as I thought about what to create, how to create it, elements that might be useful, and common techniques that make things flow well. Using a pencil and paper also allowed me to make mistakes, fix them easily, and iterate through multiple designs rapidly. I never felt tied to any particular element of my designs, because it was so easy to erase them and create a new piece in its place. With my previous experience in web-based prototyping, I definitely felt obligated to keep certain pieces that took a while to implement, but with paper prototyping I was able to freely design anything.

I also really like Marvel and the interface they provide for stitching together basic wireframes from the paper prototypes. It was very easy to add pictures, connect them using the hotspots, and figure out the best way to make the elements flow together. I also noticed that some of the limits of Marvel actually helped me design a better product. For example, at one point I was trying to connect one screen to two potential other screens, and Marvel’s inability to do so helped me notice that there were better ways to flow through the interaction I wanted. Because of this I was able to create a more logical interaction.

Thinking about other applications of paper prototyping, the biggest way I see myself implementing this technique is while writing papers. Currently my process for writing a paper is to just sit down and start writing with no plan in mind or direction of thought. I think it could be really useful to use the idea of making small “sketches” of arguments on individual Post-It notes to better plan and map out how to structure my arguments. Using something that is neither permanent nor very structured could be super useful when it comes to formulating my argumentative structure. Slightly more broadly, I think this technique could be useful anywhere that quick, low-fidelity brainstorming is needed. I can’t say enough how much I like the idea of being able to easily destroy bad ideas and iterate through multiple good ones to get to something that might actually be useful.

To be honest, I can’t think of too many places where an approach like this wouldn’t be appropriate. Like was mentioned on the first day of class, everything is designed (theoretically) so this process could be useful just about everywhere. One small, potential place this might not be incredibly applicable is in a space where you aren’t trying to completely “reinvent the wheel” so to speak. If a designer is just trying to tweak a current feature to make it more useful, then this might not be incredibly helpful since there is already a working design that just needs minor improvements.

If you would like to see the entire application to get a better feel for what exactly I created, a link can be found here: https://marvelapp.com/g7iei76/screen/26729342.

--

--