My Insights: This is a really good thread to freshen up strategies, patterns and best practices to drive the building of API-based products. Although APIs provide "encapsulation" and a way to expose capabilities of a business, they should (I would say must) be built based on the customer(s) that will use them, in true "product development" style. They are not "just a technical artifact for integration", even though this can also be a consequence. However, we should not be the sole driving factor, even if the goal is to enable integration.
Analysis & Summary
This Twitter thread by Stefan Tilkov raised a very interesting discussion on the rather common misuse of the “API-first“ strategy. In classic Stefan style, he comprehensively shows several interesting points and patterns where such misuse happens. Most prominently the overuse of this technique for "encapsulation" of technical capabilities within the "enterprise". This tends to be part of the mission of many Enterprise Architects, as a way to have a good governance model over the different "parts of the enterprise". However, if APIs are purely built "inside-out" (just as a way to encapsulate and expose business capabilities) and are not built as a product, i.e.: based on the needs of the customers/clients using it (and what they are looking for), it tends to lead to a mismatch of expectations.
At a given moment of the thread Simon Wardley shared a nice visualization of "types of developments" where APIs are strategic and how to start such initiatives using his famous Wardley maps.