# Project export: MealPrep

This document was generated by HackStack to give an AI agent context about a hackathon project. Sections are labeled with their provenance; content marked as truncated was cut to keep this document small.

## Project metadata

- Hackathon: Cal Hacks 11.0
- Tagline: In a generation of young adults that are becoming increasingly in-need of healthy meals to cook, introducing MealPrepMealPrep is a user-centric platform for streamlining the process of meal prepping
- Devpost: https://devpost.com/software/mealprep
- GitHub: not linked
- Demo: https://mealprep-hazel.vercel.app/
- Video: https://www.youtube.com/embed/VNZguZ76Ru0?enablejsapi=1&hl=en_US&rel=0&start=&version=3&wmode=transparent
- Team: contributor stats unavailable

## Devpost submission (written by the team)

### Inspiration

Our team wanted to address the growing concern for young adults and college students who are becoming increasingly dependent on food-delivery services like DoorDash and UberEats. This creates unhealthy habits of eating, which will scale into an unfavorable lifestyle in the future. For convenience's sake, we wanted to build a custom user-centric platform that is simple enough that even the least culinary-inclined could embrace the process of preparing a meal that you find delicious.

### What it does

MealPrep gathers dishes from the keywords of your choice, steps you through the process of cooking with a voice-dictated AI chatbot, and bookmarks your favorite foods for next time.

### How we built it

Built with React.js on the frontend, supported by Vite.js and Tailwind.css, packaged with Node.js, and deployed to Vercel. On the backend, we're using Javascript with Firebase user-authentication and Firestore to store user bookmarks. Our user experience is derived from Groq.AI's lightning responsive LLM responses, as well as Cartesia AI's voice-to-text dictation.

### Challenges we ran into

Attempting to deploy on industry-standard technologies like AWS / Docker Trying to integrate Linter in a CI/CD pipeline using GitHub Actions Adding/removing data using Firestore

### Accomplishments we're proud of

Creating a unified user-interface that reflects our values and simplistic, modern product vision. Adding dynamic animations that create a smooth navigational experience. Having integrated many technologies that all overlap with each other, consistently researched the docs to see what works best for our code. In the end, our technologies all fit together like a beautiful piece of the puzzle.

### What we learned

API's are difficult to implement and wrangle around, and sometimes diving too deep into one solution isn't the most optimal workflow. Always remember to think of different solutions and take yourself outside of the box sometimes. Having a cycle of communication, delegating tasks, and single-focus times worked well for our team's productive workflow. It felt like mini-sprints which organized and allowed us to adapt to our own roles on the team. Taking a step back from coding to brainstorm, draw out our ideas, and have fun with the process is so important to the team's cohesive vision. It allows us to remain on the same page.

### What's next

Features like ingredient overlap detection would focus on giving the users a way to see which of their favorite recipes can be built using the same ingredients. Engagement is an important factor for any platform. To add engagement, we want to focus on shifting our platform to social media. Features like a daily popular meal, or community postings where people can share their experiences and advice on meal-prepping would be a fantastic addition. On top of our default guides, we want there to be more interactivity with guides created by users and brands. Speaking of brands, having companies promote their meal-prep-friendly products on our page would be a great monetization strategy.

## README (from the GitHub repository)

No README available.

## Detected evidence (automated analysis)

No repository was indexed for this project. Claimed technologies below could not be checked against code.
- Express (technology) — claimed on Devpost, not found in the code
- Firebase (technology) — claimed on Devpost, not found in the code
- React (technology) — claimed on Devpost, not found in the code
- Tailwind CSS (technology) — claimed on Devpost, not found in the code
- Vercel (technology) — claimed on Devpost, not found in the code

## Codebase structure

No repository index available.

## Key source files

No repository index available; no source files included.