Descripción general de las funciones y API

Android 14 incluye excelentes funciones y APIs para desarrolladores. La siguiente información te ayudará a obtener información sobre las funciones de tus apps y a comenzar a usar las APIs relacionadas.

Para obtener una lista detallada de las APIs agregadas, modificadas y quitadas, consulta el informe de diferencias de API. Para obtener detalles sobre las APIs agregadas, consulta la referencia de la API de Android. En el caso de Android 14, busca las APIs que se agregaron en el nivel de API 34. Para conocer las áreas en las que los cambios de la plataforma podrían afectar a tus apps, asegúrate de revisar los cambios en el comportamiento de Android 14 para apps orientadas a Android 14 y para todas las apps.

Internacionalización

Preferencias de idioma de las apps

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 the LocaleConfig 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 the res folders of your app modules and any library module dependencies to determine the locales to include in the LocaleConfig file.

  • Dynamic updates for an app's localeConfig: Use the setOverrideLocaleConfig() and getOverrideLocaleConfig() methods in LocaleManager 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.

API de Grammatical Inflection

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.

Para ayudarte a compilar una IU centrada en el usuario para idiomas con inflexión de género, Android 14 introduce la API de Grammatical Inflection, que te permite agregar compatibilidad con el género gramatical sin refactorizar la app.

Preferencias regionales

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.

Accesibilidad

Escalamiento de fuente no lineal al 200%

A partir de Android 14, el sistema admite el escalamiento de fuente hasta el 200%, lo que les brinda a los usuarios con visión reducida opciones de accesibilidad adicionales que se alinean con las Pautas de Accesibilidad al Contenido Web (WCAG).

Para evitar que los elementos de texto grandes en la pantalla escalen demasiado, el sistema aplica una curva de escalamiento no lineal. Esta estrategia de escalamiento implica que el texto grande no escala a la misma velocidad que uno más pequeño. El escalamiento de fuente no lineal ayuda a preservar la jerarquía proporcional entre elementos de diferentes tamaños, a la vez que mitiga los problemas con el escalamiento lineal de texto en grados altos (como el texto cortado o el texto que se vuelve más difícil de leer debido a su gran tamaño de visualización).

Prueba tu app con escalamiento de fuente no lineal

Habilita el tamaño máximo de fuente en la configuración de accesibilidad de un dispositivo para probar tu app.

Si ya usas unidades de píxeles ajustados (sp) para definir el tamaño del texto, estas opciones adicionales y mejoras de escala se aplican automáticamente al texto de tu app. Sin embargo, debes realizar pruebas de la IU con el tamaño máximo de fuente habilitado (200%) para asegurarte de que tu app aplique los tamaños de fuente correctamente y pueda adaptarse a tamaños de fuente más grandes sin afectar la usabilidad.

Para habilitar el tamaño de la fuente al 200%, sigue estos pasos:

  1. Abre la app de Configuración y dirígete a Accesibilidad > Tamaño y texto de la pantalla.
  2. En la opción Tamaño de fuente, presiona el ícono de signo más (+) hasta que se habilite la configuración de tamaño máximo de fuente, como se muestra en la imagen que acompaña esta sección.

Usa unidades de píxeles ajustados (sp) para los tamaños de texto

Recuerda siempre especificar los tamaños de texto en unidades de sp. Cuando tu app usa unidades de sp, Android puede aplicar el tamaño de texto preferido del usuario y escalarlo de forma adecuada.

No uses unidades de sp para el padding ni definas alturas de las vistas suponiendo padding implícito: con el escalamiento de fuente no lineal, las dimensiones de sp podrían no ser proporcionales, por lo que 4 sp + 20 sp podría no ser igual a 24 sp.

Convierte unidades de píxeles ajustados (sp)

Usa TypedValue.applyDimension() para convertir unidades de sp en píxeles y TypedValue.deriveDimension() para convertir píxeles en sp. Estos métodos aplican automáticamente la curva de escalamiento no lineal adecuada.

