Android 17: What's new, changes and compatible phones

Android 16 has just settled in, but All eyes in the Android ecosystem are now on Android 17Google has started the rollout with several Developer Previews and up to four betas, and it can already be said that this is not a simple aesthetic update: the company is preparing a change of cycle, with a more unified architecture, more prominence for AI and a very serious leap in large and portable devices.

In the next lines you will find All the information known so far about Android 17: full calendar, internal name, ChromeOS integration, interface changes, AI features, gaming improvements, what's new in each beta, compatible devices (Pixel, Xiaomi, Redmi, POCO and other manufacturers) and how to install the beta if you want to tinker before anyone else.

What is Android 17 and why is it going to generate so much buzz?

Android 17 will be the official version of Android for 2026With API number 37 and a clear focus: to move beyond simple updates and address the system's fundamental issues. Google has already released several Developer Preview and betas designed for developers, in which new APIs, profound changes in architecture, and AI functions integrated into the core of the system are tested.

According to analysis by specialized media, Android 17 is shaping up to be a version "Reinvented" that wants to unite mobile, tablet and computer under one umbrella. The idea is to eliminate the historical barrier between Android and ChromeOS, simplify Google's internal maintenance, and transform Android into a system capable of scaling from an inexpensive mobile phone with Android Go to a high-end laptop, with a strong presence of Gemini and AI in virtually every layer.

Among the major pillars being built around Android 17 are the following: The initiative known as “Aluminum OS” or unified Android, the performance and battery boost, a visual redesign with Material 3 Expressive much more visually appealing and the arrival of advanced features for gaming and photography.

Codename: Cinnamon Bun and the new Android internal order

As has become tradition, each major version of Android receives an internal dessert nameAlthough Google hasn't used it in public marketing for years, Android 17 is codenamed [codename missing]. “Cinnamon Bun” (cinnamon roll)which in turn is part of an internal alphabetical reorganization that Google has been readjusting.

After the famous “Vanilla Ice Cream” for Android 15Logically, Android 16 should have started with W, but Google decided to break the pattern and named it as "Baklava"This change is not a mere whim: it marks a kind of "year one" for the new stage of development called “Trunk Stable”, a much more orderly and predictable model when it comes to integrating changes into the system.

With that restart, Android 17 had the letter CHence the “Cinnamon Bun”. All this nomenclature goes hand in hand with another much-loved tradition: the Easter egg Included in Settings. In Android 17 beta 4, the old Android 16 logo disappears and gives way to the purple Android 17 emblem with several superimposed layers and a style very much in line with Material 3 Expressive. Activating it unlocks a minigame called “Landroid”, a modern homage to the classic Atari Lunar Lander from 1979.

Android 17 release schedule

The pace of Android versions has become very predictableGoogle has maintained a fairly refined annual cycle for years, and with Android 16, it already moved up the stable release to summer. With Android 17, it seems they will repeat this strategy, with a schedule roughly as follows:

• February 2026: The first Developer Preview of Android 17 has been released. This is a very early version, designed for developers to begin testing new APIs and behavior changes. It is typically unstable and not recommended for regular users.
• February – March 2026: successive Developer Previews that refine APIs, correct serious bugs, and add more features under the hood.
• February 13, 2026: Android 17 Beta 1 (builds CP21.260116.011.B1 / A1), with security patch level 2026-01-05 and Google Play Services 25.47.33, suitable for 64-bit x86 emulator and ARM v8-A.
• February 26, 2026: Android 17 Beta 2 (CP21.260206.011 and CP21.260206.011.A1 for Pixel 6, 6 Pro, 6a, 7 and 7 Pro), with patch 2026-02-05 and Google Play Services 25.49.33.
• 26 March of 2026: Android 17 Beta 3 (CP21.260306.017), which reaches the platform stability, freezes APIs and behavior, and includes patch 2026-03-05 and Google Play Services 26.02.35.
• April 16 from 2026: Android 17 Beta 4 (CP21.260330.008), considered the last scheduled beta, with security patch 2026-04-05 and Google Play Services 26.11.36. It is the version to finalize compatibility and for app and SDK developers to polish details.

