In the past decade or so, the competitive logic of smartphones and smart cars has undergone the same change: from "hardware is high or low" to "system and software determine experience". Among them, mobile phones have shifted from comparing workmanship and signals to winning by UI/system capabilities and ecology; cars have shifted from three major components and power parameters to the continuous upgrade of smart cockpit and autonomous driving computing power. The yardstick for measuring the long-term value of products has also changed from one-time delivery configuration to update speed, data closed loop and scene coverage.
Similarly, the electric two-wheel industry is also at the threshold of the same "transformation". For a long time, the industry has mainly done "parameter addition" around motors, batteries, frames, brakes, etc., but this kind of competition is difficult to precipitate into a sustainable experience: the bottom layer inconsistencies brought by different supply chains make function reuse and migration expensive and slow, and the user side often sees "a certain product, a certain software version is doing well", rather than "the more you use it, the better".
To turn the "parameter advantage" into a long-term experience advantage, there must be an operating system-level intelligent base that unifies data structures, interface specifications, and capabilities through algorithms and languages, and makes it possible to coordinate iterations across vehicles, clouds, and mobile phones. In this context, on August 26, No. 9 released the first self-developed global operating system in the field of two-wheel/short transportation - NimbleOS.
This is not to add another function to the existing product, but to advance the competitive logic of the two-wheel track from the stacking of components in the "mechanical age" to the systematic competition of "software definition": precipitation with a unified architecture/the same set of DNA carrying capacity, and continuous evolution of replication and decentralization through cloud-side-end collaboration and OTA of the whole machine, so that the user experience changes from "buying a car" to "obtaining a continuous refresh and continuous optimization of the product experience".
Two rounds of industries have entered the "self-developed OS era"
In terms of system naming, the "Lingbo" in the name of Nimble OS is taken from the image of "light and smooth", echoing the English Nimble, and also points out the requirements for lightweight and response consistency of the two-wheeled product - it is not a "general operating system" that copies the car's car rules system, but a special system base that combines the computing power and energy consumption boundaries of the two-wheeled product.
Looking at the timeline, "Lingbo OS" did not come out of nowhere. Starting from "applying robotics technology to two-wheelers", No. 9 Company first reinvented the entrance of the car in 2019 with True Intelligence 1.0 (RideyGO keyless, etc.); then True Intelligence 2.0, through mole control, OTD single-turn handle, ramp assistance, etc., will "use software to define riding" into daily experience; in 2022, the core algorithm will be further popularized to most models, and intelligent capabilities will no longer be "early adopters" of a few models.
Entering the stage of true intelligence 3.0, the top layer began to move towards ecology, and what supported the continuous growth of the ecology was the Lingbo OS architecture that was named externally and harvested into a system. Therefore, "Lingbo OS" is more like a systematic naming and engineering convergence of years of technology accumulation, that is, depositing scattered functions on a unified base.
Choosing to "expose" the operating system at this moment also has clear internal and external logic: externally, the industry and users have a mature understanding of the concept of "operating system", and the discussion of intelligence is no longer limited to a single function; internally, cross-platform and cross-model development and iteration need a unified architecture and the same set of "DNA" to carry, to avoid transplantation rejection and slow pace due to underlying differences.
Based on the self-developed OS, No. 9 Company has integrated the car terminal, the cloud terminal, and the mobile terminal into an integrated link, and the functions and algorithms have the conditions for precipitation, replication, and decentralization - this is not only a forward-looking judgment of the direction of the two-round industry, but also the only way to move from the "functional era" to the "software-defined era".
In this sense, the beginning of the "self-developed OS era" is not to stack "a few more functions", but to establish the system force as the starting point of competition: unified data structure and interface, scene-oriented capability collection, sustainable OTA and algorithm evolution.
Lingbo OS is a concrete expression of user value
Making more features and making the experience better are two different things. The former can be done by stacking single point configurations, while the latter requires a system base that connects the sensing, control, and application layers, and can precipitate capabilities into standards and continue to evolve in a unified way.
Lingbo OS assumes exactly this role: with a unified architecture and the same set of "DNA" specification data and interfaces, the car terminal, cloud terminal and mobile terminal are connected into a link, so that algorithms and functions no longer rely on a single chip or a generation of hardware, but are updated on a rolling basis within the same framework. For users, this means that the "version difference" is gradually smoothed out, the upgrade path is changed from an occasional "big change" to a predictable and replicable whole machine OTA and algorithm iteration, and the product value no longer stays at the moment of delivery.
When it comes to the current perceivable experience, the system base first changes the "parameter" to "somatosensory". Taking the M5 as an example, electronic control, meters, BMS, etc. cooperate under the same OS framework, 5-inch TFT meters, true intelligence 3.0 and "mole control" "player mode" and other capabilities work in a unified mode management and prompt logic, and the burden of information reading and processing is lighter. The dual-channel driving recorder is also connected to the system to form a riding record that can be called and retained.
Focusing on battery life and replenishment, the sampling on the BMS side is coordinated with the diagnosis/prediction in the cloud to make the remaining mileage and battery status more stable. With fast charging and a unified replenishment strategy, the sense of "battery life anxiety" in daily use is significantly reduced. More importantly, these capabilities do not exist in isolation, but are incorporated into the same iterative path: today's optimization will become the "basic ability" of more models tomorrow, rather than the "early adopter function" of a few models.
From the perspective of value attribution, the necessity of Lingbo OS lies in meeting the demands of both users and development: for users, it turns "buying a car" into "joining a system that will continue to evolve", and the upgrade frequency, experience consistency and learning cost are more controllable; for development and operation, it converges long-term investment into a unified architecture, reduces the consumption of cross-platform transplantation and rejection, and accelerates the closed loop of "requirements-development-verification-release", making "functional decentralization" a normal capability.
The result is not a string of new additions, but a reusable, reproducible, and decentralized evolution channel - this is the "smart base" necessary for the two rounds of intelligence to move from the "functional era" to the "software-defined era", and it is also the "smart key" to undertake user requests, simplify development burden, and build the upper limit of the imagination of the two rounds of products.
From "proposing intelligence" to "defining intelligence", Company Nine builds "system barriers"
Company No. 9 attracts users through "intelligent functions", and then precipitates the technology into the "system", and finally develops the "ecosystem". Since entering two rounds of industries in 2019, Company No. 9 has regarded intelligence as a breakthrough to bring innovation and value to the industry and users, and it is also a key point for itself to gain a foothold.
Now, Lingbo OS has completed the systematization of this thread. It hosts discrete functions and algorithms in the same architecture. As a result, the ability to "launch in flagship models today" has a faster pace of replication and decentralization across models; "experiences needed tomorrow" can also be quickly verified and delivered in a unified data and interface specification.
For users, intelligence is no longer a label for a certain generation of products, but an experience upgrade with the entire life cycle of the vehicle. For R & D and operation, investment is no longer consumed at one time, but continuously reused and amplified on the system base.
This also explains the true meaning of "intelligent leadership": not "a few more function points", but to raise the starting point of competition to a system force. Single point functions can be imitated, but systematized capabilities are difficult to replicate - unified data structures, cross-end collaborative links, verifiable iterative processes, superimposed on years of accumulation in riding algorithms and human-machine interaction, constitute intelligent "structural advantages".
When such a base interacts with the product matrix, new products like the M5 are no longer just "stronger parameters", but unify the battery, electronic control, car and human-machine interaction in the same rhythm, so that "visible experience enhancement" and "invisible engineering efficiency" reinforce each other.
From "proposing intelligence" to "defining intelligence", No. 9 completed the change of track of the competition rules: the two rounds of competition from one-off parts to sustainable system competition. Lingbo OS, as the intelligent base, makes this path repeatable, verifiable, and scalable engineering conditions, and also allows "intelligence" to achieve stable benefits that users can feel on a daily basis.
