Android api level 23 download

This revision allows for more drawing features in ADT and fixes several bugs in the previous rendering library. It also unlocks several editor features that were added in ADT Fixes an issue with the visual layout editor rendering library that prevented Android 3. Android Studio. Download What's new User guide Preview. Features overview Release notes. Android Developers. This is required to compile your app for that version.

Several System Image packages. At least one of these is required to run that version on the Android Emulator. The Sources for Android package. This includes the source files for the platform. Android Studio may show lines of code from these files while you debug your app. Revision 1 August Released to stable channel no longer in preview.

Android 8. Revision 1 December Released to stable channel no longer in preview. Revision 2 August Released to stable channel no longer in preview. Android 7. Revision 3 December Incremental update. Your app must be running on a compatible device with a fingerprint sensor. You must implement the user interface for the fingerprint authentication flow on your app, and use the standard Android fingerprint icon in your UI.

To see an app implementation of fingerprint authentication, refer to the Biometric Authentication sample. On Windows, you may have to run telnet Your app can authenticate users based on how recently they last unlocked their device. This feature frees users from having to remember additional app-specific passwords, and avoids the need for you to implement your own authentication user interface.

Your app should use this feature in conjunction with a public or secret key implementation for user authentication. To set the timeout duration for which the same key can be re-used after a user is successfully authenticated, call the new setUserAuthenticationValidityDurationSeconds method when you set up a KeyGenerator or KeyPairGenerator.

Avoid showing the re-authentication dialog excessively -- your apps should try using the cryptographic object first and if the timeout expires, use the createConfirmDeviceCredentialIntent method to re-authenticate the user within your app. This feature allows you to associate an app with a web domain you own.

Based on this association, the platform can determine the default app to use to handle a particular web link and skip prompting users to select an app. To learn how to implement this feature, see Handling App Links. Auto Backup for Apps The system now performs automatic full data backup and restore for apps. Your app must target Android 6. If users delete their Google accounts, their backup data is deleted as well.

To learn how this feature works and how to configure what to back up on the file system, see Configuring Auto Backup for Apps. This release provides you with APIs to make sharing intuitive and quick for users. You can now define direct share targets that launch a specific activity in your app.

These direct share targets are exposed to users via the Share menu. This feature allows users to share content to targets, such as contacts, within other apps. For example, the direct share target might launch an activity in another social network app, which lets the user share content directly to a specific friend or community in that app.

To enable direct share targets you must define a class that extends the ChooserTargetService class. Declare your service in the manifest. The following example shows how you might declare the ChooserTargetService in your manifest. This release provides a new voice interaction API which, together with Voice Actions , allows you to build conversational voice experiences into your apps. Call the isVoiceInteraction method to determine if a voice action triggered your activity.

If so, your app can use the VoiceInteractor class to request a voice confirmation from the user, select from a list of options, and more. Most voice interactions originate from a user voice action.

A voice interaction activity can also, however, start without user input. For example, another app launched through a voice interaction can also send an intent to launch a voice interaction. To determine if your activity launched from a user voice query or from another voice interaction app, call the isVoiceInteractionRoot method. If another app launched your activity, the method returns false. Your app may then prompt the user to confirm that they intended this action.

To learn more about implementing voice actions, see the Voice Actions developer site. This release offers a new way for users to engage with your apps through an assistant. Building intelligent escalation chains for modern SRE. Featured on Meta. Now live: A fully responsive profile. Reducing the weight of our footer. Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled.

Accept all cookies Customize settings. Steven Murawski Principal Cloud Advocate. Zachary Deptawa Cloud Advocate. Martina Director of Product Management. Learn more about Azure DevOps. Azure DevOps Feature Timeline.