To develop mobile phone software platforms, we must start to establish this platform for the future to open out, that is, this thing developed, will continue to be developed in the future.
A mobile phone software platform I participated in this, followed the OSGi agreement (this is a lot of vendor organizations that are supported by many manufacturers, and Eclipse 3.x will also support this protocol). This kind of benefit is that the entire team (often a few hundred people) has a unified Vision. When there is a technical decision, consider it, what we do will take out to someone else, it is convenient to develop applications. Software designers always feel the future developers, the design and interfaces have tended to be reasonable. Another platform for participating is not so far-sighted. I have never thought about it to take this platform in the industry. A lot of technical solutions will be the equity of the equity in order to drive. Hard-code is more and more, the entire Code tends to rot.
The development of software platform is a big project, which needs to be constructed, and hundreds of people collaborate together. If the developer of each company is thinking, this Component is not only to give the line in the future, and will give third-party uses, The API will define reasonable. On the contrary, if communication between Component uses Hard-Code's way, it will be endless, not only the problems that cause configuration management, more serious, the API tends to be unreasonable. I have heard of one way, the API is Pandora's box, and the code is a plague. If the box is not defined, the plague will be transmitted to other modules.
