Foody is a mobile app concept with AI. It is designed to make smart and quick decisions when you are unsure about choosing what to eat. Foody analyzes your dietary habits, assesses your daily food selections and allows you to swipe through options to show you most compatible food options for the fast paced day.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/806cdce1-31f6-47b1-81ec-43eb4e6976e3/Mockup_final_product.svg

My role in this project was to bring Foody to life by creating quick, enjoyable and meaningful interactions that primarily tasked to solve the painful question; What should we eat?

Design Process

Context

This is the story of July

July is a hard working professional in the fast paced startup environment. Her favorite time of the day is lunch time because food simply relaxes her and gives her an escape form the craziness. She is eager to try new food options and have meaningful conversations with her friends during lunch and they usually order food to eat near the office.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/216fbbb7-f29c-4e2c-93fd-b9b1df719084/5d0156faa38ae0050345e69e_Foody-July-1.svg

However,

July and her friends spend more than 15 minutes on deciding what to eat, and by the time they finish their food, its time to get back to work. Which leaves no room to relax. This waste of time causes discomfort and frustration.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/e3d03292-ff70-45cf-8491-049397d79f5d/5d0156faa38ae0fa3445e69f_Foody-July-4.png

With that in mind,

I wanted to get to the bottom of this and find out why this is happening. I talked with July and her colleagues individually and asked them what the problem is. Here are some of their reasoning.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/3b85be01-5114-4c7e-acd4-88c773a9f029/5d0156faec964681972f2337_Foody-July-3.png

Sketching Ideas

Once I got July and her friends' insights about this problem I created sketches of immidiate ideas. In this project I was determined to go back to the end user after sketching, wireframes and prototype and allow the final solution to evolve around their feedbacks and opinions on the deliverables I created for them.‍

<aside> ❓ July, what do you think about these sketches?

</aside>

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/18984165-3ad3-46fa-b50a-7323fa3874aa/Feedback-on-Sketches.png

Initial concept sketching, refined and colored for visual engagement.

Initial concept sketching, refined and colored for visual engagement.

Wireframes

Other than improving upon the design with respect to July and her friends' comments, I created wireframes to represent different levels of the information architecture. This way of visualization will later serve as inspiration of the 3D representation of Foody.

<aside> ❓ ‍July wireframes are ready, any comments?

</aside>

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/6eda31fb-966b-42cb-985c-87db13ead03c/Feedback-on-Wireframes.png

Wireframes generated on Balsamiq to quickly get the message accross.

Wireframes generated on Balsamiq to quickly get the message accross.

Key Decisions

After listening to July and her friends, and generating potential solutions with them, I felt ready to design the high fidelity prototype and get the ultimate feedback on the product. To establish a baseline I came up with three key design decisions that were later turned into tasks and shaped the final product.

  1. The food picking process should at least be ENJOYABLE. The app interface, and interactions that come with it should not bore the user.
  2. The application should be customizable by the user to offer a truly PERSONAL experience.
  3. In case the user needs a quick decision by the app, FASTER AI response through voice interaction can save time. Also allows RANDOM choice options.