What is an SDK?

What an SDK provides

An SDK is the vendor's code running inside your application. It typically wraps an API, handles authentication, retries and offline queuing, and exposes a small set of methods your developers call.

The value is that you do not implement any of that yourself. The cost is that you are shipping someone else's code with the same privileges as your own.

What SDKs cost

• App size, which affects install conversion measurably in markets with constrained devices or connections.
• Startup time. SDKs initialising on launch delay the first screen, and several of them compound.
• Stability risk. A crash in a third-party SDK is a crash in your app, attributed to you.
• Privacy exposure. Data collected by an SDK is your disclosure obligation — see privacy manifests and Privacy Nutrition Labels.
• Maintenance. Every SDK is a dependency requiring periodic updates, and an outdated one is a security and compliance liability.

Managing them

The failure mode is accumulation. SDKs get added for a specific campaign, a vendor trial or a partner integration, and then nobody removes them. Apps routinely ship several SDKs for vendors no longer used.

Two habits prevent most of the damage. A named owner and a stated purpose for every SDK, reviewed periodically, with anything unowned removed. And keeping the measurement SDKs current specifically — SDK spoofing defences live in the SDK, so an outdated version is running old protections against current attacks.