EasyGreen

Problem

As me and my partner have grown, we've seen a trend in the behavior of our peers. In our community, once students reach highschool, they start to care more about their physical characteristics whether it's beauty, weight, or physique. However, one shared concern amongst all these characteristics is the factor of diet. Some individuals, not just students, aim to eat more, and some aim to eat less. It doesn't stop there however, things become more complicated when specific nutrients are thrown into the equation: carbs, sugars, protein, dairy, and more. In addition, with the dominance of social media in our daily lives, its easy for the community to get confused or led to believe false information regarding proper diet. This can potentially lead to unwanted physiques long term or possibly even harmful and dangerous improper diets.

Our Solution

The solution me and my partner came up with is an AI program that takes in the user's goals, restrictions, and health to come up with a schedule that tends to the specific needs of the user. The output from the AI is specifically built to be simple and easy to understand while being credible with ratings out of 100 to show how suggested the AI is with certain meals/meal plans. Also, the AI will provide summarized bullets of why a meal was suggested and links to recipes online as a quality of life feature to prevent the user of searching through many online recipes. EasyGreen has the potential to significantly benefit the community since its a more direct way of finding meals instead of searching the vast depths of social media platforms. In addition the ratings out of 100 allow the user to not only help find the most fitted meals but also lets them decide if they should make the meal.

How We Built It

Me and my partner divided this project in 2 ways. One would have one of us do the frontend of the website and the other would do the backend of the website. This allowed for a better result since we both share different sets of skills. The frontend is made up of a standard html, CSS, and J.S., structure while the backend was made with the python coding language. The second division was the actual website having a main page, a intake page, and finally a meal plan page. We decided that the main page would be entirely html and CSS since the information would largely just be explaining the functionality and purpose of the website. It was also a good place to establish the credibility of the program. The intake and results page were both made in similar ways (just separate files) of the main page. Since an API key did cost money, we decided to create a default mock results page to demonstrate what the basic premise of the results page would show.