Open ghost opened 9 years ago
I am going to be looking at Yelp API
I found Google Places API and I think it's exactly what we need. It lets us look at points of interest around us using various filters and categories. It also has an add places feature which lets an app add places that aren't already there to Google's Places database.
Does that add it to to Google Place's database. Since things we would have later might be a time constraint thing, we probably don't want to add it to the Google Database?
It also lets us add events which expire after a certain time. Besides, realistically speaking, we didn't have enough time to implement custom events by making our own servers and databases and stuff. So I think the Places API is a lifesaver
Would that show it on the other Google API users then or just ours? Otherwise, sounds great
It would show it to everyone who uses Google Places API. I don't see why we should close off the events we add from our app to just our users. Especially since we are not making a real proprietary app.
I think the question then would be what makes us different from the Google Maps app.
Google Maps itself doesn't show all the places around you unless you specifically search for a particular product. Our app will let users look at possible places they want to visit in their vicinity by specifying various parameters such as categories, price, etc. We can also let them add these places and events to their calendars. Also, Google Maps itself doesn't let anyone add places to the Map unless you visit a particular website and have a Places account and then verify each place. Maps is a map and navigation app first and foremost. Whereas our app will be about places of interest.
Make a Different Issue for each API you want to use.
Restaurants/ Food, Concerts, Movies, Theatre, Tourist Attractions
Start Off with a event class, build categories based on that, and then individual events