From there, if Google repeats the same pattern, The stable version of Android 17 should arrive in the summer of 2026.Probably in June or July for the first Google Pixel phones. After that, the other manufacturers will adapt the Android 17 base to their own interfaces (HyperOS, One UI, etc.) during the second half of 2026 and the first part of 2027.

Furthermore, according to some analyses, Android 17 inaugurates a more structured update system, with two major releases a year and constant quarterly improvements (the well-known Quarterly Platform Releases or QPR), which guarantees a continuous flow of changes without waiting twelve months between major versions.

Android Canary: an early glimpse into the future of Android 17

Alongside all of this, Google has created an updates channel called Android Canary For Pixel devices, it works the same as Chrome's Canary channel. It's the most experimental step. much more unstable than a classic beta, and it is updated with the changes that the engineers are integrating almost in real time.

This channel has become a key source for seeing many of the features ahead of time which then appear in the Android 17 Developer Preview. With Android Canary, details such as the new Material 3 Expressive design, changes to the control panel, or "Liquid Glass" style transparencies could be tracked even before Google talked about them at Google I/O.

The big leap: Aluminium OS and the end of ChromeOS as we know it

The most disruptive new feature associated with Android 17 is the project “Aluminum OS”, an initiative that seeks, nothing more and nothing less, than unify Android and ChromeOS in a single system capable of working on mobile phones, tablets and laptops.

Until now, Google maintained two systems in parallel: Android for mobiles, tablets, watches, cars and other connected devices, and ChromeOS for laptops and computersespecially in the low and mid-range segments. This duplication implies maintaining two development processes and dividing efforts. With Aluminium OS, the idea is to have a single core for everythingwith a mobile and a desktop experience that adapts depending on the device and screen.

In practice, this means that Android would also act as a desktop systemConnected to a monitor or laptop, it would offer a full desktop interface with optimized windows and controls, while on mobile it would remain the classic experience. This way, Google can attack on several fronts:

• Unify resources: By focusing on a single development, duplicate work between Android and ChromeOS is reduced, and advancements are shared faster between formats.
• Attacking the high-end laptop market: Chromebooks have been heavily focused on affordable entry-level devices. With Android capable of running on premium laptops, Google aims to compete at a higher level.
• Integrate Gemini into the core: Google's AI, Gemini, would not only be limited to isolated apps or services, but would be integrated into the core of the system, enabling advanced native functions on laptops and desktops without complicated configurations.

The important thing is that, although everything fits into the roadmap of Android 17 and the 2026 calendarGoogle hasn't fully confirmed that Aluminum OS will be fully launched with this version. What is clear, however, is that the head of Android has publicly acknowledged that they are working on it. “taking the experience of ChromeOS and rebuilding its technology on top of Android”, and that it is a project that excites them for "next year", making it clear that the launch is very close to the Android 17 era.

Interface and design: Material 3 Expressive, Liquid Glass and a new control center

On the visual side, Android 17 reinforces the redesign started with Material 3 Expressive by introducing more customization, better-crafted animations, and a strong use of transparenciesThe goal is to modernize the interface without losing its identity compared to rivals like iOS or skins like HyperOS.

One of the most visible new features is a kind of effect “Liquid Glass” or frosted glassThis is very similar to what we've already seen in iOS and Xiaomi's own HyperOS. Instead of light or dark opaque panels, many elements become semi-translucent:

• Translucent volume bar: When the volume is adjusted, the bar slightly reveals the content underneath, both in apps and on the home screen.
• Panels and sheets of the system with blur: Menus such as the full volume sheet, the power menu, or certain system cards apply a soft blur that preserves the background colors.
• Icons more integrated with the theme: The app and interface icons more rigorously adopt the user-defined accent color, reinforcing visual cohesion.

Additionally, Android 17 introduces a new divided control centerInspired by what other systems already offer, but with its own unique touch:

• Al swipe in from the top left You can access notifications and the so-called "magic summaries" powered by Gemini, which can offer a smart summary of what is displayed.
• Al swipe in from the top right a opens new control center with a frosted glass effect and resizable and customizable quick settings buttons.

There are also more subtle changes: a redesigned search bar as a persistent widgetInternal settings have been reorganized, and a new interface has been created for screen recording with floating bar which does not appear in the final video and the possibility of hide app labels on the main screen, which forces the icons to be more recognizable on their own.

AI and Gemini: AppFunctions and intelligent brain at the core

