Скачать или смотреть Understanding Why Android API 19 Can Use Functions Added by API 23

Discover how Android's compatibility libraries enable lower API levels to access newer framework functions. Learn about back-porting features and ensuring broader app compatibility.
---
This video is based on the question https://stackoverflow.com/q/63715823/ asked by the user 'Piper' ( https://stackoverflow.com/u/14212078/ ) and on the answer https://stackoverflow.com/a/63715930/ provided by the user 'Gavin Wright' ( https://stackoverflow.com/u/7434090/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Why can Android API 19 use the functions added by API 23

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Why Can Android API 19 Use Functions Added by API 23?

As an Android developer, have you ever stumbled upon a situation where functions introduced in a higher API version seem accessible in earlier versions? You’re not alone! A common point of confusion is when you find that methods introduced in higher API levels, such as API 23, can still be utilized in API 19. One example is the Drawable# setLayoutDirection function. Let’s dive into this topic and uncover the reasons behind this phenomenon.

The Problem Explained

At first glance, you might wonder how API 19 can access methods that are officially marked as part of API 23. This confusion often arises when inspecting the source code or browsing documentation where newer API features are outlined. You expect the method to be unavailable until you reach the specified API version, but that's not the case here.

The Solution: Compatibility Libraries

What Are Compatibility Libraries?

Google provides compatibility libraries, such as the Android Support Library and AndroidX, which are designed to help developers maintain functionality across different Android versions. These libraries back-port new features, allowing older platform versions to use certain capabilities introduced in later versions.

How Does Back-Porting Work?

Every time a new feature is added to the Android framework, Google ensures that much of this functionality is accessible on older versions through these compatibility libraries. Here’s how it breaks down:

New Framework Features: When Google releases a new Android version, they add new functions to the framework API.

Library Support: Developers using their older builds don't miss out on these enhancements, thanks to the support libraries. These libraries often contain implementations that mimic newer API features.

The Example: Drawable# setLayoutDirection

In our specific case of Drawable# setLayoutDirection:

On devices running API 23 or higher, the method is called directly through the Android framework's code.

For devices operating on API 19 or lower, this method is provided by the compatibility library. This allows applications to reference the method without running into version compatibility issues.

Key Takeaways

Understanding Compatibility: Knowing how compatibility libraries function is essential for developing cross-version applications.

Check for Availability: Always verify API compatibility when using specific methods, especially if you aim for broader device support.

Leverage the Libraries: Utilize the Android Support Library or AndroidX to ensure access to the latest features without limiting your app's user base to only the most recent Android versions.

Conclusion

In summary, the integration of compatibility libraries into the Android development ecosystem is a powerful advantage, allowing developers to continually provide new features across a range of devices. The case of Drawable# setLayoutDirection is just one instance where this functionality comes into play, demonstrating how you can take advantage of newer capabilities even when working with older API levels. Understanding these tools not only enhances your app's reach but also improves user experience across the board.