## Inspiration

From housewives to students, they all face a common problem - meal planning and preparation. Therefore, we decided to test our technological skills by creating an AI recipe builder with your own ingredients!

## What it does

We created a form field to let users select all their available ingredients in their fridge, from leftover chicken to basic ingredients like eggs and flour, our app would find the best recipe. Vegan, lactose intolerance or a specific allergy? We got you covered. Our app lets users specify what they don't want to have in their dish, heck even the amount of calories they can intake in their meal. Select a variety of Main dishes, Side dishes, Desserts, or other meal types suitable for your needs.

## How we built it

We utilize an API from RapidAPI and build our app completely in React and TailwindCSS with the help of Axios. The design process was done on Figma, GitHub for version control, and Railway for deployment and implementation.

## Challenges we ran into

We mostly ran into useEffect and useHook implementation issues in React due to the lack of our lack of knowledge. Using Routing for passing objects around pages was definitely a challenge for us, too. Lastly, we went from Merge conflict to conflict in real life where we tried to modify the same function at the same time.

## Accomplishments that we're proud of

Our web app is fully functional, with a clean home-made design. Our team has to work interdisciplinarily to push the project on time. We were most proud of the fact that this app we would use daily since meal prepping for us students can sometimes be troublesome.

## What we learned

A team leader would make a huge difference in any project - who would ensure which one works on which and would not conflict with each other. Git can sometimes be a double-edged knife, we would need to tread carefully.

## What's next for Gustus

One feature we would need to implement is to create a meal plan for the whole week, with an automatically generated shopping list for grocery trips. Currently, our database supports 1000 food and drink ingredients and we plan to expand more.
## Inspiration

We wanted a way to promote a healthy diet and lifestyle during these trying times and we thought a great way to start that was to cook your own food instead of having take out.

## What it does

It's tinder but for recipes; you either like a recipe and we save it for you or you pass on it and we will remember to exclude it next time

## How we built it

We used Googles Firebase to hold our user data such as the recipes they've liked and the ones they've passed on, as well as a recipe API to obtain recipes from, and we used Java on Android Studio for the front end

## Challenges we ran into

Learning development on Android using Java for the first time for the majority of our group members along with implementing best practices for android such as MVVM and using the most optimal method for the problem was difficult to digest at the start.

## Accomplishments that we're proud of

Having a working project, learning and implementing MVVM architectural pattern, trying out best.

## What we learned

We learned how to use information from an API and present it on an application for consumers. It was a good learning experience working with firebase and experimenting with what android studio has to offer.

## What's next for Chef Swipe

Since the API we use limits the number of calls we may perform, we hope to invest in a plan that would allow for more usage. We were not able to create tags that would filter through what recipes would appear on the application for each specific profile and we hope to implement that in the future.
## Inspiration

We love cooking and watching food videos. From the Great British Baking Show to Instagram reels, we are foodies in every way. However, with the 119 billion pounds of food that is wasted annually in the United States, we wanted to create a simple way to reduce waste and try out new recipes.

## What it does

lettuce enables users to create a food inventory using a mobile receipt scanner. It then alerts users when a product approaches its expiration date and prompts them to notify their network if they possess excess food they won't consume in time. In such cases, lettuce notifies fellow users in their network that they can collect the surplus item. Moreover, lettuce offers recipe exploration and automatically checks your pantry and any other food shared by your network's users before suggesting new purchases.

## How we built it

lettuce uses React and Bootstrap for its frontend and uses Firebase for the database, which stores information on all the different foods users have stored in their pantry. We also use a pre-trained image-to-text neural network that enables users to inventory their food by scanning their grocery receipts. We also developed an algorithm to parse receipt text to extract just the food from the receipt.

## Challenges we ran into

One big challenge was finding a way to map the receipt food text to the actual food item. Receipts often use annoying abbreviations for food, and we had to find databases that allow us to map the receipt item to the food item.

## Accomplishments that we're proud of

lettuce has a lot of work ahead of it, but we are proud of our idea and teamwork to create an initial prototype of an app that may contribute to something meaningful to us and the world at large.

## What we learned

We learned that there are many things to account for when it comes to sustainability, as we must balance accessibility and convenience with efficiency and efficacy. Not having food waste would be great, but it's not easy to finish everything in your pantry, and we hope that our app can help find a balance between the two.

## What's next for lettuce

We hope to improve our recipe suggestion algorithm as well as the estimates for when food expires. For example, a green banana will have a different expiration date compared to a ripe banana, and our scanner has a universal deadline for all bananas.