4 ms·
Ask HN : Facebook API vs Foursquare API?
Hi i'm wondering if one is building a location based service that needs signing in what's the better API to use? Foursquare or facebook?
I know when it comes to locations foursquare is better but they don't have that many users isn't it? So most people won't be able to use what we build from the API isn't it as when using facebook instead?
But then again if we use foursquare API with facebook login the service will ght API limits of foursquare cause we're using only one auth keys to to foursquare api than using many keys when allowing people to sign in from foursquare. What do you think?
Any idea on this
- jack9 14y agoAccording to my company's stats, Foursquare is far more popular than people would expect. It's a nontrivial number of people that exceeds instagram's traffic within our domain. This may be due to our domain or other factors (like we're one of the few to support foursquare). The Graph API is also quite confusing and returns rather inconsistent results...meaning the API is so vague as to what is to be returned, it's a whole subtask to parse and interpret what you get per request. On the other hand, foursquare is straightforward and far less disparate. Would it be so hard for foursquare to return valid json? Hey, you must quote your attribute tags, not just your values! Sheesh.