Developing good APIs very much depends on building the right thing, and then building it right. This process requires a perspective on APIs that not just looks at them as technical capabilities, but as products that are designed with a clear idea of scenarios, use cases, and consumers. With such a more holistic approach, APIs can be designed in a way which makes it more likely that they will be used and reused.
In this video James Higginbotham, author of "Principles of Web API Design", presents his ADDR method. The method uses the four phases "Align", "Define", "Design", and "Refine", and provides seven steps along the way when moving through these phases. Typically consulting with large organizations, James' focus was to create a design process that is scalable, repeatable, and teachable. The goal is to enable as many teams throughout the organization to design and develop good APIs, and ADDR is one possible method to make this happen.
00:00 Introduction
00:10 Welcome Back James Higginbotham
00:21 The Principles of Web API Design
00:50 The Origin of ADDR
03:38 ADDR Phase #1: Align
04:41 ADDR Phase #2: Define
07:37 ADDR Phase #3: Design
09:32 Examples of Multiple APIs Designs for one API Definition
13:17 ADDR Phase #4: Refine
15:05 Closing the Cycle
17:03 Wrapping it up
20:04 API Developer Weekly