The digital age has brought a lot of practical advantages to the world. It brings new opportunities for creative individuals and organizations to thrive, but also brings about its own, unique set of challenges, especially in an era with multiple platforms and distribution channels for new applications and products.
This is why an API-first approach is a refreshing approach to developing products. The API-first approach makes an API the first interface built for an application. The approach forces people to build an API that provides high value to the target audience, before building a product on top of it. It enables developers and organizations to minimize product liability and failure, maximize value and prepare for future product success across different platforms and channels.

A big part of adopting the API-first mindset is design thinking. The OpenAPI Specification (formerly Swagger Specification) goes hand-in-hand with an API-first thinking. In this talk, we’ll cover what it realistically takes to actually adopt an API-first approach to building products from the API’s design, and how to position API design into your development workflow using the latest version of the OpenAPI Specification, OpenAPI 3.0