Around 2015, automakers and consumers arrived at an unspoken bargain: buy the car and you can connect your phone. Apple CarPlay and Android Auto projected familiar maps, music and messaging onto the dashboard. Automakers outsourced an experience they struggled to keep current; drivers brought a digital life they already understood.

In October 2025, GM chief executive Mary Barra told Decoder that the company would eventually phase out CarPlay and Android Auto across its lineup. GM later clarified that existing vehicles would not change, gasoline vehicles would retain projection for the foreseeable future, and the transition would be gradual as a new centralized-compute platform arrives from 2028. [The Verge] [GM clarification]

That remains an unusually large bet. McKinsey found in 2023 that 45% of connected-car users used phone projection regularly and another 40% used it periodically; nearly half of surveyed buyers said they would not purchase a vehicle without CarPlay or Android Auto. [McKinsey]

The replacement makes the story more interesting. GM is removing Android Auto, a Google product, while relying more heavily on Android Automotive OS, Google built-in and Gemini. This is not Google deliberately killing Android Auto—Google is still developing it, and began rolling Gemini out to Android Auto in late 2025. [Google] What is happening is subtler: an automaker is giving up Google's projection layer while inviting Google into a deeper embedded layer.

That shift captures the evolution of Google's relationship with the auto industry: from a suitcase carried into the car to part of the building's infrastructure. “Landlord” is a metaphor for control over digital infrastructure, not legal ownership of the vehicle, and it does not mean Google automatically receives every stream of vehicle data.

Act I: the suitcase era and the bill behind the win-win

Projection remains one of the most successful features in automotive history. Apple said in 2022 that 98% of new cars sold in the United States supported CarPlay and that 79% of US buyers would only consider a car with it. Those were Apple's own figures, not an independent global measurement, but they captured how quickly projection became expected equipment.

The bargain meant different things to each party. Drivers received an interface that improved with their phones. Automakers avoided an endless cockpit-software refresh cycle. The technology companies gained something more strategic: time inside the car and influence over how drivers defined a good cockpit. Whenever a driver chose projection, the automaker's own navigation, media and app layer disappeared behind the phone.

The economics sharpened that tension. MarketsandMarkets estimates the connected-car market could reach $26.4 billion by 2030. [MarketsandMarkets] At a March 2026 investor presentation, GM described roughly $2.7 billion in 2025 digital-services revenue and $5.4 billion in related deferred revenue—the second number is a balance-sheet liability to be recognized over time, not annual revenue. [GM Investor Relations] Stellantis has targeted about €20 billion in incremental annual software-related revenue by 2030. [Stellantis]

Revenue and data control are therefore deep motives behind the move away from projection. Safety and integration are not merely excuses: an embedded system can use battery state, range, sensors and vehicle controls in ways a phone connection often cannot. But those engineering benefits coexist with a commercial ambition—to keep the customer relationship and recurring revenue inside the automaker's own product.

Act II: the fitted-interior era and its paradox

Automakers then tried to reclaim the cockpit. The problem was what to build it with. Maintaining a global operating system, map, voice layer, app ecosystem and security-update program is expensive, and many in-house projects have struggled. Android became the most visible path out.

A 2022 S&P Global Mobility forecast illustrated the slope: Android Automotive OS, or AAOS, was expected to grow from roughly 1% of infotainment systems in 2022 to about 18% in 2027. [S&P Global Mobility] That does not mean AAOS simply “ate” QNX. AAOS commonly runs the infotainment experience, while QNX may handle real-time, safety-critical or hypervisor layers; both can exist in the same vehicle. QNX says its software is embedded in more than 275 million vehicles. [QNX]

AAOS is also not the same thing as Google built-in. AAOS is the open-source operating-system base. Google Automotive Services, or GAS, adds Google Maps, Google Play and Google's assistant layer under a commercial agreement; that package is marketed to consumers as Google built-in. An automaker can use AAOS without buying GAS.

