We came up with this idea when I realized that online ratings don't always accurately represent the true consumer belief of the restaurant.

What it does

Originally, We wanted to use Yelp API data to track ratings over time and identify trends in those ratings. We realized a few hours into the project how bad Yelp's API is. We ended up scratching all that we had done and start with Google's Place API.

As of submission, Ye-p uses Google's Place API and Walmart's Open API to search relevant businesses or products, graph the 5 most recent reviews over time and display other relevant data.

How I built it

We built it using HTML/CSS, Javascript, Ajax, Jquery, Bootstrap and a few other Javascript libraries. GitHub also helped us along the way.

Challenges I ran into

API's!! They are so much harder to work with than we initially anticipated. We were hoping to get a ton of data from multiple API's, but we ended up with just 3 different sources. A 4th API from BestBuy is in the works but will not be ready by submission time.

We also went through a number of different languages before deciding on Javascript. We started out with PHP, then switched to Python and Django, then finally to Javascript.

Our team also spent some time on figuring out hosting. We tried AWS and Heroku when we used Django. After we switched to javascript, developing locally over and syncing over GitHub made much more sense.

Accomplishments that I'm proud of

I am impressed with how little sleep I have gotten.

What I learned

I learned a lot. I had never worked with such complex API's before. I am by no means an expert now, but I understand how to work with them now. Ajax was also an unfamiliar system, and we are now well-versed in callbacks

What's next for Ye-p

We plan to expand API's and add more meaningful analytics. We also plan to build a database of review data that will aggregate data over time so that more than 5 reviews could be shown in the future.

Share this project: