You could build a bookshelf from raw planks. Or you could buy a flat-pack kit with every part, the right screws and an instruction booklet.
You could build a bookshelf from raw wood: measure, cut, sand and drill. Or you could buy a flat-pack kit: every part cut to size, the right screws and a picture-by-picture booklet.
An SDK is that flat-pack kit for building with a service. It’s a bundle of ready-made code and instructions that makes it much easier to build an app that works with a particular service.
What’s usually in the box
- ready-made code for the common jobs
- instructions and examples
- tools for testing
Examples
Payment companies offer SDKs so shops can take card payments. AI companies offer SDKs so apps can talk to their models. Apple and Google offer SDKs for building iPhone and Android apps.
What it isn’t
It isn’t the service itself. The SDK is the kit. It still talks to the service, usually through its API.
Where the comparison breaks down
A bookshelf kit stays the same once built. SDKs get updated. Apps need updating to keep up.
How the words fit together
An SDK wraps an API. To your project, it’s just another dependency.
An SDK usually wraps a service's API, so developers write one line instead of twenty.

When you'll hear it
“Use their SDK.” Use the ready-made kit the company provides, rather than building everything yourself.
“Is there a Python SDK?” Is there a kit for building with this service in the Python language?
“Update the SDK.” Get the latest version of the kit, which may fix problems or add features.
“Is there an official SDK for this, so we're not building and maintaining the connection ourselves?”

