Needs a description.
SDKs
Experiences
Products
I keep pushing teams to think of their APIs as products. When you treat an API like a product, you start thinking about who uses it, what they need, and how to make the whole thing sustainable.
Onboarding
I see teams dealing with massive friction during onboarding. If a consumer can't get from zero to their first successful API call in minutes, you've already lost them. Getting started guides, sandb...
Simplicity
I am a big believer that the best APIs are the simple ones. When I see overly complex API designs, I know someone was thinking about their internal architecture instead of the consumer. Keep the su...
Self-Service
Self-service is the goal I keep pushing teams toward. If a consumer can't find your API, sign up, get keys, and make their first call without emailing someone, you've created a bottleneck that will...
Velocity
Velocity matters because the business side isn't going to wait around. I see the gap between what the business needs and what API teams can deliver growing wider, and without repeatable processes a...
Developer Experience
Developer experience is the thing I'm most passionate about across the API landscape. Poor docs, missing examples, inconsistent patterns, and no tooling -- these are the things that make developers...
Policies
Getting Started SDKs
Including SDKs in your getting started flow gives consumers a head start. Pointing them to client libraries and code they can use right away removes a lot of friction from onboarding.
CSharp
Having a CSharp SDK available for each API means .NET developers can get up and running quickly. Meeting consumers where they are with their language of choice reduces friction.
SDKs (Getting Started)
Including SDKs in your getting started flow gives consumers a head start. Pointing them to client libraries and code they can use right away removes a lot of friction from onboarding.
Go
A Go SDK gives consumers building in Go a native way to interact with the API. Language-specific SDKs are how you lower the barrier to entry across different developer communities.
Java
Java SDKs are essential for reaching enterprise developers. Having a well-maintained Java client library shows that you take the enterprise segment of your consumer base seriously.
JavaScript
JavaScript SDKs cover both browser and Node.js consumers. Given how much of the web runs on JavaScript, having a solid SDK here is practically mandatory for broad adoption.
PHP
PHP still powers a massive portion of the web. Having a PHP SDK available means you are not leaving a large segment of potential API consumers behind.
SDKs
SDKs are how you meet developers where they are. Handling authentication, wrapping operations, and supporting multiple programming languages reduces the effort consumers need to get value from your...