Android 14 introduces great new features and APIs for developers. The sections below help you learn about features for your apps and get started with the related APIs.
For a detailed list of new, modified, and removed APIs, read the API diff report. For details on new APIs visit the Android API reference — new APIs are highlighted for visibility. Also, to learn about areas where platform changes may affect your apps, be sure to check out Android 14 behavior changes for apps that target Android 14 and for all apps.
Internationalization
Per-app language preferences
Android 14 expands on the per-app language features that were introduced in Android 13 (API level 33) with these additional capabilities:
Automatically generate an app's
localeConfig
: Starting with Android Studio Giraffe Canary 7 and AGP 8.1.0-alpha07, you can configure your app to support per-app language preferences automatically. Based on your project resources, the Android Gradle plugin generates theLocaleConfig
file and adds a reference to it in the final manifest file, so you no longer have to create or update the file manually. AGP uses the resources in theres
folders of your app modules and any library module dependencies to determine the locales to include in theLocaleConfig
file. See Automatic per-app language support for more information and leave feedback.Dynamic updates for an app's
localeConfig
: Use thesetOverrideLocaleConfig()
andgetOverrideLocaleConfig()
methods inLocaleManager
to dynamically update your app's list of supported languages in the device's system settings. Use this flexibility to customize the list of supported languages per region, run A/B experiments, or provide an updated list of locales if your app utilizes server-side pushes for localization.App language visibility for input method editors (IMEs): IMEs can utilize the
getApplicationLocales()
method to check the language of the current app and match the IME language to that language.
Grammatical Inflection API
3 billion people speak gendered languages: languages where grammatical categories—such as nouns, verbs, adjectives, and prepositions—inflect according to the gender of people and objects you talk to or about. Traditionally, many gendered languages use masculine grammatical gender as the default or generic gender.
Addressing users in the wrong grammatical gender, such as addressing women in masculine grammatical gender, can negatively impact their performance and attitude. In contrast, a UI with language that correctly reflects the user's grammatical gender can improve user engagement and provide a more personalized and natural-sounding user experience.
To help you build a user-centric UI for gendered languages, Android 14 introduces the Grammatical Inflection API, which lets you add support for grammatical gender without refactoring your app.
Regional preferences
Regional preferences enable users to personalize temperature units, the first day of the week, and numbering systems. A European living in the United States might prefer temperature units to be in Celsius rather than Fahrenheit and for apps to treat Monday as the beginning of the week instead of the US default of Sunday.
New Android Settings menus for these preferences provide users with a
discoverable and centralized location to change app preferences. These
preferences also persist through backup and restore. Several APIs and
intents—such as
getTemperatureUnit
and
getFirstDayOfWeek
—
grant your app read access to user preferences, so your app can adjust how it
displays information. You can also register a
BroadcastReceiver
on
ACTION_LOCALE_CHANGED
to handle locale configuration changes when regional preferences change.
To find these settings, open the Settings app and navigate to System > Languages & input > Regional preferences.


Regional preferences screen in Android system settings
Temperature options for regional preferences in Android system settings
Accessibility
Non-linear font scaling to 200%
Starting in Android 14, the system supports font scaling up to 200%, providing low-vision users with additional accessibility options that align with Web Content Accessibility Guidelines (WCAG).
To prevent large text elements on screen from scaling too large, the system applies a non-linear scaling curve. This scaling strategy means that large text doesn't scale at the same rate as smaller text. Non-linear font scaling helps preserve the proportional hierachy between elements of different sizes while mitigating issues with linear text scaling at high degrees (such as text being cut off or text that becomes harder to read due to an extremely large display sizes).
Test your app with non-linear font scaling

