Or there is only one solution. Let's talk about the future direction of electronic and electrical architecture from a user's perspective.

But even if it is a cross-domain/centralized EEA, the author still believes that it will not be an ideal breeding ground for explosive in-vehicle applications, and even the central computing architecture recognized by some car companies is not competent. There is still a huge problem that has not been solved here, that is, universality. We can refer to the popularity of PCs and the popularity of Apple and Android systems. The core is to achieve unification in system architecture. PC is the winner of Intel's X86 architecture, while Apple and Android have reached an agreement under the ARM architecture. But looking back at the automotive industry, even under the cross-domain/centralized EEA architecture, whether it is BMW, Toyota or Volkswagen, they have launched their own corresponding solutions, but there are still obstacles to universality, which will be a catastrophic test for developers.

At present, most car companies still rely on their own capabilities to achieve the best scale. For example, Volkswagen is the best example. They plan to unify more than ten brands in the group into the SSP platform architecture in the future. This means that in terms of electronic and electrical architecture, Volkswagen's annual production and sales of about 10 million will be replaced by a unified software and hardware environment. Moreover, this architecture will start to launch products in 2024. In a few years, the user scale of this platform architecture will reach tens of millions, which is of course good news for developers. But the author believes that this is not enough. This is equivalent to Volkswagen actually wanting to copy Apple's previous gameplay, using strong product power to expand the scale and using scale to grab developers. But the industry may also need another "Android" model, a model that allows more car companies, at least those that cannot compete with Volkswagen in scale, to still choose. Perhaps at that time, some companies will choose to open source their architecture, and at the same time give this architecture enough space so that car companies using it can create their own unique soul.

Of course, these are all my assumptions, but a unified EEA architecture will be the inevitable choice for the industry. Because at that time, the in-vehicle application will not only be a program running on the screen of the car, it will inevitably involve core content such as vehicle driving and driving control. Perhaps a set of tuning programs adapted to the Nürburgring Nordschleife will be able to be loaded between different brands, and the logic algorithm of autonomous driving can also be installed in different sizes, different sensors, and of course different brands of models after each push, and these are all based on the fact that everyone uses the same EEA architecture.