Survey Says Facebook API Has Most Headaches and Horror Stories

A survey of API experiences raised some of the largest problems developers encounter, including which companies cause them. The Facebook API was mentioned far and away more than any other in long-form answers to questions about headaches, horror stories and other issues while integrating with APIs. Also mentioned often were Google APIs and the Twitter API. While it should be noted that all three are also among the most popular for developers, there are lessons to be learned in mining the results of this survey put out to Hacker News readers.

Over 100 developers answered the nine question survey in June posted by photo aggregation service Trove. The full results are available from the Trove blog. While the survey had multiple choice questions to get at some generic issues, long-form answers (which received between 31 and 88 responses each) asked for more detail. That's where developers harped on specific companies.

"Facebook, Facebook, Facebook," one developer wrote in response to a question about horror stories. "They release half-baked stuff that doesn't work, shut down existing functionality without replacing it, and never document anything correctly."

Poor Documentation and changes to the API were the most common issues that developers noted, regardless of company. But Facebook definitely took the brunt of the attack. "Facebook continually alters stuff thus rapidly outdating my apps," one developer wrote.

Another was more succinct: "Facebook. Everything is broken."

Google also received its share of negative comments, though they were spread across several services. One developer mentioned the Google Buzz API, which did not launch with the service. Two more complained that the Google Plus API is not available.

While Twitter had a handful of negative comments, it also received almost as many positive comments, and more than any other service. "The Twitter documentation is top notch," one developer wrote.

The survey also asked how many services developers use. Nearly two-thirds of developers use three or more services, with a full third using between four and six. There were nine developers who typically use 11 or more services. Wow.

Interestingly, OAuth was also the subject of developer ire. It's being widely adopted as the go-to Authentication scheme, but that doesn't make it perfect. "It’s a standard that no one seems to be standardized on," one developer wrote. In fact, if we were to get really general with the survey results, you might say inconsistency and unpredictability are the two things that give developers the most headaches.

Be sure to check out the whole survey if you're into the details. And keep a look out for Trove's follow-up survey.

For those interested in our analysis, we've published our tally of long-form answers.

Be sure to read the next Surveys article: Survata’s Consumer Feedback API Helps Power Business Decisions