CarPlay Integration with Lynk & Co 06: A Microcosm of Open vs. Closed In-Car Ecosystems

According to IT Home's report on July 27, the entire Lynk & Co 06 series (including Relive, EM-P, and Renew models) received the LYNK Flyme Auto 2.5.0 push update, with the core update being support for Apple CarPlay. This means that amidst the wave of domestic car OS systems trying to build independent ecosystems, Lynk & Co chose a path of "inclusive compatibility."

A set of data is worth noting: As of Q1 2024, Apple CarPlay's penetration rate in the Chinese market was approximately 35%, mainly concentrated in mid-to-high-end joint venture brands; meanwhile, the Lynk & Co 06 sells around 3,000-4,000 units per month, with a user profile skewed towards younger, tech-savvy individuals. When these two sets of numbers collide, it brings not just a feature update, but a rethink of car OS ecosystem strategy.

Short Term: Immediate Satisfaction of User Needs and Smooth Experience

In the short term, this update directly addresses two pain points: high-frequency essential needs of Apple users and experience upgrades for existing vehicle owners.

• High-Frequency Essential Needs of Apple Users: Among potential buyers of the Lynk & Co 06, iPhone users account for a significant proportion (according to industry surveys, iPhone users account for about 40% of buyers in the 200k-300k RMB price range). Previously, although Lynk Flyme Auto had strong self-developed capabilities, it lacked native CarPlay support, forcing some users to choose between "good car OS" and "phone ecosystem." Now, the addition of CarPlay allows users to seamlessly connect without switching phones or abandoning the car OS.
• Experience Upgrades for Existing Vehicles: For owners who have already purchased the Lynk & Co 06, OTA pushes are the optimal solution for "refreshing old cars." Compared to hardware upgrades, software-level CarPlay support can directly enhance the experience in core scenarios like navigation, calls, and music, at almost zero cost. This aligns with the industry trend of "software-defined hardware."

My judgment is: In the short term, this update is a defensive strategy. While Huawei HarmonyOS Cockpit, Xiaomi HyperOS, and other domestic systems are conquering markets, retaining the CarPlay interface gives users a reason to "not switch cars." But what's more noteworthy is why Lynk & Co chose to integrate CarPlay only after its self-developed system had iterated to version 2.5.0?

Long Term: The Game Between Self-Developed Ecosystems and Open Ecosystems

From a long-term perspective, this update reveals the competition between two paths for car OS development: self-developed closed loops vs. open compatibility.

[!note]

Car OS systems are essentially a battle for "entry points." Whoever controls the user's in-car interaction controls the lifeline of data, services, and even business models.

• The Dilemma of Self-Developed Closed Loops: Lynk Flyme Auto is a product of cooperation between Geely and Meizu, initially emphasizing "boundless connectivity," aiming to establish a closed ecosystem from phone to car, from travel to life. But the reality is that the stickiness of the Apple user ecosystem (over 2 billion active devices globally) exceeds expectations. Any domestic system attempting to "replace" CarPlay must face the huge cost of migrating user habits. The update for the Lynk & Co 06 is essentially a compromise with the reality that "users won't switch phones for a system."
• The Cost of Open Compatibility: Integrating CarPlay means giving up some data sovereignty. Behind Apple's "privacy protection" label lies the fact that automakers cannot directly access user behavior data such as navigation, calls, and media usage, thereby weakening subsequent monetization capabilities like precise push notifications and paid services. But looking at it another way, if forced closure leads to user churn, the loss is greater.

My research insight is: At the current stage, smart cockpits are still in the phase of "feature completion" rather than "ecosystem dominance." Most users' core demands for car OS systems remain "easy to use, stable, hassle-free." CarPlay's stability and seamless multi-device switching capabilities are precisely what many domestic car OS systems find difficult to surpass in the short term.

A Question Worth Asking: Why "Now"?

The update rhythm of the Lynk & Co 06 is intriguing. The push time for LYNK Flyme Auto 2.5.0 coincided with one month after the release of Huawei HarmonyOS Cockpit 3.0, and three months after the launch of the Xiaomi SU7. These competitors are all emphasizing "phone-car integration," while Lynk & Co chose to reverse-integrate CarPlay.

[!tip]

This perhaps suggests that Lynk & Co has adopted a "barbell strategy" in its ecosystem approach: one end maintains technical autonomy through self-developed systems, while the other covers the vast majority of user devices through open interfaces. Apple users use CarPlay, Android users use Flyme Auto, and both run in parallel without conflict.

But the question is, can this "fence-sitting" strategy last? When Huawei, Xiaomi, and Apple are all trying to build "full suites," the automaker's neutrality might actually become an advantage—users don't need to switch phone brands for a car's system. However, this also means Lynk & Co must continue investing resources in maintaining and adapting two systems, which is a test of R&D resources.

Trend Prediction: Over the Next Two Years, Car OS Ecosystems Will Move Towards a "Three-Layer Architecture"

Based on the above analysis, I offer a clear trend prediction: In 2025-2026, mainstream smart cockpits will no longer be an either/or choice of "closed vs. open," but will form a "three-layer architecture."

• Bottom Layer: Vehicle OS Kernel (e.g., QNX, Linux, Android)—Determines system stability and security.
• Middle Layer: Automaker's Self-Developed Interaction Layer (e.g., LYNK Flyme Auto, HarmonyOS Cockpit)—Provides differentiated experiences and brand-exclusive features, such as vehicle control and special scenario modes.
• Top Layer: Third-Party Phone Projection Protocols (CarPlay, Android Auto, Huawei HiCar)—Covers users' core phone applications, but automakers can retain partial data control through customized interfaces.

Original Link: https://www.ithome.com/0/982/210.htm