Enterprise Integration Zone is brought to you in partnership with:

Mitch Pronschinske is a Senior Content Analyst at DZone. That means he writes and searches for the finest developer content in the land so that you don't have to. He often eats peanut butter and bananas, likes to make his own ringtones, enjoys card and board games, and is married to an underwear model. Mitch is a DZone Zone Leader and has posted 2574 posts at DZone. You can read more from them at their website. View Full User Profile

The Secrets of Awesome JavaScript API Design

08.17.2013
| 2379 views |
  • submit to reddit

It doesn't take long for most developers to sniff out a poorly-designed JavaScript API. Within minutes of reading about or coding against a new library, most developers can intuit whether their long-term relationship with that library will be a pleasant or unfortunate one. While documentation, buzz and other factors certainly play into that conclusion, the largest influencer of that snap conclusion is the "feel" of the API itself. APIs are developer UX: A good one raises a developers enjoyment; a bad one sends it plummeting.

As developers, we know what good and bad JavaScript APIs "feel" like, and yet we struggle with designing the kind of APIs that we enjoy using. But principles of good JavaScript API design do exist, and it's possible to extract them from several key libraries in the the proliferating JavaScript landscape. In this article, Brandon Satrom will do exactly that, digging into the design aspects of popular libraries like jQuery, Backbone, Modernizer, Kendo UI and others to enumerate the designed-in qualities of these libraries that make them not only popular, but a pleasure to use.

-- YouTube Page