UX-research: Change shopping habits related to food
One-third of food produced for human consumption is lost or wasted globally, which amounts to about 1.3 billion tonnes per year. In this assignment I have been asked to on a micro level come up with a solution in form of a digital product or system that can help consumers to change their consumption and shopping habits related to food. I will be focusing on wasting less of what we already produce, rather than how we grow food.
Design thinking: A non-linear process
Design thinking is a framework that UX-designers can use in order to tackle big, complicated or even largely unknown problems in product development. It is an important thing to be aware of before starting the process of a new product. You can look at it as a research plan.
Empathise
To start everything, I begin with empathising. I need to do some research to understand the problem and my potential users. In this assignment I will be creating something brand new, and therefore I need to focus on understanding my potential users and their needs. This way I will be able to solve their problem.
This means that i need to be doing some generative research. Generative research is a method of research that will help me develop a deeper understanding of the users in order to find opportunities for solutions and innovation. If I don’t do the research, i could end up with a product no one would want to use. And that is most certainly not what I am aiming for.
Solving a global problem with one digital product is what I can say: impossible. Therefore, I need to be focusing on solving the problem in a smaller scale. Locally and individually, which can make an impact towards the greater cause of reducing food waste and loss. So, in my research I will focus on deeper research so that I can truly understand the problem I am given. But I will also focus on finding out who my potential users are and how they live their everyday life.
Secondary research
The first thing I began with was conducting secondary research in the form of going through statistics and facts about the topic. Reducing food waste in the world Is a very big task. And I cannot decide to change the world, because I can’t.
Food waste is one of the most meaningless and sad things we see. Locally it’s sad, but globally it’s a disaster. Specially if you think about the 820+ million people who are going hungry. The UN Food and Agriculture Organization estimates that as much as 1/3 of all the food we produce in the world is not eaten! This is problematic from both an ethical and environmental perspective, as food production occupies 37% of the worlds land area, 70% of fresh water and accounts for 24% of global greenhouse gas emissions.
In Norway we aim to halve food waste from farm to fork by 2030, which means that food waste must be cut at all levels (household and producers). Almost 60% of food waste in Norway is accounted for by the household, where each of us throws away an average of 42,1 kg of edible food every single year. In 2016 framtiden.no did a study on the Norwegian food waste. And they found out that the Norwegian food waste could feed 800.000 people. And if we reduce our food waste to zero, it will give the same effect as removing 400.000 cars of the road.
“Competitor” analysing
Since I am going to create an app to help people reduce food waste, I also have to take a look at other similar apps to understand the current market. What are they doing? What value do they provide? Strategies and market. I found these apps:
- Too good to go
- Throw no more
- Spot on
- Sulten
Too good to go
The app Too good to go allows restaurants, cafes, flower shops, hotels and stores sell their leftovers through the app. People can use the app to buy todays leftovers from the hotel breakfast for example. Then the hotel doesn’t need to throw away food, and the people buying get a delicious lunch. Or maybe the bakery has leftover bread that they can’t sell the day after; perfect to buy as a user instead of the bakery throwing it away! They have a lot of users and their growth is very big, but they have a few issues: it works best for people in cities, and it doesn’t help the household to throw less food.
Throw no more
Their vision: We live to make it easier to reduce food waste. After checking out this app I almost had to laugh a little. It is basically exactly the same as Too good to go. And sadly, for Throw no more, Too good to go won the marked. Probably because the design looks more modern and the app is easier to use and understand. And also, because their market budged probably were higher.
Spot on
The Spot On app gives you an overview of all spot items at greatly reduced prices in stores in various grocery stores. This is a very good concept as well, but again it focuses on producers and not the household. It is a very good thing to buy food before it gets old, and helping people buy it by reducing the price. Spot On’s vison: Think environment, save money and shop smart!
Assumptions
At the beginning of an assignment you always have a lot of thoughts, ideas and assumptions around the topic. An assumption is formed out of the given problem and is assumed to be true. The goal is to prioritize a set of assumptions to test, based on which things would be riskiest to get wrong. The higher the risk and the more unknowns involved, the higher the priority to test these assumptions. The assumption sheet will also help us create an assumption persona and defining research objectives.
Assumption Persona
To make sure that me and the team helping me have the same vision of who we are building for, I am creating an assumption persona. Personas are fast to create and will help make the research a further a little easier. The assumption personas will also be changed after the research, to be a primary persona.
Defining research objectives
Before recruiting people to my study, I am going to define research objectives. The research objective should address how I am going to study the problem and help me define how I’m going to post the future study. It will also identify what knowledge gaps that needs to be filled.
What am I trying to learn?
I am trying to learn how people of the household address food waste today. Do they think about it, or do they do anything to prevent it? If they find it hard to do something about, and why. And general pain points around the topic.
What should the research achieve?
The research should help me understand the users and the users pain points, so that I hopefully can create something that will remove them.
User survey and Participant recruitment
To collect quantitative data in order to validate customers’ needs and pain points, I created a user survey screener. This survey will also help me to recruit participants to user interviews. In the screener I put questions they had to answer so i could choose the people who answered what I was searching for. I also made sure they allowed me to contact them and to save their answers recording to the GDPR rules.
User survey answers – Quantitative data
In my survey I got a lot of answers from a lot of different people. And here are a few key-answers: (Funfact. Alot of people say they want to reduce food waste, but almost noone does it).
Participant recruitment
During my user screener I got a lot of answers, from a lot of different people that represent people from all stages of the life. Therefore, when I were to pick out participants, I made sure that they were quite different from each other. I want to create a product that will work for everyone, not only a certain type of people. In the survey I also collected a lot of interesting facts that would be great to use in the research and ideation later.
I have chosen to recruit 5 participants. This is to filter out any assumptions I have in my personas, and also so that I can find any patterns or key behaviors for my users.
These are the people I ended up Recruiting (they had agreed in the survey for me to use their information, and that i could contact them):
- Eivind, 25, Working in foodproduction - fish industry. Single.
- Stine, 31, year old kinder garden teacher. Single.
- Mats, 19, year old student. Single, but live at home with his parents.
- Karin, 72, Retired. Married, two kids and a bunch of grandkids.
- Mona, 48, Hotel Manager. Married, with kids.
Participant scheduling and incentives
Next up is scheduling the user interviews. While contacting the users I make sure that they know what they are joining in to. I provide them clear context on the study, explain why I want them to join and how they are helping me and also make them sure that they are not put to any test. They cannot come with any wrong answers.
Planning the Interviews
In the interviews I will be using the 5W technique. This way I can interview them better, and I can find pain points and goals. I’ve already gotten to know a little about them in my survey, so i can base some of my questions on their answers in the survey. So this i my start-up script for the interviews:
- Do you try to reduce food waste?
- Why do you/do you not reduce food waste?
- While cooking; do you think about using food that is near experation date?
- What do you do if the food is past it’s experation date?
- What do you do with leftovers?
- What do you know about the food waste situation in Norway?
- Do you find it hard to use up all your groceries?
- What do you want to get better at, when it comes to food and saving food?
These questions will give me information, and also give me the opportunity to dig deeper in their answers. I want their answers to help me create a new question based on their answer.
User interviews – Qualitative research
While conducting the interviews I used different equipment. I recorded the sound from everyone so that I have the whole interview recorded. This way I can hear back everything afterwards. But I also noted down in a notebook, for backup. In my notebook I just noted down quick sentences and not the conversation.
Systemizing information
After conducting the interviews and keeping people answering my survey; I gathered a lot of raw data to systemize. So I decided to make an affinity map to systemize the data I conducted during the research. This way I can create a visual representation of the data I’ve been gathering and will help me make a future strategy.
These are the pain points and the goals I ended up with after systemizing the information in the affinity map.
Ethnographic interviews
I really wanted to do ethnographic interviews as well. This is because as Margaret Mead once said, “What people say, what people do, and what people say they do are entirely different things”. People often recall wrong about our own behaviour. In trying to re-call what we did or believe we did; our recollection will often not align. Especially when we try to describe why we do something.
Therefore, while doing ethnographic interviews I can bring the research at home to my “objectives”. In their own environment. This way i can observe in exactly the way they actually do things. And maybe find some faults from the interview section.
Due to the Covid-19 situation we currently are in, I sadly did not get to do any observations or ethnographic interviews. I decided to continue my survey and extend it to get as many people as possible to join and answer. I ended up with a lot of answers who surely will help me continuing the study.
2. Define
Visually illustration
Based on the information i have gained in my research, I do now have enough information to visually illustrate my primary persona and scenarios. The pain points and the goals i have gathered in my affinity map, and also through my screener, helps me to understand the most usual wants and needs. This way I can create a primary persona, with the needs and goals that fit most people. In this case, i ended up with two primary personas. This is because they might have a lot of the same issues, but the issues are there for different reasons.
Context scenarios
Next, I am making context scenario. The main purpose of making a context scenario is to show how a product can help my primary personas to achieve their goals. These scenarios are just assumptions but will help me during the ideation session. They will help me think of different scenarios my product could help the personas. I will take each defined goal of my personas and string them together in a scenario.
Let’s begin with Lillian. These are Lillian’s goals:
- Shop grocery’s 1-2 times a week.
- Make healthy dinners.
- Use all the ingredients she has at home.
Lillian has just finished work and do now have to run by the store on her way home. She is a little stressed, since she has to make dinner before her kids go off to football. When she comes to the store, she hasn’t planned out what she is going to make, this makes her even more stressed. She takes up her phone and opens her app. The app has gotten to know Lillian, and therefore recommend her a weekly dinner plan with a shopping list with healthy dinners and snack. This makes Lillian relax, and she can now be done with the shopping for the whole week. This spares her time for the rest of the week, and it saves her money.
It’s Sunday, and the grocery stores are closed. Lillian and the family have been gone for the weekend, and when they come home, she needs to make a meal. When she opens the fridge, there is not much to cook with. Lillian gets a little confused and is not sure on what to make with what is left. She picks up her phone, and gladly the app knows what groceries she has. And gives her a great and healthy recipe to use the ingredients she has left. This makes Lillian feel good, because usually she would have thrown away the ingredients, she can’t use - and spend money on an expensive take away dinner.
Next up is Marcus. These are Marcus’s goals:
- Save money on food.
- Use everything he buys.
- Make meals for many days.
- Freeze meals.
It is at the end of the month, and the student money Marcus gets is running short. He understands that he has to shop smart and make one large meal for more days. Gladly he has an app that helps he plan. He notes down in the app how much money he got to spend, how many days the food need to last and that he is only him eating. The app helps him plan a shopping list based on his notes, it even helps him go to the right store to get the best prizes on the grocery’s! This helps Marcus to actually save some money till next month!
Marcus opens the fridge and doesn’t feel very creative. He has a lot of ingredients but does not know what to do with them. But he knows he want to use the meat that he haves. He therefore goes to his app. The app reflects he’s fridge, since he has been good at registing what he has. He selects the meat, and then the app comes up with many recipes based on the ingredients he has! The recipe also says he needs to use he’s cheese. But the cheese has a little bit mold on the side of it, so he doesn’t know if he can use the rest of it. Happily, he’s app can help him there as well, by giving him tips on how to know if you can it the product.
Problem- and vision statement
To create an app or a website, you need to think about the requirements for creating it. The product’s requirements simply explain what the product is, and what it should do. And it is a process based on all the research that has already been done. The first thing I will do, based on earlier research is to make a problem statement and a vision statement. To creating them I will be using the 5W technique:
What is the problem?
The problem is that people today are throwing away too much food and cause too much food waste.
Who is experiencing the problem?
Every person in Norway.
When does the problem occur?
Every day, all the time.
Where does the problem occur?
At people’s homes and where they eat and shop.
Why does the problem occur?
Because many people don’t have time to plan meals, or the ability to plan meals based on few ingredients and also doesn’t remember what they have already bought. Therefore, they are shopping more food, and throwing away the old grocery’s. And also, because people struggle to know if groceries are good or bad after a while.
Problem statement:
People withing the Norwegian household throw away too much food and causes to much food waste. This is because they struggle to plan meals, using all the food they have and remembering what they already have while shopping. They also struggle to understand if a grocery is useable or not.
Vision statement:
People withing the Norwegian household throw away too much food and causes to much food waste. This is because they struggle to plan meals, using all the food they have and remembering what they already have while shopping. They also struggle to understand if a grocery is useable or not. Our solution should deliver a new app that will create the user’s everyday life easier. By helping them not waste food, planning their shopping/meals and making them find reducing food waste a fun activity. The app should be able to help them to improve and achieve their wanted goals in a simple and efficient way. It should also look modern and adapt different target groups.
3. Ideation
Next up I made an ideation workshop. This is to generate ideas and to be sure to cover all the requirements we need for this app to function the best possible way. I gathered a team to help me during the ideation phase. This is to gather even more ideas and thought about the application.
Pretending its magic
I wanted to try an ideation technique to begin with that I have read about in “Cooper, Alan. About Face (p. 115). Wiley.”, which is called: Pretending its magic. If your personas have goals and the product has magic powers to meet them, how simple could the interaction be? This kind of thinking is useful in helping designers think outside the box. So, this way we could find different requirements that are needed in the app. I asked my team two just think of an app, and if it could do anything, they want. What do they want it to do! I set the timer to 15 minutes, and we wrote down as many ideas as we could on post-its and hung them on the wall. Afterwards we used dotting to decide what ideas we wanted to keep.
Brainstorming
Next up I created a brainstorming session, and I wanted to focus on the requirements based on the session we did before. I set the timer to 20 minutes for each requirement category, to generate as many ideas as possible. I wanted everything we could come up with written down, and then we will talk through it afterwards. And select the requirements we thought would be necessary.
Requirements
Data requirements
The data requirements should cover what my primary personas need when interacting with the app in terms of information or data. The kind of data we as users are looking for. So, these are the requirements I have listed based on their needs:
Sharing data with familymembers.
Give the user recipes based on likes. And also, on what the user has in the fridge.
The users should be able to register what food they buy and have in the fridge.
The app should connect with other apps.
Tips and tricks based on likes
Feed with recipes based on likes.
User should be able to register a budget they want shopping lists and recipes based on.
Weekly meal planner based on users’ choices
Able to edit choices and wants
Able to give tips about expired foods
Give alerts if something is bought a while ago and should be used - then what to use it for
Turn on and of alerts after what user wants
GPS. So that the app can see offers in store nearby.
Inspiration data
Recipes
Contextual requirements
The contextual requirements refer to determent how best to communicate with the users through the interface. How will the user engage with the product? As soon as an app is opened, its purpose should be clear, and the next step should always be obvious.
Device: The app has to be easy to use on the phone. But it should also be able to connect with a smartwatch and also a smart device, such as a google home. So the users can talk to their smart device to for example add things to their lists.
UI: The interface should adapt the user. There will be many different groups of people using this app. It must be able to be different after what the user needs and wants. It is also very important that the app is universally designed to fit every target group. No matter disabilities.
Time/day: The app should get to know the user. The alerts will appear when it suits the user best. For example, the app knows that the user usually shops food after work on Monday. So then it will alert the user with the shopping list right before this.
Dashboard: The user should be able in an easy way decide what parts of the app she/he is interested in. And it will then create a personalized dashboard at the start of the app.
Voice: Using a touchscreen or a device while doing daily task can often be a struggle. Your hands may not be free, or you are doing an activity that makes it hard for you to pick up the phone to write. It should be possible to talk to the app to add details to the data in the app. Either through phone, watch or another smart Device.
Functional requirements
The functional requirements refer to what the persona needs the app to do, so that they can reach their goals.
Shopping list: Creating shoppinglist, and being able to co-create shoppinglist.
Mealplanner: A meal planner that will help the user plan meals for a whole week (or more).
Budget: The user need a budgetplanner connected to the shopping list an meal planner.
Meal preferences: Noticing shopping habits, grocery preferenses and meal preferenses so the app can give tips based on that.
Viritual fridge: So that they can see what their fridge contain.
Technical requirements
To decide the technical requirements, you should talk closely to a technical team that is working on the project. They have more in-depth knowledge of technical aspects. But these are a few requirements that is needed to consider:
Software choices: mobile (iOS and android) and it is also going to work on smartwatches and other smart devices, such as google home.
UI: It is going to be a large app, that will be needing a lot of coding. But it does also need to look polished. The UI is going to look good, and the app should meet the personas mental model and be easy to use. So, the development needs a lot of consideration.
Account / Signup: Users are going to need a personalized site with log in. They shall have the opportunities to log in through e-mail and Facebook.
Content: The app needs a dashboard that is personalized for the user. The user will have the opportunity to decide what is important for them in the app, and therefore the desktop will mirror their needs.
User profile: Every user will have their own profile with their personal needs and information. They also will be able to connect with other users to share virtual fridge and shopping list.
Search: The user should be able to search in free text within the app. This to find recipes and tips.
Calendar: Calendar is important so that the user can do their weekly meal planning. And also register shopping.
Messaging: Should be able to massage family member you are connected to.
Dates & location: A simple GPS so the app can understand which stores is close to give right offers.
Billing & eCommerce: This app is going to cost. There is no doubt. Therefor we will be needing subscription plans. The app should mostly be free features, but you can subscribe to get even more! Then we will also need payment processing.
Admin, Feedback & Analytics: We will be needing CMS Integration, Usage Analytics, Crash Reporting, Performance Monitoring and Multilingual Support.
External APIs and Integrations: Here we will be needing to connect to one or more third party services. This is because the app will be used on different smart devices and connect to other apps. We also need an API for others to integrate with your app.
Security: Security is important. The users should feel that their information is safe, and also due to GDPR. So we do need SSL Certificate based Security and DoS protection.
Information architecture
Information architecture, or IA, is the structure for app that allows the user to understand how to use the product and where they can find the information they are looking for. It dictates the user flow and user experience. I got a lot of help from what me and the team came up with in the early ideation and in the requirements. So this is my sketch for Information architecture diagram:
As you can see in my information structure above, a lot of the pages connect together. One page can lead to another page. Here is an example of a user flow:
Wireframe Ideation stage
Now it is time to ideate even more. The goals of the ideation stage are to generate ideas, that potentially inspires newer and better ideas to solving the challenge. I start with Sketch storming; creating low fidelity design layouts that are quick to make and cheap to make. For creating wireframes for the website, i need to make at least 3 to 5 different wireframes of each stage so that I can choose the best one. I need to keep an open mind to find new, and great solutions. Therefore, I decided to do sketch storming.
Sketch storming
I gathered the team i used in the early ideation stage, and set the timer for 45 minutes, to skecth different wireframes for the website. Our sketches where very rough, just to try out different scenarios and ways the site would move. They looked like this:
4. Prototype
Low-fidelity wireframes
In the Wireframe ideation stage, me and my team discussed and found out what worked and what not worked in the sketches that we made. We also combined elements from each other’s sketches. One thing we were made sure of is that this app is going to be complicated. There are many different key-tasks within the app. So, it is important to make the UI as simple as possible, and to consider peoples mental models as much as possible. Especially because this is going to work as a app to help their everyday life to become easier, as well as reducing food waste.
After a lot of talking, we decided to create the low-fidelity wireframes together, on a drawing tablet. This way we could easier make them quickly, change them quickly and collaborate. This is how they turned out:
Design principles
In the storm sketching in the ideation phase, we sketched a lot of different ways to structure the design. But we noticed that the best way to do this app was to separate the different parts of the app. An instead connected them through a menu, that can resemble a website menu.
While creating the low-fidelity wireframes i also found a lot of different scenarios on the page where the information structure should be well thought about. How things are shown on the page, why and how to make it easily for the user to use. The app should most definitely not create any frustration, since the whole point of the app is to make life kind of easier.
Motivational design - When people are motivated from the inside, they are more likely to reach their goals. This is because they are more engaged, focused, and interested. The people who are going to download this app, is motivated to change their habits. They want to get better at using their grocery’s, shopping better and save money. Therefore, one design Princip that I will be focusing on in this app, is motivational design. The motivational design can get users to do something on their own terms through encouragement from the interface. This can also be provided with positive colours and illustrations.
Excitement and positivity - A part of the motivational design Princip, I will also include excitement and positivity. When a user completes a task, or does anything at all in the app, the app will provide with encouraging and positive feedback. This will make the user feel motivated and happy with what they have done. And also make them want to return.
Meet the user’s needs - I will make sure of meeting the users need throughout the design. The dashboard in the app will be personalized after the users wants and needs. And also, the recipe. When the user log in, they will be quizzed about what is most important for them, and the dashboard will reflect that. The user can change this whenever they want. The app shall provide the user with what they need, not everything else. They can also set budget, family members, cuisine and other details to make for example the recipes reflect them better.
Easy to undo - When the users start using the app, they answer a question to make the app fit them best. But it should also be easy to change their needs!
Aesthetic and minimalist design - The UI is going to be relevant and only contain the information that the user needs.
Usability & Navigation - I have tried to make the navigationsystem in the app as simple as possible. It is a site that provide a lot of options, so it is important to make it easy to use.
Low-fidelity prototypes
Afterwards i created a low-fidelity-prototype of the wireframes, where i also connected the prototype to different pages, to see how the page would move when the user clicked on different buttons. When creating this i used the software Adobe XD. This is because then i can get people to test the page by making it clickable, and also they can comment on things if they feel like it inside the testlink.
Possible issues
After creating my prototype, I do see a few issues that may accour. This app has a lot of information, and a lot of different tasks you can do. And it may be hard to understand how you can do certain tasks as easy as possible. There are many ways to come to the different sites of the app. So I am curious to see with way the users choose.
I do think that the shopping list and the virtual fridge is going to be easy to understand for my users, but I am a little bit unsure on the meal planner section and its connections to the recipe section. Are people going to understand the site well enough? The recipes are going to look like any other recipe site they are used to already.
Recruiting users for testing
I recruited three og the people that I used early in my research to also test the prototype. This could be fun since they are quite different from each other, and to see if they actually think the site will help them. It’s also helpful that they have a tiny bit of insight from before as well.
Tasks for usability testing
Before conducting the usability testing, I wrote a script to myself with tasks that I will be giving the users. This is tasks that represent stages of the app that i need tested to get further. For example, where will they click while going through the site. Do they move differently? These are the scripts that I used:
Task 1:
Check your shopping list.
You notice that the list has milk, and you have bought milk. Check of milk.
Task 2:
You got an alert that your kids have commented on your shopping list. Find the comments.
You accept your child’s wish and go back to your list and adds the item.
Task 3:
Open your virtual fridge. As you scroll through your fridge items, you notice that you cheese is marked red. But you checked your cheese and considers it usable. Edit your cheese to mark orange.
Even if you know that the cheese you have left can be used, you also want to buy a new one. Add cheese to your list.
Task 4:
Check your meal plans for the week. You notice that you do not have a plan for Saturday. But you remember that you have saved a recipe for hamburger that you want that day. Edit Saturday and add the saved recipe hamburger.
These tasks will be given while using the site, so I will be able to see how they move within the site.
Usability testing
Next up; Do the testing. My testing method is session recording. I will be using the app Zoom where I have created workspaces and invited my testers to the workspace at different times. Then I will be sending them the prototype link that they will be using in the testing. I will make them share their screen, so that I can see how they move inside the website, and that I can also see their faces at the same time. Then I will be able to see their facial expressions as well. I will also make them talk to me during the session and telling me what they are doing and thinking while doing it.
This is also called CTA. And of course, I will be doing something called RP, which means that i will be asking following up questions if they do something interesting or unique, but I will ask the questions after the session is over. I do not want to stop the session by asking questions during it.
The session videos will be delivered with the assignment PDF (My testers want to be anonymous so I will not include their faces).
When I asked the testers after the sessions if they had any comments on the sites, any pain points or anything else I got these comments:
Session 1: I like the site. I really think I would have use for this. But maybe make the “back” button larger. I found it hard to see.
Session 2: I thought it worked fine. I liked that there were many buttons for the same things, so I could choose what was closest to me.
Session 3:
In the food planner section, I wanted to press the whole box, not just the edit button.
On the pop up, I needed to look good on the buttons. Because they were so similar.
I really loved the colours on the groceries! That would help a lot!
Is it possible to add my own recipes also?
I liked the fridge, but maybe a little hard to delete an item.
Results
After conducting the usability testing and watching my users try out the site. I learned that the current site has a lot of improvements that need to be taken care of. I also think that the meal planner and recipe section of the site need a new round of ideation. But these are my notes:
The children should be able to suggest an item to the shopping list that the administrators can accept or decline. If they accept, it will automatically add the item to the list. Then they don’t need to write the item down.
As said by a user; the back button must be larger.
Most of my users used the back button to navigate, and almost no one preferred the menu in the top. And one of them used the bottom menu. I do believe that more people will use the bottom menu when the icons are there. So that will be interesting to see when people test the high-fidelity prototype.
It is hard to delete items from the fridge. They have to edit the item to delete it. Maybe put in that when you swipe item-box to the left; you get a delete option? As it is in an email-app.
The conversation with the user must improve. The app should talk better and easier to the user.
The meal planner needs to be taken another look at. It feels a little complicated for the user.