Project Overview

Nowadays, cooking from a traditional cookbook seems like an old time thing to some people. Most people find and use recipes they've discovered on the internet, which they usually search for on a mobile device. But who doesn't know the struggle of trying to wipe the phone to continue the recipe while elbows deep in batter.

Comi is our approach to transforming your cooking experience!

User Research

User research was conducted in several steps. First, interviews were conducted to get an idea of current pain points, gains, and the user flow in cooking. The information gathered was then translated into an empathy map, a user journey map, and a value proposition canvas.

Design

For the design we all agreed on some design guidelines together. So we created a mood board through which we determined the general colors and typographies. Using the Android design guidelines, we agreed on the general layout.

Prototyping

Before you start prototyping, it is important to be clear about what you want to test? You should ask yourself, what is the critical question I want to answer with my prototype? You can't test everything, so focus on the essentials. Start with the end in mind.

To do this, for example, you can put on your customer's hat and think, what is the critical moment in using your application. What will make or break your product?

In our case, there were two things that we thought would differentiate us from the competition. First, the starve button, which suggests a recipe based on 3 small questions.
Second, our voice control while cooking, which prevents you from touching your phone with dirty fingers.
We said to ourselves, if recipes are displayed prettier on our site than on the competitor's site, it won't make the customer tell his friends about it. But if our killer voice control gives the customer a great experience, they'll be happy to share it.

But we believed that! Of course, we couldn't prove whether the user really wanted these features. So we had to test it!

Now we knew what we wanted to test, so we could come up with a scenario where the customer would go through our app once. The user would choose a recipe and eventually cook it. This scenario is important because we can develop tasks from it, which we later present to the participants during testing to give them "instructions".

With this scenario in mind, we created a story board on which every screen and every click is defined in advance before we finally implemented it in our prototype.