Artificial intelligence is not limited to a couple of flashy functions: Android 17 embeds it directly into the system baseOne of the keys is AppFunctionsa local framework that allows applications expose their own internal functions so that assistants like Gemini can execute them using natural language.

Thanks to this, AI can chain together complex multi-step tasks within third-party apps without the user having to press each button individually. For example, you could ask the assistant something like "book a Japanese restaurant for tonight with my college friends" and, through AppFunctions, Gemini would call specific functions in messaging, calendar, or booking apps to complete the operation in the background.

This integration is reinforced by the push of Aluminium OS in the laptop market: having Gemini embedded in the Android core It opens the door to contextual desktop assistants, local content generation, summaries of what is seen on screen, or advanced automations without relying so much on the cloud.

Gaming: controller remapping and integrated virtual controller

Android 17 arrives with Exciting new features for playersGoogle wants mobile to be a more serious and coherent gaming platform, and to achieve this, it is introducing very specific improvements:

• Native controller remapping: The system incorporates official support for remapping physical controller buttons, so you can adapt the actions to your liking and avoid typical problems when connecting an Xbox or PlayStation controller in games designed for a different layout.
• Virtual control function: Android 17 allows you to translate on-screen taps in a touchscreen game into signals from a physical controller. This lets you use your favorite controller even in titles designed exclusively for touchscreens. The system acts as a bridge between the two, improving the experience without requiring developers to completely rewrite the game.

Furthermore, under the hood, Android 17 introduces MessageQueue optimization without blocking, new generational garbage collection system in ART and performance profiling triggers (cold starts, excessive CPU usage, etc.), which helps to reduce stuttering, dropped frames, and power consumption spikes in demanding games.

Privacy, security, and a change in philosophy regarding app installation

In terms of privacy, Android 17 follows the path of recent versions, but gives several very relevant steps that even change the traditional culture of freedom on Android.

On the one hand, protection is strengthened data in transit and network accessAndroid 17 It blocks the sending of unencrypted data by default. In certain circumstances, it requires the use of new advanced cryptographic standards and adds compatibility with post-quantum hybrid signatures (APK Signature Scheme v3.2 with a combination of RSA/EC and ML-DSA) to prepare for the arrival of quantum computing.

The permission is also introduced. ACCESS_LOCAL_NETWORK, within the NEARBY_DEVICES group, which protects access to the local area network (LAN) and forces apps that want to communicate with devices on your same network to explicitly declare that intention, thus improving control over which apps can "snoop" on your WiFi.

In terms of user security, Android 17 introduces a SMS OTP code hijacking protection systemThird-party apps (except the default messaging app) will see Programmatic access to SMS messages containing one-time codes was delayed for three hours.To avoid surprises, Google promotes the use of SMS Retriever and SMS User Consent as secure alternatives.

More controversial is the new approach to installing APKs: Google will require developers to verify their identity so that their APKs can be installed, even if downloaded from outside of Google Play. This is officially done to fight malwarebut it hits hard open-source stores like F-Droid and the ecosystem of emulators and unofficial appsreducing the freedom that users had historically had to install anything "at their own risk".

Performance, memory and battery improvements

In terms of performance, Android 17 brings A lot of invisible but crucial workOne of the most important is the introduction, in Beta 4, of conservative memory limits per appIf an application exceeds the RAM usage limit based on the total available on the device, the system will close it and log the closure with the description “MemoryLimiter”. ApplicationExitInfo.

These limits shouldn't affect well-made apps much, but Yes, they will put a stop to poorly optimized applications that “eat up” all the memory and end up crashing the system. Developers can also use the new system of trigger-based profile registration to capture memory dumps when those limits are reached and thus correct bugs.

Android 17 also improves the background process management To save CPU and battery, reduce wakelocks associated with alarms thanks to a new AlarmManager method based on callbacks (instead of PendingIntent), and optimizes garbage collection with a generational collector which cleans short-lived objects faster without having to stop the system so much.

In the betas, it has also been observed that much more comprehensive battery status panelNow the system can display the total number of charge cycles, the cell's manufacturing date, and a “percentage of state” This is a guideline to help the user know when the battery is starting to wear out and it's advisable to replace it or consider upgrading their phone.

Camera, photo and video: RAW14, advanced extensions and better tools

