Tracking: The application tracks and reports your activity to somewhere – usually either without your consent, or by default (i.e. you’d have to actively disable it). It’s commonly used for when developers obtain crash logs without the user’s consent, or when an app is useless without some kind of authentication.

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.

Constraint Layout Library (Utility)

library to reduce the number of nested views needed.

AppCompat (Utility)

support newer Android features on older Android versions.

Androidx Core (Utility)

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.

androidx.legacy (Utility)

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.

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.

a set of core libraries that includes new collection types (such as multimap and multiset), immutable collections, a graph library, functional types, an in-memory cache, and APIs/utilities for concurrency, I/O, hashing, primitives, reflection, string processing, and much more.

specifies a means for obtaining objects in such a way as to maximize reusability, testability and maintainability compared to traditional approaches such as constructors, factories, and service locators (e.g., JNDI). This process, known as dependency injection, is beneficial to most nontrivial applications.

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.

Constraint Layout Library (Utility)

library to reduce the number of nested views needed.

AppCompat (Utility)

support newer Android features on older Android versions.

Androidx Core (Utility)

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.

androidx.legacy (Utility)

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.

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.

a set of core libraries that includes new collection types (such as multimap and multiset), immutable collections, a graph library, functional types, an in-memory cache, and APIs/utilities for concurrency, I/O, hashing, primitives, reflection, string processing, and much more.

specifies a means for obtaining objects in such a way as to maximize reusability, testability and maintainability compared to traditional approaches such as constructors, factories, and service locators (e.g., JNDI). This process, known as dependency injection, is beneficial to most nontrivial applications.

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.

Constraint Layout Library (Utility)

library to reduce the number of nested views needed.

AppCompat (Utility)

support newer Android features on older Android versions.

Androidx Core (Utility)

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.

androidx.legacy (Utility)

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.

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.

a set of core libraries that includes new collection types (such as multimap and multiset), immutable collections, a graph library, functional types, an in-memory cache, and APIs/utilities for concurrency, I/O, hashing, primitives, reflection, string processing, and much more.

specifies a means for obtaining objects in such a way as to maximize reusability, testability and maintainability compared to traditional approaches such as constructors, factories, and service locators (e.g., JNDI). This process, known as dependency injection, is beneficial to most nontrivial applications.