Evita codificar la ecuación mediante Configuration.fontScale o DisplayMetrics.scaledDensity. Como el escalamiento de fuente no es lineal, el campo scaledDensity ya no es preciso. El campo fontScale debe usarse solo con fines informativos, porque las fuentes ya no se escalan con un solo valor escalar.

Usa unidades de sp para lineHeight

Define siempre android:lineHeight con unidades de sp en lugar de dp para que la altura de la línea se escale junto con el texto. De lo contrario, si tu texto es sp, pero tu lineHeight está en dp o px, no se escala y parece apretado. TextView corrige automáticamente el lineHeight para que se conserven las proporciones previstas, pero solo si textSize y lineHeight se definen en unidades sp.

Cámara y contenido multimedia

Ultra HDR para imágenes

An illustration of Standard Dynamic Range (SDR) versus High Dynamic Range (HDR) image quality.

Android 14 adds support for High Dynamic Range (HDR) images that retain more of the information from the sensor when taking a photo, which enables vibrant colors and greater contrast. Android uses the Ultra HDR format, which is fully backward compatible with JPEG images, allowing apps to seamlessly interoperate with HDR images, displaying them in Standard Dynamic Range (SDR) as needed.

Rendering these images in the UI in HDR is done automatically by the framework when your app opts in to using HDR UI for its Activity Window, either through a manifest entry or at runtime by calling Window.setColorMode(). You can also capture compressed Ultra HDR still images on supported devices. With more colors recovered from the sensor, editing in post can be more flexible. The Gainmap associated with Ultra HDR images can be used to render them using OpenGL or Vulkan.

Zoom, enfoque, vista posterior y mucho más en las extensiones de cámara

Android 14 upgrades and improves camera extensions, allowing apps to handle longer processing times, which enables improved images using compute-intensive algorithms like low-light photography on supported devices. These features give users an even more robust experience when using camera extension capabilities. Examples of these improvements include:

Zoom en el sensor

Cuando REQUEST_AVAILABLE_CAPABILITIES_STREAM_USE_CASE en CameraCharacteristics contiene SCALER_AVAILABLE_STREAM_USE_CASES_CROPPED_RAW, tu app puede usar capacidades avanzadas de sensores para otorgar los mismos píxeles a una transmisión RAW recortada los mismos píxeles que el campo visual completo mediante CaptureRequest con un objetivo RAW que tenga el caso de uso de transmisión establecido en CameraMetadata.SCALER_AVAILABLE_STREAM_USE_CASES_CROPPED_RAW. Cuando se implementan los controles de anulación de solicitudes, la cámara actualizada les brinda a los usuarios control de zoom incluso antes de que estén listos otros controles de la cámara.

Audio USB sin pérdida

Android 14 gains support for lossless audio formats for audiophile-level experiences over USB wired headsets. You can query a USB device for its preferred mixer attributes, register a listener for changes in preferred mixer attributes, and configure mixer attributes using the AudioMixerAttributes class. This class represents the format, such as channel mask, sample rate, and behavior of the audio mixer. The class allows for audio to be sent directly, without mixing, volume adjustment, or processing effects.

Productividad y herramientas para desarrolladores

Credential Manager

Android 14 adds Credential Manager as a platform API, with additional support back to Android 4.4 (API level 19) devices through a Jetpack Library using Google Play services. Credential Manager aims to make sign-in easier for users with APIs that retrieve and store credentials with user-configured credential providers. Credential Manager supports multiple sign-in methods, including username and password, passkeys, and federated sign-in solutions (such as Sign-in with Google) in a single API.

Passkeys provide many advantages. For example, passkeys are built on industry standards, can work across different operating systems and browser ecosystems, and can be used with both websites and apps.

For more information, see the Credential Manager and passkeys documentation and the blogpost about Credential Manager and passkeys.

Health Connect

Health Connect is an on-device repository for user health and fitness data. It allows users to share data between their favorite apps, with a single place to control what data they want to share with these apps.

