Problem B: In dorms, buying ingredients for recipes can be expensive and wasteful. "When I bake with friends, I have to get a whole gallon of milk and entire carton of eggs, even if we use less than half of each of those," said one interviewee.

Solution B: I created a second feed for Ingredients, where individuals can post ingredients such as the remaining milk or eggs, leftovers from club events, and more. Users must "claim" the item, meaning that there is a depleting count of how much is left for the next user to claim.

Problem C: Each dorm kitchen contains a different set of specs: some have ovens, some don't, same with pots, pans, baking trays, salt, pepper, oil, and other supplies, which can make it difficult to plan events centered around cooking, or even cook for oneself.

Solution C: I designed a map feature which users can use to find kitchens and geotagged events. Users can also input information about which features the kitchen contains for other users to see.

With the MVP features identified from my research translated into app features, I moved onto refining my low-fidelity wireframes, layout, and navigation into high-fidelity, interactive prototypes from user feedback and usability testing metrics.