Mobile photography also gets a boost. Android 17 significantly expands what a camera app can do with the platform. One of the biggest additions is compatibility with RAW14 images, a 14-bit per pixel RAW format that offers much greater dynamic range and color depth than the usual 10 or 12-bit RAW files of most current mobile phones.

This leap brings the mobile phone closer to a behavior more typical of DSLR or mirrorless cameras High-end, provided the sensor is up to par. Furthermore, several improvements have been incorporated:

• Manufacturer-defined camera extensions: Hardware partners can define special modes like "super resolution" or advanced AI enhancements, which apps can query using APIs such as isExtensionSupported(int).
• New APIs for camera device types: It is now possible to identify whether a camera is integrated, an external USB webcam, or a virtual camera, facilitating specific configurations.
• Customizing the photo selector: Developers can change the aspect ratio of the system photo picker grid, switching from 1:1 to a 9:16 vertical format to better suit the app's design.

In video and audio, Android 17 incorporates Constant quality (CQ) recording in MediaRecorder, allowing you to adjust the video encoder to prioritize stable quality over a fixed bitrate. Platform support is also added for VVC (H.266)a more efficient video codec, and restrictions are strengthened background audioSo, playing sound, requesting audio focus, or changing volume from an app that is not in a valid lifecycle state may now fail silently to prevent abuse.

For users with hearing aids, Android 17 introduces a new category of Bluetooth LE Audio devices specifically for hearing aids (TYPE_BLE_HEARING_AID)which allows them to be distinguished from normal headphones and to route system sounds (notifications, tones, alarms) separately to them or to the internal speaker.

User experience, windows and large screens

One of Google's obsessions with Android 17 is standardize the experience on large screensStarting with this version, apps that explicitly target Android 17 (API level 37) and run on devices with a minimum width of 600 dp They can no longer disable resizing or orientation changesIn other words, if you're targeting Android 17 and your app runs on a tablet or foldable device, you'll have to adapt, no matter what.

The system also now prevents automatic restarts of activities on certain configuration changes, to avoid losing user state. If an app relied on these restarts to reload resources, it must use the new manifest attribute. android:recreateOnConfigChangesAll of this is combined with improvements in multi-window functionality, more powerful bubbles (which can now be created from almost any app by pressing and holding its icon) and compatibility with iPiP (interactive Picture-in-Picture) in desktop modewhere the fixed windows remain always visible and interactive.

Other interesting changes include:

• EyeDropper API: Apps can read the color of any pixel on the screen without needing capture permissions, ideal for design and editing.
• System-level contact selector (ACTION_PICK_CONTACTS): grants temporary access to specific fields without requiring the full READ_CONTACTS permission.
• Capture the touchpad as a mouse: By default, captured touch panels behave like a traditional mouse (relative movement and gestures) instead of reporting absolute coordinates.

Practical security features: App Lock and more flexible VPN

Android 17 also adds security improvements aimed directly at the average user. One of the most notable is App Lock, a native application locking system which allows you to protect specific apps with a PIN, pattern, or password.

The operation is very simple: Simply press and hold the app icon On the home screen, tap to open the context menu, where the new "lock app" option will appear. Once locked, only you will be able to access that app, ideal for hiding banking, messaging, or email apps from prying eyes. It's a similar concept to... “Application locking” already present in HyperOSbut officially integrated into Android.

On the VPN side, Android 17 incorporates a system-managed exclusion settingVPN apps can launch a special intent (ACTION_VPN_APP_EXCLUSION_SETTINGS) so that the user can easily choose which apps should be left out of the tunnel (split tunneling), without relying on confusing third-party menus.

Improvements in connectivity, multi-device support, and digital health

Android 17 continues to strengthen the coordinated use of multiple devices. A new feature appears. Multi-device Handoff API which allows, through CompanionDeviceManager, resume the state of an activity on another device: start something on your mobile and continue it on your tablet, for example, without losing context.

are also added new precision measurement capabilities with UWB (Ultra Wideband) and Wi-Fi, as support for FiRA 4.0 in indoor navigation and proximity detection using Wi-Fi Alliance specifications. Additionally, the apps can consult the maximum upload and download speeds that the operator allocates to streaming trafficThis allows the video quality to be adapted according to the actual limits of the network.