The scale of the embedded layer became unusually visible in April 2026. GM said Gemini would roll out to about four million eligible model-year-2022-and-newer Cadillac, Chevrolet, Buick and GMC vehicles with Google built-in in the United States. [GM]

Now the paradox can be stated precisely. GM wants more control over data, experience and revenue, yet it is placing the operating-system base and some combination of maps, voice and apps on Google's stack. It is not transferring legal title to the cockpit, and the data Google can access depends on contracts, accounts, consent and configuration. But the dependency is deeper than it was in the projection era. To reduce its dependence on a phone platform, the automaker may become more dependent on embedded infrastructure.

Four doors into the same courtyard

Google's automotive portfolio is effective because it is not a single all-or-nothing door. It offers several levels of integration.

Door one: Google built-in. This is the fastest way to fill a cockpit's map, app-store and assistant gaps. BYD's ATTO 2 DM-i, unveiled in October 2025 and launched in Europe in 2026, became one of BYD's first models with Google built-in. It still supports CarPlay and Android Auto, useful evidence that embedded Google and phone projection can coexist. [BYD] BYD and Parkopedia are also preparing an AAOS ParkPay service for early 2027, initially on the Denza Z9 GT and BYD ATTO 3 EVO, with some older vehicles to receive it by OTA. The public announcement does not support the claim that every Denza model is included or that it covers 90 million spaces. [Parkopedia]

Door two: Google Maps Auto SDK. This suits automakers that want to preserve their own interface while using Google's map data and routing engine underneath. Rivian was an early deployment in July 2025. [Rivian] On July 16, 2026, XPENG became the first Asia-Pacific automaker to ship the SDK. The L03 opened orders simultaneously in 65 countries and regions—not 64—and XPENG and Google said the integration was completed in less than a year. [XPENG]

Door three: a branded AI agent. Google Cloud's Automotive AI Agent lets an automaker keep its own wake word and identity while using Gemini and Google Maps Platform. Mercedes-Benz introduced it in the new CLA's MBUX under “Hey Mercedes.” The concrete advantage highlighted in the announcement was access to more than 250 million places and over 100 million map updates a day. [Google Cloud]

Door four: projection. If an automaker signs none of the deeper agreements, an Android user can still bring Google into the car through Android Auto. In that case Google occupies the user-experience layer, but it does not automatically gain an OEM contract or access to the automaker's full vehicle-data stream.

These doors lead toward the same courtyard, but not to the same room. Each gives Google a position in part of the cockpit; the rights, data flows and switching costs are different in every case.

The conversion at the border: the China variable

There is a large market where Google's proprietary consumer stack cannot operate in the same way. In S&P Global Mobility's 2022 baseline, roughly 32% of infotainment systems were classified as “generic Android,” and the forecast still put the category above a quarter of the market in 2026. That was a dated baseline and forecast, not a current measured share. It describes a world in which many automakers—especially in China—adapt the Android Open Source Project without Google's proprietary services.

Google's consumer services are not normally accessible in mainland China, and Google Cloud lists no mainland-China cloud region. [Google Cloud locations] But it would be wrong to say every car in China is unrelated to Google: AOSP still sits in the lineage of many systems, and suppliers operate across borders. The accurate point is that Google's proprietary services and commercial cloud stack do not participate in mainland cockpits on the same terms as they do in Europe.

The conversion happens on export programs. Rivian arrived in July 2025, BYD's first Google built-in European programs followed, and XPENG shipped Maps Auto SDK in July 2026. Some Chinese automakers are keeping a self-developed Android stack at home while adding Google's services to selected overseas vehicles. That is not yet a universal rule, but each export program that adopts Google converts an AOSP-based cockpit into commercial Google automotive business.

The attraction is real. Overseas buyers already expect navigation at phone quality; domestic suppliers often lack equivalent global POI depth, local services and language coverage; and the Google name can reduce trust friction for a new Chinese brand. The trade is classic: exchange some control and bargaining leverage for speed, coverage and market acceptance.

