In January 2025, Google Cloud and Mercedes-Benz stood on the same stage to unveil Automotive AI Agent: built on Gemini, running on Vertex AI and launching in the new CLA's MBUX assistant. [Google Cloud] In 2026, BYD began adding Google built-in to new European models, while XPENG announced that overseas vehicles would use Google Maps Auto SDK as a navigation foundation. [BYD] [XPENG] The in-car AI assistant, a category that is already two decades old, has entered its third generation.

The debate has heated up with it, but most of the industry is asking the same question: whose model is strongest? Gemini versus GPT versus Chinese foundation models, compared on benchmarks, latency and hallucination rates.

That is the wrong question. Twenty years of in-car voice history point to the same conclusion: this category has never been won by the technology ranking. It is won by the need the product is built around.

Three layers of demand, three very different destinies

Lay out an automaker's needs from external suppliers and the differences in intensity are enormous.

Maps are a monopoly-grade necessity. No automaker can build a global map from scratch: collection, freshness and point-of-interest depth are a multibillion-dollar annual sinkhole. Outside China, consumers' expectations for in-car navigation have been trained by their phones. If the system cannot approach Google Maps quality, users switch to CarPlay and the cockpit experience the automaker spent years building is effectively bypassed. Automakers may resent that dependency, but they cannot route around it.

Voice is a fully competitive product. LLMs have demolished the old entry barrier: today, almost any automaker can connect an API to a microphone array and assemble an assistant that can hold a conversation. Traditional automotive suppliers are transforming, independent companies are chasing contracts, technology giants are bundling products, and automakers are considering in-house stacks. Four camps are fighting at once, and none has a monopoly lever.

Cloud is almost completely substitutable infrastructure. Automakers are naturally multi-cloud, use whichever provider offers the right economics, and show close to zero loyalty.

Those three layers produce three supplier destinies: map vendors retain negotiating power, voice suppliers are continually repriced and replaced, and cloud providers fight on price.

The fate of voice suppliers was written by the category

The dominant supplier of first-generation in-car voice once appeared in nearly every vehicle that offered voice control. Yet anyone who lived through that era remembers that even at the height of its dominance, the business was difficult. Automakers treated voice as an experience feature rather than mandatory equipment. Budgets were cut year after year, customization costs could not be passed through, and the threat of replacement never went away. Local players later won the Chinese market with better Mandarin experiences; LLMs then gave everyone access to a model. The original leader's business has since been split and passed through several corporate structures, and its position in the capital markets is plain to see.

The problem was never that its technology was poor. The problem is that voice itself is not a hard requirement. Remove the assistant and the vehicle can still be sold. Remove navigation and the sale becomes much harder. A supplier living under a cuttable budget line can have superb technology and still face an upper limit defined by gentle, relentless price pressure.

Replacing the old stack with an LLM does not rewrite that fate. Any in-car AI company that still defines itself as "smarter voice" is walking the same road.

Google's real card is not Gemini

Return to the Mercedes-Benz announcement and one detail stands out. The concrete selling point is not simply that Gemini is intelligent. It is that the agent can call on Google Maps Platform data covering 250 million places, with more than 100 million map updates every day. The demonstrations are all navigation questions: "Is there an Italian restaurant nearby?" "Does it have good reviews?" "What is the signature dish?" [Mercedes-Benz]

In plain language: Google is selling the agent, but maps are the ballast.

That is the genuinely asymmetric part of this competition. Models are broadly comparable and the ranking will reshuffle again next year. But only one company can currently offer a conversational assistant natively grounded in the world's strongest global consumer map dataset. Traditional automotive suppliers do not own the map. Independent voice companies do not own it. Automakers attempting to build in-house own neither. Position the same product as an "AI assistant" and it enters a red ocean; position it as "navigation you can talk to" and the field is nearly empty.

Go one layer deeper and this is probably the product's end state. On a vehicle screen, "map" and "assistant" should never have been separate things. Drivers do not really want a car that can chat. They want navigation that can negotiate: "Find a charger on the way, make sure it has coffee, and don't add too much time." The agent is not a new feature sitting beside the map. It is the map's next interaction layer. Whoever truly grows the two together first turns an experience feature into mandatory equipment — and moves itself from a cuttable budget line into a core requirement.

A hard-demand anchor does not guarantee victory

Three buckets of cold water are necessary here, or this becomes advertising.

First: the trust record. Google has repeatedly sunset driver-facing experiences, including Google Assistant Driving Mode, which disappeared after years of changes. [9to5Google] Every cockpit procurement team remembers that consumer-internet companies can cancel products. Automotive programs need supply commitments measured in a decade or more; Google's product-sunsetting habit is one of its largest psychological barriers to entering the vehicle.

Second: the early evidence was not flawless. Rivian's first weeks after adding Google Maps features included owner reports of frozen navigation and repeated reboots. [Carscoops] Heavy EV users also remained divided over the maturity of charging planning. A better data foundation does not remove rollout risk.

Third: integration depth is the dividing line. Google itself describes EV routing as being tailored to a vehicle's specific needs, including proactive charging stops. [Google built-in] That promise only works when the automaker exposes state of charge, consumption, charging and vehicle-control data and then integrates the outputs into the cockpit. Renault and Polestar have shown what deeper integration can do; a brand that merely installs the Google layer can still leave drivers reaching for CarPlay. The hard-demand anchor is an entry ticket, not immunity.

Ask everyone the same question

This framework is not only for understanding Google. It is a mirror for the entire industry.

For Chinese cockpit and voice suppliers, the question is: what hard requirement does your assistant grow from? In China, the answer can be local digital ecosystems and assisted driving. Once the product goes overseas, however, global languages, global POIs and local services are all missing. That gap is exactly why leading Chinese exporters are increasingly turning to Google. For traditional mapmakers, the question is: when an agent takes over the map's interaction layer, which hard requirements remain yours? Regulatory data and the ADAS chain — areas the agent cannot cover — are the positions worth defending. For automakers, the question is simpler: when you cut the budget, who goes first? That answer reveals every supplier's real industry status.

The table for third-generation in-car assistants has just been set. Do not watch only whose model posts the best benchmark. Watch who has embedded itself in a need that cannot be cut.

The next decision point comes in the fourth quarter of this year, when Mercedes-Benz, BYD and XPENG implementations will face real owners at the same time. What will be judged is not AI's IQ, but the quality of the demand beneath it.

This article is based on public information. The argument and conclusions are those of TopChinaCar.