[Reprinted] My views on mobile phone software development

Original address: http://topic.csdn.net/u/20080114/14/433ec24c-9700-4e8c-9ed4-504c36d75093.html? Seed = 1207256351

I have more than 4 years of development experience and work experience in the development of mobile phone software. Mobile phone software development companies are divided into two types from the perspective of developers. Most of the technical staff in a company are specialized in mobile phone development; A mobile phone software is a part of the entire project or product. In this way, most of the company's technical staff are not dedicated to mobile phone software, A small company may be a mobile phone software developer, and others may not be familiar with this technology. We will discuss the next situation today.

When developing mobile phone software, the latter companies need

1. Work with the manufacturer and operator

Pay attention to cooperation with the manufacturer when developing mobile phone software. Generally, manufacturers will have a certain level of openness to their mobile phone systems. The products that are open to the public are relatively secure and feature-limited, only by working with them can they get a higher level of openness and technical support to better implement their own functions. Some of the more sensitive APIs and functions that may cause user fees must be signed or verified by the vendor before they can be used. Otherwise, there is no way to develop them, or the user experience is poor. For example, text messages and network connections will pop up one after another and ask the user to confirm. Working with manufacturers also gives you a clearer picture of what functions a mobile phone has and how much you can do. You can also know the future development status earlier than others and plan ahead. Cooperation with vendors is not necessarily unilateral. For example, when a company marketing its own products, it can recommend or specify the products of that manufacturer to expand the influence and depth of the mobile phone manufacturers, companies can also use the brand of mobile phone manufacturers to increase their credibility and strength to achieve a win-win situation.

Pay attention to the cooperation with operators when developing mobile phone software. If you want to do stand-alone mobile phone software without network, it doesn't matter. If you want to develop mobile phone software that requires a network, you need to work with the operator. For example, if you develop a mobile phone office system for a certain enterprise in a certain place, the mobile phone needs to use GPRS to connect to the background for data. In this case, cooperation with the carrier is necessary. The customer's network quality and stability, as well as some methods of major customers in the group, need to cooperate with operators. The negotiation with the carrier can be between the customer and the local carrier, or between the company and the carrier. It is recommended that the company have a good relationship with the operator, which is conducive to long-term development. Cooperation with operators is complicated. Cooperation models such as SP and Si are too long to be discussed. My point is that the long-term vision of cooperation with operators is to be unable to fully depend on them. For example, some companies leave their products to the operators (such as China Mobile's ADC platform ), the product operation is just like a shopkeeper, waiting for money to be distributed, which is not conducive to the company's development. (We have the opportunity to discuss with you about the ADC platform .)

2. Strengthen customer persuasion in the marketing process

Marketing is a big topic. Today we will talk about one of the details: communication with customers. Mobile phone software requires more communication with customers. We need to communicate with our customers to demonstrate the superiority of our products and increase the attractiveness to our customers. However, if our customers are not as professional as you are, they may have many "beautiful" ideas, however, this is unrealistic. Generally, we are "customer needs first". Therefore, when a customer puts forward their "beautiful" ideas, we promise to go back and put pressure on developers to satisfy customer needs, after that, the project will fail if the project is delayed. We don't want to see this process. In fact, we should communicate with our customers more, understand the starting point of their needs, and then let everyone solve this starting point within the achievable scope, instead of facing the "higher level" demand. For example, a customer once proposed that they want to download data to a mobile phone without knowing it. The starting point of this requirement is that the customer is unwilling to wait for a connection for a long time, you can click the software. It would be very difficult for us to solve the problem of "downloading data to a mobile phone without knowing it", but the solution is "not waiting for a long time, click it to use it. Some of the requirements may not be met, but the next series of mobile phones can be implemented. We can also give our customers a technical expectation (how important it is to cooperate with the manufacturer, huh, huh ). Let customers trust us, communicate with customers more, persuade those "beautiful" desires, give customers an honest and practical image, and truly achieve professional marketing. Of course, to be an expert, it is a complicated and huge project and requires the efforts of all aspects of the company. This topic is relatively simple and can be further discussed.

3. involve mobile phone technicians

When designing technical implementation solutions, it is helpful to let mobile phone developers participate and listen to their opinions. Compared with the mature background technology, mobile phone systems and network restrictions are a bottleneck and sometimes cannot be changed. For example, some mobile phones can only download K of things at a time. Therefore, you should pay more attention to these restrictions when determining the technical implementation scheme, and discuss with the mobile phone technical staff to avoid subsequent changes due to these restrictions. Mobile phone software adaptation is also a problem. Currently, mobile phone platforms are mixed with different standards. It is very difficult to adapt to different mobile phones. It is also necessary for mobile phone technicians to determine specific models or minimum adaptation standards. The user is very concerned about the UI of the mobile phone software. When it looks good, he will feel technical and useful. He will like our products more. Therefore, a set of good UIS is essential. Most projects of mobile phone software development are in the UI system. A good set of independent mobile phone software UI system is part of the core competitiveness of the product. Therefore, it is essential to establish and develop such a UI system together with mobile software developers.

Today, I briefly talked to you about mobile phone software development and will have more discussions with you later. Welcome to our discussion. MSN: yangbin313@example.com