Expanding The Scope Of Your API
In development, the term full stack – familiarity with multiple programming languages for both frontend and backend development – is thrown around pretty regularly. Full spectrum is one that’s used from time to time, and may be a better way to describe the techniques required for superior API practice. Read more
An API is a method of communication. At best it’s a tool to make building software easy, but at worse a time-waster and constant hassle. Good APIs abstract complexity and quickly provide clear valuable data, whereas bad APIs abstract too much, don’t allow for any customization, or aren’t clear and therefore are difficult to use. Read more
Developer experience is a vital component of API design. The best developer experience will result in a better, stronger, more useful API, and by extension, a better, stronger, more useful end user experience.
While developer experience is very much a subjective thing that is highly dependent on the developer consumer, there are nonetheless some recurring positive elements that successful APIs with good experience share. Read more
API metrics are perhaps the single most important factor in improving any API system. Metrics are inherently valuable – tracking data on API usage, availability, uptime, and other insights is pivotal to keeping a consistently healthy platform. That being said, it’s an unfortunate truth that many developers do not leverage API analytics to their full power, simply preferring to consider metrics a business tool, and little else. Read more
We’ve been in the API game for a little while now, and we’ve seen our fair share of compelling developer communities being cultivated. On the flipside, we’ve also seen some epic fails. At our 2016 Platform Summit, Shayne Parmelee, developer experience lead at Shopify, talked about some of his own successes (and failures) during his time with the company. Read more