"I never actually know if I'm getting a good deal anymore..."
While enjoying some free pizza, we began to discuss the struggles of being broke students in New York City.
"The food is good, but it's also really expensive."
"How much is too much for good food?"
"Bad food is cheap food and that's all that matters."
There are countless websites to check out food in your area, but they're all missing a critical element: a comparison with other local restaurants to determine if the food is a good value.
What it does
Bytes compares the ratings and cost of a restaurant to other restaurants around you to help you get the best food for your money. Bytes, taking into account cost/rating ratio of local restaurants, calculates a score and assigns a letter grade determining the quality of the deal. The higher the score, the better the deal!
How we built it
Back-end dependencies: Requests, BeautifulSoup, NumPy, SciPy, GeoPy
Challenges we ran into
Making the front end was challenging because none of us actually knew how to do it or had any real experience with that. The greatest challenge by far has been using Flask to tie the front and back ends together, with the largest obstacle being getting user input into the back end.
Accomplishments that we're proud of
The front end came out very nicely considering our lack of previous experience. At present, Bytes is extensible (to hotels, attractions, and other things under the TripAdvisor and Yelp APIs), and it is good at error handling. Being able to learn new APIs quickly is a skill we gladly continue to improve upon. We are also proud of the idea we used for rating the restaurants: it makes sense, is efficient, and is something other than coding that we came up with.
What we learned
What's next for Bytes
Bytes, in its current state, works very efficiently for finding local deals on food. However, this behavior could easily be extended to other areas such as hotels, attractions, and other things. Adding other features such as displaying menus, having user accounts to allow users to save favorites and view eating history, share recommendations with friends, etc. Bytes could also (in a non-evil way) collect data about its users, using this information to improve user experience and perhaps even local food options. Most importantly, cleaning up the integration between the front and back ends using Flask would be great (as in do it right this time).