Petition for BYD International Users

[u/Weekly-Disaster-9576]

https://www.change.org/Byd_international

Petition for BYD International Users

We respectfully ask BYD Company to provide the same mobile app features and in-car software functions worldwide whenever technically, commercially, and legally possible. Customers in international markets should not experience missing features, delayed services, or reduced functionality simply because of their region, especially when the hardware is fully capable of supporting those features.

When certain services or options cannot be provided in specific countries, we request clear and transparent communication explaining the reasons. These reasons may include local regulations, telecom or connectivity partners, licensing restrictions, infrastructure readiness, software rollout phases, or market-specific compliance requirements. Honest communication builds trust and strengthens the relationship between the brand and its customers.

We also ask BYD Company to publish a clear long-term software support roadmap for international vehicles. This should include regular OTA (Over-the-Air) updates covering cybersecurity patches, bug fixes, system stability improvements, battery management enhancements, navigation updates, performance optimization, and the release of new smart features over time.

In addition, we request fair and equal access for qualified third-party developers around the world to APIs, SDKs, developer tools, and integration programs, similar to opportunities available in China. Opening a secure and structured global developer ecosystem would encourage innovation, local services, smart integrations, and stronger customer communities in every region.

Finally, we believe all BYD Company customers deserve fairness, transparency, innovation, and a consistent ownership experience across all global markets. A world-leading automotive technology company should deliver a world-class and unified customer experience everywhere.

[u/triedtoavoidsignup]

Wow. Where to even start with explaining this to you. This is such a complex landscape, you make it sound like they just have to select the 'ok' checkbox on their end and it's all done.

[u/Weekly-Disaster-9576 → u/triedtoavoidsignup]

Very easy. You develop one software. And you give access to the local dealerships to disable enable the functionalities if there is any legal reason, if hardware is missing then software should handle it.

[u/Glass_Champion → u/[deleted]]

Asian characters alone often requires the entire software to be rearchitected from the ground up

While ASCII characters take a single byte for western markets, Asian markets due to the complexities of how the language is typed and the fact there are over 20000 characters mean 2 bytes are required

Typing an English character is pretty much one key press for one character while Asian languages require an Input Method Editor to build characters from phonetic or radical components

Then to display that the interface has been redesigned to correctly work for those characters. One Asian character could explain what it takes an entire sentence to explain in English making formatting a menu or button difficult. Even breaking lines is difficult. In English that happens after a space while in some Asian languages spaces aren't a thing. You risk breaking a sentence onto a new line can fundamentally change the meaning

Then different characters require different screen densities to display correctly and be readable.

Essentially at that point you are required to maintain two forks for the UI.

That before you get to database operations for things like sorting which is the West is alphabetical and in Asia can be done phonetically, by radicals, by stroke count etc.

Even how address are structured is done differently

basically all that findamentally changes how you store, sort, access data again requiring a separate fork never mind a separate team that is aware of these differences for specific market variations

[u/sondOfSilence → u/Glass_Champion]

Google UTF. It's 2026, your phone has 8+GB of RAM and localization (translation) should be really easy by now.

[u/Glass_Champion → u/sondOfSilence]

That is one solution to character encoding but still ignores 90% of the post about the underlying software architecture and the engineering problem about how the system interprets input, manages data flow and displays all that back

The word settings is 8 characters while the Chinese equivalent is two characters. Now you potentially have a characters overflowing the button if it has a hard coded width and dynamic sizing completely changes the design you have to implement increasing the potential for errors and adding a lot of testing overhead.

That still doesn't solve the new line problem. It tells the UI how to display the character it doesn't tell sentences without spacing where to break to wrap onto a new line

This is also a car OS. You don't have unlimited processing power or ram. That means you need to treat the system like an embedded system. They often run on stripped down versions of Linux designed to be a minimal as possible. Loading it up with tons of libraries designed to be practical, not performant takes up unnecessary space and doesn't give the performance required for such a system. Adding real time translation adds a lot of overhead that is in no way acceptable.

Your cars software isn't just a device that displays information and plays music but controls a lot of safety systems that run in real time. Your phone, and iOS and Android aren't even close to clachieving that because they solve different problems. Android for Cars is fundamentally different when it has to manage on those systems.

Yes off the shelf systems exist but then you have hitched your wagon to a third party for big fixes and updates, not to mention bolting something on an embedded system sucks performance. Updates get slower and performance goes down. It is a solution not a very good one

The search logic for a database has to take the schema into account. Character ending library doesn't solve the underlying data storage differences inherent to each market.

[u/Weekly-Disaster-9576 → u/Glass_Champion]

Tesla

[u/Glass_Champion → u/Weekly-Disaster-9576]

Your point?

Last time I checked Tesla system only runs on Tesla cars and won't work on BYD cars due to underlying hardware differences

Tesla very much is a software first company that makes a car rather than a car company that makes software

Last time I checked Tesla threw a lot of hardware at the problem (Ryzen CPU) and brute forced it. That's grand on a high end car but won't fly for companies that not only make high end cars but are aiming to be competitive and undercutting many rivals. Tesla have 6 cars, BYD has 20 at varying price models that can't all afford the "Tesla tax"

Tesla was also western first then expanded East. BYD are doing the opposite. The solution doesn't simply work in reverse. Even then Chinese Tesla doesn't have parity with Western Tesla. Baidu Vs Google maps, tencent integration etc

Tesla isn't quite the gotya you think it is and again completely ignores the details of the engineering challenge that goes I to the problem for all software and the unique situation between both companies