A recipe management app to help you remember and share the recipes worth having
RecipeTin is a mobile application that strives to replace the paper-based recipe organization system you would find in your mother's kitchen. Store all the recipes you will need in a handy application that makes it easy to edit, scale, group by type, and plan for future occasions.
Finding a good recipe on the internet is easy, but saving that recipe for another day is often forgotten. Considering search engine metrics and the depth of content available, you may never find that recipe again. Meal planning can be made easier by helping you keep the recipes together, to encourage you to develop good habits in the kitchen.
We found our target
I was responsible for the competitive analysis, lo-fi wireframes, research, and affinity diagram of the survey data. We iterated three user flows and made a task analysis of what the application would do in practice. I created a low fidelity prototype based off of a paper prototype to test its form and function with six users, before the design was iterated into high fidelity.
My biggest constraint was my initial starting ability. This was the first time learning these techniques and putting them into practice. Between honing my interviewing technique, moving through the design cycle, understanding Adobe XD to create prototypes, while learning the specifics of design thinking was a challenge of no small measure. We completed and iterated this project in three weeks to the an earlier state than is available currently.
The ones who agreed to be interviewed are male and Caucasian. All of them had done some traveling so I was able to summarize their feelings and insights into an empathy map, to identify their pain points and preferred activities. I transferred that into making and organizing wireframes into a hypothetical task flow. I was able to comprise the login screen, main menu, and search function of the application. I researched comparable applications and studied their user flows as a point of reference. I arranged materials into a lo-fi prototype and tested with users to address potential oversights. This led to a round of iteration and then into the creation of hi-fi prototype mockup images. This was tested and iterated another time before the project concluded.
I was able to understand user flow and how it may be used to order screens and processes within an app. I iterated the product several times and would like to iterate it more. Initially I was caught up in the minutiae of what I was doing that I found it difficult to make any headway. After the initial learning curve I found myself getting more and more expedient in the creation of this process. I would like to return to this project in the future to update it with my current skill set and increase functionality.
