Android support library v4 download

Note: The appcompat library has migrated into the AndroidX library, which is an Android Jetpack component. See it in use in the Sunflower demo app. This library adds support for the Action Bar user interface design pattern. This library includes support for material design user interface implementations. This library adds support for the CardView widget, which lets you show information inside cards that have a consistent look on any app.

These cards are useful for material design implementations, and are used extensively in layouts for TV apps. After you download the Android Support Libraries, this library adds support for the GridLayout class, which allows you to arrange user interface elements using a grid of rectangular cells.

For detailed information about the v7 gridlayout library APIs, see the android. In general, the APIs in the v7 mediarouter library provide a means of controlling the routing of media channels and streams from the current device to external screens, speakers, and other destination devices. The library includes APIs for publishing app-specific media route providers, for discovering and selecting destination devices, for checking media status, and more.

For detailed information about the v7 mediarouter library APIs, see the android. At this time, we recommend using the library only in connection with Google Cast. The v7 palette support library includes the Palette class, which lets you extract prominent colors from an image. For example, a music app could use a Palette object to extract the major colors from an album cover, and use those colors to build a color-coordinated song title card.

The recyclerview library adds the RecyclerView class. This class provides support for the RecyclerView widget, a view for efficiently displaying large data sets by providing a limited window of data items. The v7 Preference library adds support for interfaces, such as Preference. OnPreferenceChangeListener and Preference.

This library provides specific feature sets and can be included in your application independently from other libraries. This library adds support for the RenderScript computation framework. These APIs are included in the android. You should be aware that the steps for including these APIs in your application is very different from other support library APIs. For more information about using these APIs in your application, see the RenderScript developer guide.

This library adds support for the Fragment user interface pattern with the FragmentCompat class and additional fragment support classes. For more information about fragments, see the Fragments developer guide. Note: The v4 fragment library provides a Fragment class. The android. This package requires API level 17 or higher. The Gradle build script dependency identifier for this library is as follows:. This document discusses the current behavior as of August The technique described in this document is not part of the stable testing suite for Xamarin, so it could break in the future.

For further assistance, to contact us, or if this issue remains even after utilizing the above information, please see What support options are available for Xamarin? Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Contents Exit focus mode. How can I manually install the Android Support libraries required by the Xamarin. Support packages? Please rate your experience Yes No. Any additional feedback? Alternately, you can check which version of the Android Support Repository you currently have installed in the Android SDK Manager: If the version matches the one you need for the NuGet package, then you don't have to download anything new.

There are a few distinct uses for the support libraries. Backward compatibility classes for earlier versions of the platform is just one of them. Here is a more complete list of ways you can use the support libraries in your app:. Upon discovering this, you may wonder if you should use the framework version of the API or the support library equivalent.

Here are the guidelines for when you should use support library classes in place of Framework APIs:. Support Library classes that provide a compatible implementation of platform API classes may not be able to provide the full set of functionality available in the latest release, due to the limitations of the host device platform version. In these cases, Support Library classes are designed to degrade gracefully, and may not provide the all the functionality or data of the current, platform API.

For this reason, you should review the reference documentation for the library classes and methods you use, and thoroughly test on devices running the earliest version of the platform supported by your app.

Note: The support libraries do not provide equivalent classes and methods for each framework API. In some cases, you may need to wrap a framework method call with an explicit SDK version check and provide alternative code to handle methods not available on a device.

For more information on using version checks in your code, see Supporting Different Platform Versions. Some of the Support Library packages have package names to indicate the minimum level of the API they originally supported, using a v notation, such as the support-v4 package. Starting with Support Library version For this reason, when working with any recent release of the support library, you should not assume that the the v package notation indicates a minimum API support level. This change in recent releases also means that library packages with the v4 and v7 are essentially equivalent in the minimum level of API they support.

For example, the support-v4 and the support-v7 package both support a minimum API level of 14, for releases of the Support Library from The release version of the Support Library, such as The release version number indicates which version of the platform API it was built against, and therefore, what the most recent APIs may be included in this version of the libraries.

Specifically, the first section of the release version number, for example the 24 in version The release version level of the support library indicates it incorporates some features of that API level, but you should not assume it provides compatibility with all features released in the new platform API version.