The trust problem: Google's two clocks

Automakers' deepest psychological objection is Google's record of shutting products down. The mobile driving experience is a useful case file. Assistant Driving Mode was announced at Google I/O in 2019, arrived in preview in late 2020, expanded in 2021, then began losing its Dashboard in late 2022. More features disappeared in 2024, and the remaining Maps launcher was removed in April 2025. [9to5Google] The exact definition of “launch” changes the lifetime calculation, but the direction is unambiguous: dismantling began roughly a year after the fuller experience arrived.

The embedded record is different. In 2026, existing Google built-in vehicles received Gemini by OTA: GM's eligible fleet begins with model year 2022, while Polestar said all of its models except Polestar 1 would receive the assistant without new hardware. [Polestar] That does not prove every automotive service will live forever. It does show that a multi-year vehicle upgrade promise can operate on a different clock from a consumer app.

The procurement question is therefore not simply “Will Google kill it?” Google has killed products and supported long-lived vehicle programs. The better question is: which clock is written into this contract? What is voluntary product goodwill, and what is a binding obligation covering support, security, data portability, fallback operation and migration? That distinction is worth an entire legal team's attention.

Cold water: installing Google does not win the cockpit

The first evidence is not romantic. Rivian's early Google Maps rollout produced owner reports of frozen navigation and repeated soft reboots. [Carscoops] A strong map foundation does not eliminate launch risk.

The second warning is in the product list itself. BYD kept CarPlay and Android Auto beside Google built-in. That is not a contradiction; it is an admission that users value choice and that an embedded stack has to earn daily use.

Most important, Google's EV-routing promise depends on vehicle data: state of charge, consumption, charger compatibility and destination conditions. [Google Maps] If an automaker shares too little data—or integrates it poorly—the result can still feel generic. Google supplies the entry ticket, not immunity. Differentiation moves to the depth at which the vehicle and the Google stack are fused, precisely the part that is hardest to outsource.

Three watchpoints and one old rule

GM's 2028 wager. The new centralized-compute generation beginning with the Escalade IQ will be the cleanest large-scale test of whether consumers accept an OEM cockpit without projection. The Escalade IQ already lacks CarPlay and Android Auto today; 2028 refers to the new computing architecture, not the first GM vehicle to remove projection.

The late-2026 comparison. BYD's Google built-in route, XPENG's Auto SDK route and Rivian's first full year with the SDK will begin producing comparable owner evidence. The data will not be perfectly symmetrical, but it will give the industry its first useful side-by-side view of Google's two main integration paths.

Regulation squeezing from both directions. The European Union has designated Alphabet a Digital Markets Act gatekeeper and Google Maps a core platform service. That does not make GAS bundling unlawful, but it makes future scrutiny of tying, interoperability and data terms a reasonable inference. [European Commission] In the United States, the Commerce Department's connected-vehicle rule is more concrete: from model year 2027, manufacturers owned by, controlled by or subject to the jurisdiction of China or Russia are generally prohibited from selling connected vehicles in the US, even when the vehicle-connectivity hardware and software are not themselves Chinese, unless authorized. A Google stack does not neutralize the manufacturer's national nexus. [US final rule]

The endgame follows an old automotive rhythm: embrace a technology company, fear loss of control, build in-house, struggle with the cost, then embrace again. The industry has already swung through that cycle more than once. AI raises the cost of going alone and makes Google's bundle more complete, so this swing may last longer. It has not disappeared.

For Chinese automakers and suppliers, the whole argument reduces to one question: when an export vehicle crosses the border and its cockpit switches to Google, what do you gain—and what control, leverage and optionality do you give away? The right time to calculate that trade is before signing, not at renewal.

This article is based on public information. Facts were rechecked and updated on July 18, 2026; the argument and conclusions are those of TopChinaCar.