In the field of health and personal data, Health Connect now distinguishes between data generated by apps and data coming directly from verified hardware. by the system (such as a Wear OS watch or the phone itself). This lends more weight and reliability to metrics of "physical" origin compared to those merely estimated by software.

Compatible devices and mobiles that will be updated to Android 17

As always, The first devices to receive Android 17 will be the Google Pixel devices.The Pixel 6 generation was clearly cut off from the very first beta; from then on, everything else is included. The list of models confirmed or expected for the official Android 17 betas includes:

• Pixel 6, Pixel 6 Pro, Pixel 6a
• Pixel 7, Pixel 7 Pro, Pixel 7a
• Pixel Tablet and Pixel Fold
• Pixel 8, Pixel 8 Pro, Pixel 8a
• Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a
• Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold

Google has opted for policies of up to seven years of updates in their most recent Pixel phones, so all those models have confirmed updates to Android 17. In practice, if you have a Pixel 6 or higher, you'll be covered.

For other manufacturers, compatibility depends on each brand's policiesIn recent years, Samsung has become one of the fastest manufacturers to bring the new version of Android to its high-end and upper mid-range devices, covering several generations. Xiaomi, for its part, integrates Android 17 as its operating system. foundation of the future HyperOS 4And an estimated list for Xiaomi, Redmi, and POCO can already be drawn up based on programs like Android Enterprise Recommended (AER) and Xiaomi's EOL list.

Android 17 and HyperOS 4 on Xiaomi phones

According to the information available on the AER program and Xiaomi's support cycles, there are nearly one hundred Xiaomi, Redmi and POCO models Based on their release dates and promised updates, these systems should be included in Android 17 (and therefore in HyperOS 4 based on Android 17). Some examples of planned product families are:

• Xiaomi range: Xiaomi 17 series (17, 17 Pro, 17 Pro Max, 17 Ultra, 17 Ultra Leica and Leitzphone), Xiaomi 15 and 15 Pro/Ultra/15S Pro/15T/15T Pro, Xiaomi 14 and 14 Pro/Ultra/14T/14T Pro, Xiaomi 13, 13 Pro, 13 Ultra, 13T, 13T Pro, Civi range (Civi 4, Civi 4 Pro, Civi 5 Pro), MIX Flip, MIX Flip 2, MIX Fold 3 and MIX Fold 4, along with Xiaomi Pad 8 and 8 Pro tablets, the Xiaomi Pad 7 family (including Pro, Ultra and 7S Pro 12.5 variants), as well as Xiaomi Pad 6S Pro 12.4 and Xiaomi Pad Mini.
• Redmi range: High-end K series such as Redmi K90, K90 Pro Max, K80, K80 Pro, K80 Ultra, K70, K70E, K7 Ultra and K60 Ultra; Turbo series such as Redmi Turbo 5, 5 Max, 4, 4 Pro and 3; the prolific Redmi Note 15 range (and variants 15 SG, 15 Pro+, 15 4G, 15 Pro) and Redmi Note 14/14 4G/14S/14R 5G/14 Pro+/14 Pro; in addition to lower mid-range devices such as Redmi 15, 15 4G, 15C in its 4G and 5G variants, Redmi A5 4G and tablets such as Redmi Pad 2/Pad 2 4G/Pad 2 Pro/Pad 2 Pro 5G and Redmi K Pad.
• POCO range: High-end F series such as POCO F8 Pro, F8 Ultra, F7, F7 Pro, F7 Ultra, F6, F6 Pro; X ​​series with POCO X6 Pro, X7 and X7 Pro; M series (POCO M8 5G, M8 Pro 5G, M7 4G, M7 5G, M7 Plus) and entry-level C series (POCO C85 4G, C85 5G, C71); not forgetting tablets such as POCO Pad M1 and POCO Pad X1.

All these devices, based on their age and support promises, fall into the category of devices that should see HyperOS 4 based on Android 17provided that Xiaomi maintains the pattern of previous years.

Xiaomi phones that will miss out on Android 17 but not HyperOS 4

Nevertheless, there is a group of mobile phones that, according to current forecasts, They are not included in the Android 17 listBut they will still receive one last major HyperOS update. Xiaomi has followed an interesting strategy in recent versions: The same HyperOS supports two different Android basesFor example, HyperOS 1 coexisted with Android 13 and Android 14; HyperOS 2 combined Android 14 and 15; HyperOS 3 will mix Android 15 and 16; and HyperOS 4 will do the same with Android 16 and 17.

