Re:Twitter’s poor API documentation practices
by jenius on Monday January 09, 2012 @08:33PM
(#3445216)
I just recently was impressed by how nice looking their docs are and confused by how bad they are at actually explaining what to do with it, so I can certainly relate.
I think what they really need is to figure out what calls people make most often and mark those very clearly at the top, along with a human-readable description. Like for example "HERE'S THE CALL YOU CAN USE TO GET A USER'S TWEETS', or 'HERE'S THE ONE YOU USE TO GET TWEETS ABOUT WORD OR HASHTAG X' -- Isn't this the case for everything?
I think what they really need is to figure out what calls people make most often and mark those very clearly at the top, along with a human-readable description. Like for example "HERE'S THE CALL YOU CAN USE TO GET A USER'S TWEETS', or 'HERE'S THE ONE YOU USE TO GET TWEETS ABOUT WORD OR HASHTAG X' -- Isn't this the case for everything?