## Inspiration

The indecisiveness that groups encounter when trying to collectively decide on a place to get food.

## What it does

It decides on where a group can eat through an algorithm that chooses out of some preset criteria such price point, location, food inclusivity and more.

## How we built it

Frontend: React Native, Nativewind which formally was TailwindCSS
Backend: python, MongoDB, MindsDB
Backend tools: Azure

## Challenges we ran into

As far as tales have been told and hackathons have ran, we fell down to the good old deployment stage.

## Accomplishments that we're proud of

This was the first hackathon for one member of our team. Kudos for staying 2 nights for the very first hackathon.

## What we learned

For the first time, we explored the idea AND pursued our idea of creating a mobile app.

The importance of being on the same page because it has left a lot of problems down the road. We realized that some had different ideas/perspectives of implementing certain parts that would just not be feasible to combine all.

## What's next for Tender

There are many cross-paths to where Tender can lead to. Tender was a product after much pivoting. During the process of thinking, coding and submitting Tender, there have been numerous thoughts that have been passed by just by the sheer stress of finishing within the time crunch. Our immediate goal would be to produce a fully working demo of what our app could achieve by integrating the different parts of the application that everyone worked on. We also hope to add more features and refinements that we did not have the capacity to entertain during the hackathon itself.
## Inspiration

Our inspiration came from the very real and pressing issue of choosing where to eat as a group. Everyone has experienced the endless back-and-forth that occurs when a group of indecisive friends try to decide on a restaurant. We wanted to create a solution that not only makes this process effortless but also fun and engaging for everyone involved.

## What it does

MunchMatch simplifies the dining decision-making process for groups by matching their collective preferences with local dining options. Users input their individual preferences, dietary restrictions, and budget, and our app does the rest — compiling a list of restaurant matches that satisfy the group's criteria. Its democracy meets gastronomy, ensuring that the final choice is one that everyone can get excited about.

## How we built it

We built MunchMatch using a combination of React Native for cross-platform support to deploy on both iOS and Android platforms, and Node.js and Express/MongoDB for the backend, which handles user data and preferences and integrates with various APIs for real-time data. We focused on a seamless and intuitive UI/UX to make the process as straightforward as possible.

## Challenges we ran into

As with any great hack, there was no shortage of challenges we ran into as we progressed throughout the hackathon. We spent a long time in the ideation phase (around 24 hours!) going back and forth between ideas we'd want to work on and challenges we were interested in. Once we did begin work, the biggest challenges were setting up all our different environments to work with the code, learning new languages and frameworks in the time we had left, working with the Google Maps API, and integrating - connecting the back and front end.

## Accomplishments that we're proud of

We were able to create a functional and good-looking app in the short amount of time we had to code, as well as work on mobile development and languages that we were not familiar with before. We also had a great time hacking, meeting new people, and attending workshops!

## What's next for MunchMatch

There are endless possibilities for future development - we could improve the app itself, particularly the UI and UX to make it more functional and easier to use. We can also add the ability to save restaurants and specify cuisines and preferences that a user may have, as well as potential allergies. The other route we could go down is integration within other apps, specifically delivery apps when a large number of people may be delivering food or create extensions for group messaging platforms such as iMessage or WhatsApp that may further increase the number of people our app helps.
Team channel #43
Team discord users - Sarim Zia #0673,
Elly #2476,
(ASK),
rusticolus #4817,
Names -
Vamiq,
Elly,
Sarim,
Shahbaaz

## Inspiration

When brainstorming an idea, we concentrated on problems that affected a large population and that mattered to us. Topics such as homelessness, food waste and a clean environment came up while in discussion. FULLER was able to incorporate all our ideas and ended up being a multifaceted solution that was able to help support the community.

## What it does

FULLER connects charities and shelters to local restaurants with uneaten food and unused groceries. As food prices begin to increase along with homelessness and unemployment we decided to create FULLER. Our website serves as a communication platform between both parties. A scheduled pick-up time is inputted by restaurants and charities are able to easily access a listing of restaurants with available food or groceries for contactless pick-up later in the week.

## How we built it

We used React.js to create our website, coding in HTML, CSS, JS, mongodb, bcrypt, node.js, mern, express.js . We also used a backend database.

## Challenges we ran into

A challenge that we ran into was communication of the how the code was organized. This led to setbacks as we had to fix up the code which sometimes required us to rewrite lines.

## Accomplishments that we're proud of

We are proud that we were able to finish the website. Half our team had no prior experience with HTML, CSS or React, despite this, we were able to create a fair outline of our website. We are also proud that we were able to come up with a viable solution to help out our community that is potentially implementable.

## What we learned

We learned that when collaborating on a project it is important to communicate, more specifically on how the code is organized. As previously mentioned we had trouble editing and running the code which caused major setbacks.

In addition to this, two team members were able to learn HTML, CSS, and JS over the weekend.

## What's next for us

We would want to create more pages in the website to have it fully functional as well as clean up the Front-end of our project. Moreover, we would also like to look into how to implement the project to help out those in need in our community.