Interaction Design Process Blog


In last week’s sprint, I designed a phone app that is able to record a numeric data of how many fish are in the Lake Washington area in different months. This app is a solution to learning how different seasons influence the migration or activeness of the fish in Lake Washington. The main audiences of this app would be the fishermen, fishing hobbyist, and researcher who are interested learning when is the best time to go fishing in Lake Washington.

In my design, besides of the basic entry for the name of the fish and amount of fish caught, I insert a feature that is similar to a leaderboard. It compares the amount of a certain kind of fish caught by the user of that day among other users. This ranking system would be a motivation for citizens to use the app and input data.

Another feature in my design is the photo entry for the kind of fish caught. In this feature, users will be able to take a picture of the fish they caught and scan it to learn about the name of the particular fish kind. The reason this feature is necessary is that sometimes normal citizens wouldn’t know what kind of fish they caught and the scanning feature can help to identify the fish with machine learning of pre-existing database. This feature would also prevent un-reported fish due to not knowing it’s kind.


I liked the prototype design on paper in last week’s process. I think it is a great and low maintenance technique that keeps good idea going and preview the app’s basic interface frame. Sometimes just picturing an idea or an entire prototype in the mind is hard to present and easy to lose the track of the interface pages. With prototype design on a piece paper with pen keeps record of the idea that I can always go back to and work on.


I see myself using this technique a lot in the beginning stage of a product design in the future. On paper prototype allows me to explore interface options quickly and it doesn’t require many detailed after work such as the decoration or change of fonts. It is just the blueprint of a interface design that can be further developed. For projects that I am not sure if my solution is the best or even a good one, I will probably use this technique because it doesn’t require me to put in a large amount much work to finish it. Therefore I can fix the prototypes easily after critiques without feeling a waste of time and energy.

Like what you read? Give Erica Tan a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.