Banning Blue Lights Is the First Step Toward Mature Autonomous Driving

Zeng Qinglin said on Weibo: "Upon receiving this urgent notice, our team acted immediately to implement it in accordance with national requirements."

I stared at this message three times. As a product manager for NIO's smart cockpit, I have always held reservations about marketing symbols like the "little blue light." It's not without value, but the first rule of automotive-grade requirements is: any signal emitted inside or outside the vehicle must not increase the cognitive load on drivers or other traffic participants. The problem with the little blue light is precisely that it turns "I am using autonomous driving" into a code that outsiders need to interpret, and there is no standard for such codes.

Zeng Qinglin of Yijing was quite candid, stating that "true autonomous driving capabilities will only stride forward." I agree with this judgment, but perhaps for different reasons than he intends. The ban on the little blue light appears superficially as a policy halting a feature, but essentially marks a pivotal shift in the industry from a "show-off competition" to a "safety consensus."

Comparing two approaches makes it clear.

On one side is the "Little Blue Light Faction": installing a blue light outside the car to tell pedestrians or following vehicles "this car is driving autonomously" when lit. The intention is good—to make the existence of intelligent driving perceivable to the outside world. But in reality, the brightness, flashing frequency, position, and color purity vary wildly across manufacturers. Some look like police lights, some like ambient lighting, and some directly blind oncoming drivers. More troublesome is that when the blue light is on, drivers think, "Since the car is driving, I can relax a bit." This psychological suggestion directly increases distraction risk. An iron rule of automotive-grade requirements is: no automated system should encourage drivers to disengage from monitoring. The little blue light implies exactly that—"It's reliable, you just need to watch."

On the other side is the pragmatic approach taken by NIO, Tesla, Huawei, etc.: informing drivers of the current autonomous driving status via combinations of instrument clusters, HUDs, and audio cues, while basically avoiding visual prompts outside the vehicle. Why? Because pedestrians outside don't need to know if the car is in autonomous mode; they only need to know if the car will hit them. Autonomous driving status is private information for the driver, so keeping it inside the vehicle defines the safety boundary. We conducted internal tests: when there is a blue light outside, pedestrians do glance at it, but that glance might cause them to ignore more critical traffic signals. An iron rule of automotive-grade product design is: don't create superfluous information for users, and especially don't create information for irrelevant traffic participants.

[!tip] True automotive-grade thinking means not treating users as test subjects

The ban on the little blue light causes short-term pain for emerging brands like Yijing, as they lose a marketing hook. But in the long run, this is actually a good thing. Zeng Qinglin saying "complying with national requirements" shows he understands the logic. The core of autonomous driving capability has never been a specific light, but the stability of the perception-decision-control chain. A standard that can't even unify a light indicates that autonomous driving capability itself is still in a chaotic stage. Now that the state is stepping in to unify standards, it draws a bottom line for the industry: you can compete fiercely on technology, but you cannot play tricks on safety.

I noticed another detail: the news mentioned "what some drivers do after seeing the light lit up." The original text didn't finish, but I guess it refers to relaxing vigilance or even playing with phones after seeing the light. This is the biggest side effect of the little blue light—it gives drivers a false sense of security. During product reviews at NIO, I repeatedly emphasized a principle: any feature that changes driver attention allocation must have redundant warning mechanisms. If the little blue light only illuminates without corresponding audio or vibration alerts, it is an incomplete interaction loop.

Look at this image: there are no autonomous driving indicator lights outside the car, but the interior dashboard clearly displays the current assisted driving status. This is the correct approach—give information to those who need it, and withhold it from those who don't. External lights should be for other traffic participants, such as brake lights, turn signals, and hazard lights, all of which have national standards. "Autonomous driving status" does not belong to the category of information that must be conveyed externally; forcing it out only creates chaos.

From a commercial value perspective, banning the little blue light will accelerate industry reshuffling. Brands relying on gimmicks like "blue light + auto parking" will be forced to shift resources to genuine technical refinement. Conversely, manufacturers like NIO, Xpeng, and Huawei, which have already established complete in-car interaction chains, lose a dimension where low-end competitors could attack them with "I have a blue light, you don't." When Zeng Qinglin says "autonomous driving capabilities will only stride forward," I understand his meaning: banning the little blue light is not a regression, but clearing a stumbling block from the road.

Here is a final judgment: The moment when all brands no longer need external lights to prove they are "in autonomous mode" is when autonomous driving truly enters mass life. Because true capability doesn't need a signal light to announce itself; safety itself is the best advertisement.

Original Link: https://www.ithome.com/0/983/262.htm