On devices running Android versions prior to Android 14, Health Connect is available to download as an app on the Google Play store. Starting with Android 14, Health Connect is part of the platform and receives updates through Google Play system updates without requiring a separate download. With this, Health Connect can be updated frequently, and your apps can rely on Health Connect being available on devices running Android 14 or higher. Users can access Health Connect from the Settings in their device, with privacy controls integrated into the system settings.

Users can get started using Health Connect without a separate app download on devices running Android 14 or higher.
Users can control which apps have access to their health and fitness data through system settings.

Health Connect includes several new features in Android 14, such as exercise routes, allowing users to share a route of their workout which can be visualized on a map. A route is defined as a list of locations saved within a window of time, and your app can insert routes into exercise sessions, tying them together. To ensure that users have complete control over this sensitive data, users must allow sharing individual routes with other apps.

For more information, see the Health Connection documentation and the blogpost on What's new in Android Health.

Actualizaciones de OpenJDK 17

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.

Mejoras para tiendas de aplicaciones

Android 14 introduces several PackageInstaller APIs that allow app stores to improve their user experience.

Request install approval before downloading

Installing or updating an app might 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 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.

Paquetes de metadatos de la app

A partir de Android 14, el instalador del paquete de Android te permite especificar metadatos de la app, como las prácticas de seguridad de los datos, para incluir en las páginas de la tienda de aplicaciones, como Google Play.

Detecta cuando los usuarios toman capturas de pantalla del dispositivo

Para crear una experiencia más estandarizada para detectar capturas de pantalla, Android 14 presenta una API de detección de capturas de pantalla que preserva la privacidad. Esta API permite que las apps registren devoluciones de llamada por actividad. Estas devoluciones de llamada se invocan, y el usuario recibe una notificación cuando toma una captura de pantalla mientras esa actividad está visible.

Experiencia del usuario

Acciones personalizadas y clasificación mejorada de Sharesheet

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.

Screenshot of custom actions on the sharesheet.

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, follow the guidance for improving rankings of your Direct Share targets. Communication apps can also report shortcut usage for outgoing and incoming messages.

Direct Share row in the sharesheet, as shown by 1

Compatibilidad con animaciones integradas y personalizadas para el gesto atrás predictivo

视频:预测性返回动画

Android 13 在开发者选项背后引入了预测性“返回主屏幕”动画。在已启用开发者选项的受支持应用中使用时,滑回手势会显示动画,表明返回手势会使应用退回到主屏幕。

Android 14 包含针对“预测性返回”的多项改进和新指南:

在此 Android 14 预览版中,所有预测性返回功能都是位于开发者选项背后。请参阅与将您的应用迁移到预测性返回有关的开发者指南,以及与创建自定义应用内转换有关的开发者指南

Anulaciones por app del fabricante de dispositivos con pantalla grande

Las anulaciones por app permiten que los fabricantes de dispositivos cambien el comportamiento de las apps en dispositivos con pantallas grandes. Por ejemplo, la anulación FORCE_RESIZE_APP le indica al sistema que cambie el tamaño de la app para que se ajuste a las dimensiones de la pantalla (evitando el modo de compatibilidad de tamaño) incluso si se configuró resizeableActivity="false" en el manifiesto de la app.

Las anulaciones están diseñadas para mejorar la experiencia del usuario en pantallas grandes.

Las nuevas propiedades del manifiesto te permiten inhabilitar algunas anulaciones del fabricante de dispositivos para tu app.

Anulaciones por app para usuarios de pantallas grandes

Per-app overrides change the behavior of apps on large screen devices. For example, the OVERRIDE_MIN_ASPECT_RATIO_LARGE device manufacturer override sets the app aspect ratio to 16:9 regardless of the app's configuration.

Android 14 QPR1 enables users to apply per‑app overrides by means of a new settings menu on large screen devices.

Compartir pantalla de una app

应用屏幕共享功能让用户能够在录制屏幕内容期间共享应用窗口,而非整个设备屏幕。

