API Design

In the API space, everybody is talking about REST. But really, why should APIs be RESTful? Great products are designed with rigorous customer focus, a deep understanding of the customers, their needs and desires. And with these ingredients, great customer

APIs are often built according to the ideas of the API provider without considering the needs and wishes of potential API consumers. Investing time and energy in building an API that no one wants is a waste of resources. It

I have heard the question “Why do I need OpenAPI, Swagger or RAML?” so many times, that I finally decided to sit down and write about it. Once an API has been designed, it needs to be communicated to team members,

To design great APIs, we first need to realize, that APIs are in fact products. APIs are products that are offered on a market to satisfy the needs of a group of customers. This means that APIs are not individually

In the API space, everybody is talking about REST. But really, why should APIs be RESTful? Great products are designed with rigorous customer focus, a deep understanding of the customers, their needs and desires. And with these ingredients, great customer

The first thing we see as users of a new web application is typically its user interface. This is why user-interface design is so important for web applications. Now, user interface design is for web applications, what API frontend design

After 1.5 years of work, I now have an answer to one of the most common questions I get: What are the best practices for RESTful API Design? My answer to the question can be found the recently released RESTful