Adopting an API-First Approach
@API Summit, Austin
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. 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 approach.
In this talk, I 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.
Presented on June 13, 2018.
Understanding and Executing on API Developer Experience
Developer experience (DX) is an extension of general User Experience, which emphasizes the developer, and their experiences working your API. A good API developer experience goes beyond technical writing. In this talk, I speak about what it means to have an API with good Developer Experience by understanding the types of API consumers and their journey from discovery to API integration, and how OpenAPI Spec/Swagger Spec can help in improving general API DX with great documentation.
Delivering in the Digital Age, Fidelity @ Ireland
An API First Approach with Swagger
I spoke at Fidelity's internal conference about the importance of the API First approach. The API First approach puts your API front and center in your product strategy. With the mass adoption and standardization of the OpenAPI Specification (formerly called the Swagger Specfication) as the de facto REST based API description format of the world, the focus has shifted to design quality and speed in an organization’s API development strategy.
In this session, I detailed what is the OpenAPI Specification (OAS), how it started from a humble open source API project to the REST industry standard for defining APIs, what it means to develop an API using the OAS, and provided information on leveraging the powerful Swagger tooling ecosystem.
Presented on October 5, 2017.
Serverless infrastructure is gaining popularity by the day, with AWS Lambda leading the way forward for the future of Serverless engineering. AWS Lambda and the API Gateway has also had a profound impact on how developers and organizations think about their API development, consumption and maintenance. In this talk, I discuss Serverless architecture, understand why developers should develop APIs and applications in this framework, and detail how AWS Lambda, API Gateway and the OAS work together for holistic API design development and management.
Treating APIs as Products
APIs can no longer be treated as regular tech artifacts, and instead should be treated with the same attention and planning as any first-class product. This is why a product management approach is important to harness the true potential of an API offering and offer a compelling service which internal and external developers can’t live without. In this talk, I detailed a step-by-step framework on how to plan, prioritize and execute on your API product strategy when embarking on the journey towards a successful API that's provides real consumer value and drives adoption.