SDK

Almost every app ships with third-party SDKs alongside its own code. Common families include advertising and mediation, analytics, attribution, crash reporting, payments and subscriptions, push messaging, authentication, maps and customer support. Each one is added at build time and travels inside the app package.

That makes SDKs detectable. On Android, the code libraries and manifest entries inside an app package reveal which SDKs are present, and the declared permissions add context about what the app can access. AppMetis has SDK and permission data for about 3.18M apps, enough to see which tools each category relies on.

SDK data answers practical questions: which ad networks a competitor works with, which analytics stack a target account uses, which apps might switch from a rival SDK, and which third parties may handle user data. Read it with care. Detection shows that an SDK is present in the build, not that it is active or how heavily it is used, and some SDKs arrive bundled inside others. Store privacy disclosures, such as Apple's privacy labels and Google Play's Data safety section, rely on developers to declare what these SDKs collect. Browse adoption by SDK in the SDK directory.