ROLE: UI/UX, WIREFRAMES, PROTOTYPES, USER TESTING
GOOD FOOD is an app I created for my first project as a UX Design student at General Assembly. Each group was given a word or theme. Using the UX principles we learned, we each came up with a problem we wanted to solve individually.
Create an app that allows users to identify the issues that are important to them and allows them to quickly get and share information about their food.
Users who are concerned about the source of their foods, like how it affects the environment or a company’s labor practices, cannot easily find this information without doing hours of research.
How do I empower the users to be able to make informed decisions?
How do I encourage knowledge based decisions with being “preachy”?
How do I code a landing page for my app?
The affinity map showed many of the themes that come up when you think about food. Some topics included preservation, spoilage, restaurants and dining out as well as sources and concerns about where our food comes from. The last topic sparked curiosity because organic food has become more mainstream. Additionally, I had recently heard something about the source of shrimp in particular but had not taken the time to look into the subject. This seemed like the perfect time to do a bit more research.
I wondered if other people were curious about the source of their food. Not only as a geographic concern but also and social or economic impact of the food we eat. According to my initial research people were really interested in this topic but had no way to easily learn more about their food.
This app is ideal for the user who cares about the environment, labour laws or GMO's for example. But, as much as they care they do not have the time or resources to learn everything about the source of their food. their food, but they want to. This led me to the User Story and Journey.
Thinking through the user flow helped me to understand the many tiny steps that are needed to take a user from start to finish. Creating the wireframe showed me the screens I would need and how the user might go through the app.
The prototyping process proved to be both fun and rewarding. I did both a paper prototype and also a clickable prototype in Marvel. It was very helpful because it was at this point that the users were able to give feedback on each of these steps regarding what aspects of the app were clear or unnecessary.
By observing the users interactions, I was able to see where users were having difficulty and make the adjustments.
CREATING A LANDING PAGE
For the second half of this project I created a landing page for my app. This entailed designing mockups, prototypes and actually using CSS/HTML to build the site. I was also able to concentrate on the visual design of the page which included the use of mood boards, font style and color selections.
WHAT I LEARNED
I learned not to make assumptions. Some users did not care about the geographic origins of their food. They felt annoyed by the requirement to enter a parameter that didn't matter to them.
Keep technology considerations in a mind. A design idea may be good but it may not be technologically feasible.
Spend more time creating the initial survey. This would have given me an earlier understanding of my users needs.