The Android Support Library is not actually a single library, but rather a collection of libraries that can roughly be divided into two groups: compatibility and component libraries. For details, please see Understanding the Android Support Library.

support newer Android features on older Android versions.

library to reduce the number of nested views needed.

AndroidX library to position top-level application widgets, such as AppBarLayout and FloatingActionButton.

a static library that you can add to your Android application in order to use APIs that are either not available for older platform versions or utility APIs that aren't a part of the framework APIs.

bind UI components in your layouts to data sources in your app using a declarative format.

core library to enable emoji compatibility in Kitkat and newer devices to avoid the empty emoji characters.

AndroidX library to encapsulate part of the user interface or behavior into reusable components.

perform actions in response to a change in the lifecycle status of another component, such as activities and fragments.

a library to build interactive settings screens without needing to interact with device storage or manage the UI.

AndroidX library that enables libraries to prepopulate ahead of time compilation traces to be read by ART.

display large sets of data in your UI while minimizing memory usage.

AndroidX library to implement a straightforward, performant way to initialize components at app startup.

Provides a stable but relatively compact binary serialization format that can be passed across processes or persisted safely.

entry point for Fido (Fast IDentity Online) APIs.

library to check basic device integrity and CTS Profile match. Part of Google Play Services.

Google Mobile Services in terms of the Android library refers to Google Play Services, a proprietary background service and API package for Android devices which is not part of the Android Open Source Project (AOSP). The library does not contain those services (i.e. it usually requires the Google Framework, often referred to as „GApps“, being installed on the device), but allows an app to communicate with them. Be aware this usually goes along with transferring at least parts of your personal data to the Google network.

library to help with material design guidelines.

a FLOSS (Free/Libre Open Source Software) framework to allow applications designed for Google Play Services to run on systems, where Play Services is not available.

a mechanism to serialize objects on the Android platform into Parcelables version-agnostic.

a mechanism to serialize objects on the Android platform into Parcelables version-agnostic.

a mechanism to serialize objects on the Android platform into Parcelables version-agnostic.