An SDK (Software Development Kit) is a packaged collection of code, libraries, documentation, and tools that a developer integrates into an app to add a capability without writing it from scratch. In mobile growth, the SDK is the integration unit: when you "add AppsFlyer" or "add Firebase," you're embedding their SDK, which then collects events and talks to their servers.
Why every growth platform ships an SDK
- Attribution / MMPs ([[mmp]]) — the SDK records installs, sessions, and in-app events and attributes them to ad sources.
- Analytics — product analytics SDKs capture screen views, funnels, and custom events.
- Ad networks / mediation — ad SDKs request, render, and report on ads ([[ad-mediation]]).
- Monetization — subscription/paywall SDKs manage purchases and entitlements.
SDK bloat is the accumulated weight of too many SDKs: larger [[app-size]], slower builds, more crash surface, more third parties touching user data, and harder privacy compliance. Best practice is to keep the SDK stack lean and audit what each one collects.
SDK spoofing is a fraud technique where an attacker reverse-engineers the messages an SDK sends to its server and forges fake install/event traffic to steal attribution and ad spend — see [[ad-fraud]]. MMPs defend with signed, encrypted SDK communication and anomaly detection.