That means if your phone doesn't reach Android 17, it's It's quite likely that it will have HyperOS 4 running on top of Android 16.giving them at least an extra year of system updates. In this context, there are a few devices (nine mobile phones and three tablets) that They are expected to move to HyperOS 4 but not under Android 17. Among them:

• redmi: Redmi Note 14 5G, Redmi Note 13 Pro 4G, Redmi Note 13 Pro 5G, Redmi Note 13 Pro+ 5G, Redmi 14C and Redmi 13.
• LITTLE BIT: POCO M7 Pro 5G, POCO M6 Pro 4G and POCO X6 5G.
• Tablets: Redmi Pad Pro, Redmi Pad SE 8.7 and Redmi Pad SE 8.7 4G.

For these devices, HyperOS 4 will likely be the last major updatebecause they do not have enough muscle (or the necessary support window) to make the leap to Android 17.

How to install the Android 17 beta

If you have a compatible Pixel and you feel like it Try Android 17 before anyone elseGoogle offers several official methods. The simplest is the OTA beta program:

• Log in to the page with your account google.com/android/beta.
• Scroll to the section “Devices eligible for the program”where your Pixel will appear if it is compatible.
• Push the button "To participate" Download your device to enroll it in the beta program.
• On your phone, go to Settings > System > System update and check for updates. You should see them within minutes. The Android 17 beta is ready to download and install.

There is also the option to install the betas by Android Flash Tool or manual system imagesThis gives advanced developers more control. In any case, it's worth remembering that A beta version is not intended for daily use.You might encounter serious errors, unexpected crashes, performance issues, or incompatibilities with apps you use daily. Before you start, back up everything important.

For the final version of Android 17 you won't have to worry too much: When Google releases it for your model, it will appear as a normal update in the system settings.You install it, restart, and you're done.

Main problems fixed in the Android 17 betas

Although these details may seem irrelevant to the average user, it is vital for developers to know them. what gets corrected in each betaAndroid 17 has been polishing a long list of problems, many of them inherited or aggravated in Android 16.

En Android 17 Beta 3When the platform reaches stability, the following issues are resolved, among others:

• Frequent and random app restarts and screen flickering due to regressions in process lifecycle management on Android 16.
• Camera failures when switching to the 5x telephoto lens and erratic behavior in transitions between wide-angle and ultra-wide-angle lenses.
• Lock screen freezes after disconnecting Android Auto, spontaneous restarts during periods of inactivity and general stability problems that caused the device to crash.
• vibration bug which caused some incoming calls not to activate vibration, errors in the status bar making battery and network icons disappear, or visual artifacts when interacting with notifications and back navigation.

En Android 17 Beta 4 Problems such as the following are addressed:

• URLs of web pages that were automatically attached when sharing screenshots from the preview, generating unwanted links accompanying the image.
• Total device locks related to accessibility services.
• Intermittent disappearance of media control widget or errors when switching between active multimedia sessions.
• Dream service failures (environmental displays) that did not process keyboard events or lifecycle callbacks.
• Inability to download and apply correctly cinematic or local weather backgrounds.
• Phone freezes when typing in messaging apps, very slow loading speeds near the 80% limit, and rendering problems that showed multicolored horizontal lines covering the screen.
• Bottlenecks in Bluetooth (disabled and unable to be reactivated), Wi-Fi analysis that did not detect available networks, and other critical instabilities in the system interface.

All this debugging work is key so that, when Android 17 arrives in its stable version, be perceived as a solid, everyday-ready version, despite the enormous internal changes it entails.

Android 17 is set to become one of the updates most important of the decade for the Android ecosystemIt unifies the path with ChromeOS, truly integrates Gemini's AI into the heart of the system, strengthens security and performance, enhances gaming and pampers large and foldable screens, while marking a before and after in the freedom to install APKs.

If you have a recent Pixel or a mid-to-high-range phone from manufacturers like Samsung or Xiaomi, everything indicates that you will experience this leap firsthand, and it's a good idea to be clear from now on about the new features that are coming. Share the information so that other users know about the new feature.