Android Auto is on the verge of one of its biggest updates in recent memory . While Google continues to gradually replace Assistant with Gemini in the mobile ecosystem , the in-car experience is also preparing for significant changes that will go beyond the voice assistant.
The clues found in the latest beta version of the application point to two major new features: on the one hand, support for Google Cast integrated into Android Auto and, on the other, a redesign of the multimedia player based on the Material 3 Expressive design language, which seeks a clearer and more consistent interface with current Google apps.
First hints of Google Cast integrated into Android Auto
Several analyses of the Android Auto APK file in version 15.9, including those performed by 9to5Google and Android Authority , have located new text strings directly related to Google Cast. These references are linked to the Media Router framework , the technology Google uses to manage content sharing between devices.
These lines of code mention typical connection states, such as connected, connecting, or disconnected , along with warning messages related to the Wi-Fi network. For example, text has been found recommending that the phone and car be connected to the same wireless network , a common requirement for any Cast-compatible device.
These kinds of links suggest that Google is working on a way to integrate casting more deeply into the in-vehicle experience . Until now, Android Auto already projects the smartphone screen onto the car's system, even in non-compatible cars , but it does so differently than Cast. The presence of these new features opens the door to a more flexible content delivery model, with behavior similar to that of a Chromecast in your living room.
Although the code doesn't detail the exact functionality, the references to "this car" and "this phone" suggest that the user could send content from their mobile device directly to the vehicle's screen , without relying solely on traditional Android Auto projection. The system would handle the connection, playback, and basic controls, much like what's already seen in smart TVs or speakers.
It's important to note that these are still hidden features in the application, so Google could modify or even discard them before a public release. However, the level of detail in the discovered strings indicates that development is relatively advanced and this isn't just an isolated test.
Video playback in the car: focused on use while the vehicle is parked
One of the most interesting aspects of this potential Cast support in Android Auto is its connection to video playback on the car's screen . In recent months, Google has made it clear that it wants to bring more visual content to cars, but always with strict limitations to avoid compromising driving safety.
References found in the code and the company's activity in other systems suggest that audiovisual content, such as YouTube videos or other platforms , would only play when the vehicle is stationary. This way, the user could take advantage of waiting times—for example, in a parking lot, at a charging station, or during a long stop—to watch content on a screen that is generally larger and more comfortable than their own mobile phone.
The idea would be to have a "Cast" button or equivalent on the phone to cast the video to the car's screen, just like you would with a TV using Chromecast. Once casting has started, the basic controls (pause, fast forward, rewind) would be accessible from the Android Auto interface, with a design adapted for driving but intended for use while stationary.
This approach aligns with the strategy already seen in Android Automotive, the version integrated directly into some vehicles . Last year, Google enabled Cast in Rivian cars, allowing occupants to send videos to the native infotainment system. The arrival of a solution similar to Android Auto would bring both products into much closer alignment.
In Europe and Spain, where regulations regarding distracted driving are quite strict, it seems likely that video functions will remain limited to parked cars . Google is not expected to enable playback while driving in our market, beyond audio and essential visual alerts for navigation and driving.
Relationship with Android Automotive and Google's unified strategy
The potential integration of Cast into Android Auto cannot be understood without considering Android Automotive, the platform that manufacturers can integrate directly into their cars without relying on a mobile device. Rivian was one of the first brands to launch Cast in its Android Automotive-based system , which already hinted at Google's interest in enabling content streaming to the vehicle.
The presence of the same technologies—such as Media Router and generic Cast strings—in Android Auto suggests that Google is trying to align the experience between both platforms . In other words, whether the infotainment system is native (Android Automotive) or mobile-based (Android Auto), the user will have a very similar way of sending and controlling content.
This strategy would also allow multimedia app developers to work with a more unified set of tools , reducing technical differences between cars with integrated Android and cars that only have Android Auto. In the long run, this could translate into better apps optimized for the vehicle environment and faster adoption of new features.
For drivers in Spain and the rest of Europe, this convergence has another advantage: manufacturers already collaborating with Google will be able to offer a more consistent experience over time , regardless of whether the user changes cars but remains within the Android ecosystem. The transition from a vehicle with only Android Auto to one with Android Automotive, or vice versa, would be less abrupt in terms of interface and features.
However, it's important to remember that the final implementation will also depend on each brand . Some manufacturers may limit, delay, or adapt the use of Cast based on their own internal policies and the regulations applicable in each European country.
New multimedia player with Material 3 Expressive design
In addition to references to Google Cast, Android Auto version 15.9 includes a significant redesign of the music and media player . Android Authority has managed to activate this new interface early, which adopts the Material 3 Expressive design language that Google is rolling out across its main applications.
The most noticeable change is the addition of a redesigned progress bar, featuring a wavy effect and a look more in line with the latest Android versions. This bar is displayed both in the full player view and in the control widget on the main Android Auto panel, making it easy to see the exact playback point at a glance.
Updated buttons for playback functions (play, pause, next, previous) have also been detected, along with a more consistent use of colors, shadows, and sizes, aiming to make important elements stand out without overwhelming the driver. The goal is to improve the readability and speed with which the controls are recognized, crucial in an environment where attention must be focused on the road.
This redesign is part of the broader rollout of Material 3 Expressive across many Google apps, from the Android operating system itself to services like YouTube Music and Google Podcasts. As a result, users of recent Android phones will notice that the car's interface more closely resembles what they already see on their phones , reducing the learning curve each time they switch screens.
For now, the new player doesn't introduce groundbreaking features — at least in the leaked code, there are no big surprises in terms of playlists, mixes, or compatibility — but it does represent a significant facelift that could change the overall feel of the app when using it daily.
Development status, availability, and potential changes
Both Cast support and the new media player were discovered through reverse engineering of the Android Auto APK, a common practice that allows for early access to features during internal testing. This type of analysis involves decompiling the application that Google uploads to the Play Store to identify new strings, hidden menus, and options that are not yet available to the general public.
The researchers who discovered these new features themselves point out that, although the code is quite explicit, there is no guarantee that all the functions will make it to the stable version as is . Google could delay their release, modify them extensively, or even discard them if internal testing is unsatisfactory or if regulatory issues arise.
In practice, the fact that these lines of code are present in the beta version 15.9.655104 of Android Auto indicates that development is not in a theoretical stage. Testing and adjustments are already underway, and it is likely that more details about the final interface or technical requirements, especially regarding the vehicle's and phone's Wi-Fi network, will be leaked in the coming months.
For users in Spain and Europe, it's reasonable to expect these features to arrive simultaneously with, or very close to, those in other major markets like the United States, provided that regulations regarding in-car screens don't require specific limitations. In any case, activation is usually rolled out gradually through app updates from Google Play.
Until Google makes an official announcement, it's difficult to set specific dates, but the pattern followed on other occasions with Android Auto suggests that these new features could start appearing first in a limited group of beta users and, weeks later, in the stable version for everyone.
What we've seen in the code and the tests performed indicates that Android Auto is heading towards a stage where the multimedia experience gains prominence with Cast and a more modern player , but always under the watchful eye of safety and traffic regulations. If Google manages to balance these elements well, European drivers could soon have a more convenient system that's more consistent with the rest of the Android ecosystem, without turning the car's screen into an additional source of distraction.