If you already use scaled pixels (sp) units to define text sizing, then these additional options and scaling improvements will be applied automaticaly to the text in your app. However, you should still perform UI testing with the maximum font size enabled (200%) to ensure that your app applies the font sizes correctly and can accommodate larger font sizes without impacting usability.
To enable 200% font size, follow these steps:
- Open the Settings app and navigate to Accessibility > Display size and text.
- For the Font size option, tap the plus (+) icon until the maximum font size setting is enabled, as shown in the image that accompanies this section.
Use scaled pixel (sp) units for text-sizes
Remember to always specify text sizes in sp units. When your app uses sp units, Android can apply the the user's preferred text size and scale it appropriately.
Do not use sp units for padding or view heights: with non-linear font scaling sp dimensions might not be proportional, so 4sp + 20sp might not equal 24sp.
Convert scaled pixel (sp) units
Use
TypedValue.applyDimension()
to convert from sp units to pixels, and use
TypedValue.deriveDimension()
to convert pixels to sp. These methods apply the appropriate non-linear scaling
curve automatically.
Avoid hardcoding equations
using
Configuration.fontScale
or
DisplayMetrics.scaledDensity
.
Because font scaling is now non-linear, these fields are no longer accurate.
User experience
Sharesheet custom actions and improved ranking
Android 14 updates the system sharesheet to support custom app actions and more informative preview results for users.
Add custom actions
With Android 14, your app can add custom actions to the system sharesheet it
invokes. To customize actions with sharesheets, create your custom
ChooserAction
using
ChooserAction.Builder
and specify a list of your ChooserActions
as the
Intent.EXTRA_CHOOSER_CUSTOM_ACTIONS
of the Intent
created with
Intent.createChooser
.

