4. How is an app made? 4. How is an app made?

4. How is an app made? 4. How is an app made?

Many new app backend partners, some of whom have never been in touch with this industry before, some who have learned basic technical knowledge at school, and do not know what the whole process of app development is like, so there is a fear in my heart. Listen to a bunch of app-related terms in other demographics and don't know what's going on, let alone talking to others. In this article, based on my experience in a startup company, I will help you solve the above questions and help you step into the door of app development.
　　
Project startup phase
Before an app project is launched, the product manager (in startup companies, product managers are generally the founders of the company) considers his own thoughts on the app, for example, what business the app is doing, what interfaces are available, what elements are available on each interface, and how the interfaces are redirected. Based on the above ideas, a prototype diagram is displayed.
　　
A prototype diagram is generally created using the axure software. After axure is created, you can export the prototype image as a bunch of html files, and open the file named index in the browser to see the prototype image.
　　
Is an example of a prototype graph file.

 

 

 

From the prototype diagram above, we can see that this prototype diagram only briefly describes the basic interface of the app, and the interface is extremely simple. It is difficult to develop an app by using this prototype diagram alone (if it is hard to produce a prototype diagram, you can start development as well, but the time estimated by the front-end is very inaccurate ).
　　
After the prototype diagram is displayed, the product manager submits the prototype diagram to the UI Designer for the design draft. UI designers began to beautify the prototype map based on their own artistic skills: Add appropriate colors to each element in it; adjust the layout of the entire interface, the size and position of buttons, color, make sure that the entire interface looks more beautiful; mark the font coordinates, the font used, and so on.
　　
The following is an example of design:

 

Even some UI designers are responsible for designing interactions. For example, how can A jump to B from top to bottom or from bottom to top.
　　
After the prototype diagram is displayed, the product manager will hold a product meeting to bring the project-related personnel into the meeting. The main content of the meeting is to introduce the prototype diagram in person, explain the entire product process to relevant personnel, and reply to your questions about the product.
　　
This product meeting is very important: it should ensure that the entire team members have a consistent understanding of this product and ensure the smooth development of the next step.
　　
After the product meeting, relevant personnel should estimate the time based on their own R & D tasks. The R & D Director (many teams do not have this position, and the product manager is also responsible) should formulate work plans based on the estimated time.

 

R & D Phase

 

Backend engineers design the architecture based on the product.
　　
Android and ios programmers can start with the interface based on the design draft, and do not do anything that interacts with the background.
　　
After a period of time (about a week), the backend architecture should be well designed. At this time, the api interfaces should be preliminarily set for the following three points:
　　
1. What is the use of this api?
　　
2. What are the input parameters of this api?
　　
3. What data does this api return?
　　
According to these defined api interfaces, and android and ios programmers believe in instructions, let them understand. These api interfaces first return some test data at the initial stage, so that the front-end personnel can develop them first, and the back-end personnel will gradually implement the functions of these interfaces. In this way, the development progress of the front-end and back-end will not be delayed.
　　
Of course, these api interfaces must be modified in the future. In order to ensure smooth information, please notify relevant developers of any changes.

 

Test phase

When developing a development plan, you should plan and test the functions. Generally, it is recommended to test once every one or two weeks.
　　
If the test was performed only once every two or three months after R & D, there were too many problems. If you understand the business at a specific point, an excessively long R & D cycle will also cause errors that are hard to be fixed.
　　
In the entrepreneurial team, do not imagine that there are dedicated testers, more of them are full testing. Everyone in the startup team acts as a tester to test every function in the app, record the problems found, sort them out, and submit them to the relevant owner for repair.

Official Launch Phase

 

When the app test is complete, I feel that there is no problem, so I will start preparing for mounting.
　　
If it is an ios app, it will take 7-15 working days to submit the App Store for review.
　　
If it is an android app, it will be submitted to various app markets, such as the Xiaomi app market, pods, and app Bao.
　　
However, even if you submit your application to various app markets, your potential users may not download this app?
　　
Not every user knows this application?
　　
After knowing this application, how can I ask the user to press the Download button?
　　
These problems need to be solved by marketing staff in the entrepreneurial team.
　　
After a user downloads the app, how can he ensure that the app is frequently used by the user and how can he ensure the user's activity? This is the work of the operations staff.

 

Postscript

 

The above is the overall app R & D process.
　　
The above project management part, the description is relatively simple, detailed project management, please see my previous blog: http://blog.csdn.net/newjueqi/article/details/19011017
　　
The permissions of many entrepreneurial teams are difficult to distinguish. For example, in a startup team, the app backend must work part-time for O & M, or even the frontend. The reason is simple. There are no other people to do it.
　　
In addition, many teams also have multiple roles. For example, I know a startup team. There are four people, one founder, one background, one android, and one Ios. All work except development is done by the founder.
　　
In short, in a startup company, the ability is growing fast, because you have to deal with a lot of problems, rather than in a large company, just one screw. But at the same time, in a startup company, the requirements for personnel are relatively high, the length of a dedicated course, overtime rather than anything unusual.

 

App back-end articles directory

【Author】 Zeng jiansheng
[QQ] 190678908
[Public Account] appbackend
[Sina Weibo] @ newjueqi
Blog http://blog.csdn.net/newjueqi