使用应用屏幕共享时,状态栏、导航栏、通知和其他系统界面元素会从共享显示屏中排除。系统只会分享所选应用的内容。

应用屏幕共享可让用户运行多个应用,但仅限单个应用共享内容,从而提高效率和隐私性。

Respuesta inteligente potenciada por LLM en Gboard en el Pixel 8 Pro

On Pixel 8 Pro devices with the December Feature Drop, developers can try out higher-quality smart replies in Gboard powered by on-device Large Language Models (LLMs) running on Google Tensor.

This feature is available as a limited preview for US English in WhatsApp, Line, and KakaoTalk. It requires using a Pixel 8 Pro device with Gboard as your keyboard.

To try it out, first enable the feature in Settings > Developer Options > AiCore Settings > Enable Aicore Persistent.

Next, open a conversation in a supported app to see LLM-powered Smart Reply in Gboard's suggestion strip in response to incoming messages.

Gboard utilizes on-device LLMs to provide higher-quality smart replies.

Gráficos

Las rutas de acceso son interpolables y consultables

La API de Path de Android es un mecanismo potente y flexible para crear y renderizar gráficos vectoriales, con la capacidad de dibujar o rellenar una ruta, construir una ruta a partir de segmentos de línea o curvas cuadráticas o cúbicas, realizar operaciones booleanas para obtener formas aún más complejas o todas estas acciones de forma simultánea. Una limitación es la capacidad de descubrir lo que hay realmente en un objeto Path; los componentes internos del objeto son opacos para los llamadores después de su creación.

Para crear un Path, debes llamar a métodos como moveTo(), lineTo() y cubicTo() para agregar segmentos de ruta. Sin embargo, no hay forma de preguntarle a esa ruta cuáles son los segmentos, por lo que debes conservar esa información en el momento de la creación.

A partir de Android 14, puedes consultar rutas de acceso para descubrir su contenido. Primero, debes obtener un objeto PathIterator con la API de Path.getPathIterator:

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();

A continuación, puedes llamar a PathIterator para iterar a través de los segmentos uno por uno y recuperar todos los datos necesarios de cada segmento. En este ejemplo, se usan objetos PathIterator.Segment, que agrupan los datos por ti:

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 también tiene una versión de next() no asignable en la que puedes pasar un búfer para contener los datos de puntos.

Uno de los casos de uso importantes para consultar datos de Path es la interpolación. Por ejemplo, podrías animar (o transformar) entre dos rutas diferentes. Para simplificar aún más ese caso de uso, Android 14 también incluye el método interpolate() en Path. Si suponemos que las dos rutas de acceso tienen la misma estructura interna, el método interpolate() crea un Path nuevo con ese resultado interpolado. En este ejemplo, se muestra una ruta cuya forma está incompleta (una interpolación lineal de 0.5) entre path y 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);
}

La biblioteca graphics-path de Jetpack también habilita APIs similares para versiones anteriores de Android.

Mallas personalizadas con sombreadores de vértices y fragmentos

Android has long supported drawing triangle meshes with custom shading, but the input mesh format has been limited to a few predefined attribute combinations. Android 14 adds support for custom meshes, which can be defined as triangles or triangle strips, and can, optionally, be indexed. These meshes are specified with custom attributes, vertex strides, varying, and vertex and fragment shaders written in AGSL.

The vertex shader defines the varyings, such as position and color, while the fragment shader can optionally define the color for the pixel, typically by using the varyings created by the vertex shader. If color is provided by the fragment shader, it is then blended with the current Paint color using the blend mode selected when drawing the mesh. Uniforms can be passed into the fragment and vertex shaders for additional flexibility.

Renderizador de búfer de hardware para Canvas

To assist in using Android's Canvas API to draw with hardware acceleration into a HardwareBuffer, Android 14 introduces HardwareBufferRenderer. This API is particularly useful when your use case involves communication with the system compositor through SurfaceControl for low-latency drawing.