Improve ranking of Direct Share targets
Android 14 uses more signals from apps to determine the ranking of the direct
share targets to provide more helpful results for the user. To provide the
most useful signal for ranking, report the shortcut usage by calling
pushDynamicShortcut
with a corresponding shortcut when user sends a message
to a contact, and attach the corresponding capability
"actions.intent.SEND_MESSAGE" to that shortcut by calling
ShortcutInfoCompat.Builder#addCapabilityBinding("actions.intent.SEND_MESSAGE")
.
Support for built-in and custom animations for Predictive Back
Android 13 introduced the predictive back-to-home animation behind a developer option. When used in a supported app with the developer option enabled, swiping back shows an animation indicating that the back gesture exits the app back to the home screen.
Android 14 includes multiple improvements and new guidance for Predictive Back:
- You can set
android:enableOnBackInvokedCallback=true
to opt in to predictive back system animations per-Activity instead of for the entire app. - We've added new system animations to accompany the back-to-home animation from Android 13. The new system animations are cross-activity and cross-task, which you get automatically after migrating to Predictive Back.
- We've added new Material Component animations for Bottom sheets, Side sheets, and Search.
- We've created design guidance for creating custom in-app animations and transitions.
- We've added new APIs to support custom in-app transition animations:
handleOnBackStarted
,handleOnBackProgressed
,handleOnBackCancelled
in
OnBackPressedCallback
onBackStarted
,onBackProgressed
,onBackCancelled
in
OnBackAnimationCallback
- Use
overrideActivityTransition
instead ofoverridePendingTransition
for transitions that respond as the user swipes back.
With this Android 14 preview release, all features of Predictive Back remain behind a developer option. See the developer guide to migrate your app to predictive back, as well as the developer guide to creating custom in-app transitions.
Improvements for app stores
Android 14 introduces several new
PackageInstaller
APIs that
allow app stores to improve their user experience.
Request install approval before downloading
Installing or updating an app may require user
approval.
For example, when an installer making use of the REQUEST_INSTALL_PACKAGES
permission attempts to install a new app. In prior Android versions, app stores
can only request user approval after APKs are written to the install
session and the session
is
committed.
Starting with Android 14, the
requestUserPreapproval()
method lets installers request user approval before committing the install
session. This improvement lets an app store defer downloading any APKs until
after the installation has been approved by the user. Furthermore, once a user
has approved installation, the app store can download and install the app in the
background without interrupting the user.
Claim responsibility for future updates
The new
setRequestUpdateOwnership()
method allows an installer to indicate to the system that it intends to be
responsible for future updates to an app it is installing. This capability
enables update ownership enforcement, meaning that only the update
owner
is permitted to install automatic updates to the app. Update ownership
enforcement helps to ensure that users receive updates only from the expected
app store.
Any other installer, including those making use of the INSTALL_PACKAGES
permission, must receive explicit user approval in order to install an update.
If a user decides to proceed with an update from another source, update
ownership is lost.
Update apps at less-disruptive times
App stores typically want to avoid updating an app that is actively in use because this leads to the app's running processes being killed, which potentially interrupts what the user was doing.
Starting with Android 14, the
InstallConstraints
API gives installers a way to ensure that their app updates happen at an
opportune moment. For example, an app store can call the
commitSessionAfterInstallConstraintsAreMet()
method to make sure that an update is only committed when the user is no longer
interacting with the app in question.
Seamlessly install optional splits
With split APKs, features of an app can be delivered in separate APK files,
rather than as a monolithic APK. Split APKs allow app stores to optimize the
delivery of different app components. For example, app stores might optimize
based on the properties of the target device. The
PackageInstaller
API has
supported splits since its introduction in API level 22.
In Android 14, the
setDontKillApp()
method allows an installer to indicate that the app's running processes
shouldn't be killed when new splits are installed. App stores can use this
feature to seamlessly install new features of an app while the user is using the
app.
Detect when users take device screenshots
To create a more standardized experience for detecting screenshots, Android 14 introduces a privacy-preserving screenshot detection API. This API lets apps register callbacks on a per-activity basis. These callbacks are invoked, and the user is notified, when the user takes a screenshot while that activity is visible.
Graphics
Paths are now queryable and interpolatable
Android's Path
API is a powerful and
flexible mechanism for creating and rendering vector graphics, with the ability
to stroke or fill a path, construct a path from line segments or quadratic or
cubic curves, perform boolean operations to get even more complex shapes, or all
of these simultaneously. One limitation is the ability to find out what is
actually in a Path object; the internals of the object are opaque to callers
after creation.
To create a Path
, you call methods such as
moveTo()
,
lineTo()
, and
cubicTo()
to add path segments. But there has been no way to ask that path
what the segments are, so you must retain that information at creation time.
Starting in Android 14, you can query paths to find out what's inside of them.
First, you need to get a
PathIterator
object using the
Path.getPathIterator
API:
Kotlin
val path = Path().apply { moveTo(1.0f, 1.0f) lineTo(2.0f, 2.0f) close() } val pathIterator = path.pathIterator
Java
Path path = new Path(); path.moveTo(1.0F, 1.0F); path.lineTo(2.0F, 2.0F); path.close(); PathIterator pathIterator = path.getPathIterator();
Next, you can call PathIterator
to
iterate through the segments one by one, retrieving all of the necessary data
for each segment. This example uses
PathIterator.Segment
objects, which packages up the data for you:
Kotlin
for (segment in pathIterator) { println("segment: ${segment.verb}, ${segment.points}") }
Java
while (pathIterator.hasNext()) { PathIterator.Segment segment = pathIterator.next(); Log.i(LOG_TAG, "segment: " + segment.getVerb() + ", " + segment.getPoints()); }
PathIterator
also has a non-allocating version of next()
where you can pass in
a buffer to hold the point data.
One of the important use cases of querying Path
data is interpolation. For example,
you might want to animate (or morph) between two different paths. To further simplify
that use case, Android 14 also has a new
interpolate()
method on Path
.
Assuming the two paths have the same internal structure, the interpolate()
method creates a new Path
with that interpolated result. This example
returns a path whose shape is halfway (a linear interpolation of .5)
between path
and otherPath
:
Kotlin
val interpolatedResult = Path() if (path.isInterpolatable(otherPath)) { path.interpolate(otherPath, .5f, interpolatedResult) }
Java
Path interpolatedResult = new Path(); if (path.isInterpolatable(otherPath)) { path.interpolate(otherPath, 0.5F, interpolatedResult); }
The Jetpack graphics-path library, now available in alpha, enables similar APIs for earlier versions of Android as well.
Core functionality
OpenJDK 17 updates
Android 14 continues the work of refreshing Android's core libraries to align with the features in the latest OpenJDK LTS releases, including both library updates and Java 17 language support for app and platform developers.
The following features and improvements are included:
- Updated approximately 300
java.base
classes to Java 17 support. - Text Blocks, which introduce multi-line string literals to the Java programming language.
- Pattern Matching for instanceof, which allows an object to
be treated as having a specific type in an
instanceof
without any additional variables. - Sealed classes, which allow you restrict which classes and interfaces can extend or implement them.
Thanks to Google Play system updates (Project Mainline), over 600 million devices are enabled to receive the latest Android Runtime (ART) updates that include these changes. This is part of our commitment to give apps a more consistent, secure environment across devices, and to deliver new features and capabilities to users independent of platform releases.
Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.