Inspiration: Aditya ran into multiple situations where he experienced customers having to waste time either on the phone or in-person speaking to a waiter at a restaurant when requesting menu-items based on their individual dietary restrictions. Sage felt similarly about situations where carbohydrate information was needed, especially in regard to those with diabetes. Ray and Arya agreed that our cause was a meaningful one and joined our team in helping us bring the Allergy Avoider to life, and in the hands of those who need it most!

What it does: There are two user interfaces that we have built. One for the customer-side and another for the business-side. Initially, the business goes onto our website and tells us their business name, along with the items on their menu and the ingredients that go into making each menu-item. Afterwards, the customer logs into a different interface and inputs any dietary restrictions they may have. This could be anything from the fact that they are vegan and diabetic to being allergic to eggs and nuts. After getting the customer's query, our backend C++ code filters through our data on the server side to return the restaurant names, as well as the specific menu-items that suit their dietary restrictions!

How we built it: We used HTML/CSS/JavaScript for the front end, and C++ for the backend! We would also use some form of a SQL Database in practice but haven't implemented it just yet.

Challenges we ran into: We had trouble initially in figuring out how data will be transmitted to and from our webpage and backend server code. We had to do research on how JavaScript could communicate with C++ and create a pipeline through which data could be transmitted in JSON format.

Accomplishments that we're proud of: We created a working Webpage in under 8 hours including our backend logic coded out in C++! 2/4 of us knew nothing about HTML/CSS/JavaScript before this event, and 3/4 knew nothing about using JSON! We all came in with C++ knowledge and used that to our advantage in writing out our algorithm in what we wanted to achieve through our application!

What we learned: Coding for long hours is tough! Working in a team is fun! Making mistakes is good, because they help you see and approach problems in many ways you hadn't seen beforehand!

What's next for Allergy Avoider: We want to partner up with local restaurants and collect their menu items and ingredient data initially! Afterwards, we want to store this data in a SQL Database and invite potential customers to try our web application! We believe that what we have is very meaningful and will save both customers and restaurants countless hours in sorting through menus to find the right meal for the occasion! Lastly, we are helping connect customers & supporting local business in our community!

Share this project:

Updates