Does your API suck? Okay, that one needs a little explanation.<\/p>\n
If you’ve developed an API, it exposes some functionality to users. It might suck to learn. The documentation might be unclear and the function signatures counter-intuitive. It might suck to use, doing a lot of things, but never particularly what you really need, right now.<\/p>\n
After a great deal of working with companies developing new API functionality, and also building out demo material from publicly available APIs (starting with the thought “this should be easy …”) I have developed some opinions on the subject. Just like a restaurant that doesn’t pay attention to detail, an awkward API can have a dozen small things that add up to a big problem. Misplaced silverware, a long wait time, a slow waiter, details wrong on the order … no one of these will make you want to stand up and leave, but put together, they’ll make sure you never come back.<\/p>\n