How the 4.app is tempered

Many have just entered the app back-end of the small partners, some have not contacted the industry, some have only in school to learn the basic technical knowledge, do not know how to develop the entire process of the app is how, so the heart will have a fear. Listen to the other people in the mouth of a bunch of app-related terminology, do not know how to, let alone communicate with others. In this article, according to my experience in the start-up company, help you solve the above doubts, help you step into the door of app development.

Project Start-up phase

Before the launch of an app project, the product Manager (in a startup, the product manager is generally the founder of the company) puts his own ideas on the app, such as what the app does, what the interface is, what elements are on each interface, and how each interface jumps. According to these ideas, out of the prototype diagram.

The prototype diagram is usually made with axure software. After the axure is finished, you can export the prototype to a bunch of HTML files, and the file named index opens in the browser to see the prototype.

is an example of a file of a prototype diagram.

As can be seen from the above prototype diagram, this prototype diagram simply describes the basic interface of the app, the interface is very simple. It's hard to develop an app by simply building a prototype (if you just start out with a prototype, it's a very inaccurate front-end estimate).

When the prototype is out, the product manager gives the prototype to the UI designer for the design. UI designers began to beautify the prototype according to their own art skills: to each of the elements in the appropriate color, adjust the layout of the entire interface, button size, position, color, and so on, it must make the entire interface look more beautiful, the logo inside the font coordinates, the use of fonts and so on.

Here is an example of a design:

Even some UI designers are responsible for designing interactions, for example, how a interface jumps to the B interface, jumps from top to bottom, or jumps from the top down.

When the prototype diagram comes out, the product manager will convene a product meeting to bring the entire project-related personnel into the meeting. The main content of the meeting is to introduce the prototype in person, the entire product flow to the relevant personnel to explain, but also to respond to the product of the question.

This product meeting is very important: it ensures that the entire team member understands the product in a consistent and successful development process.

After the product meeting, the relevant personnel will be based on their own research and development tasks to estimate the time, research and development director (many teams do not have this position, by the product manager) according to the estimated time to make arrangements for the work plan

Development phase

Back-end personnel according to the product, design architecture.

Android and iOS programmers, you can start with the design of the first interface, and the background interaction with the part of the first do not.

When a period of time (about one weeks), the backend of the architecture should be designed, then for the following 3 points to initially set the API interface:

1. What is the use of this API?

2. What are the input parameters for this API?

3. What data does this API return?

Based on these well-established API interfaces, and Android and iOS programmers believe the instructions to let them know. These API interfaces first return some test data, so that the front-end personnel to develop first, the back-end people slowly put the functions of these interfaces to implement. This way, the front-end and back-end development progress will not be delayed.

Of course, these API interfaces must be changed in the future, in order to ensure the smooth flow of information, there are any changes please promptly notify the relevant developers.

Testing phase

When developing a development plan, you should plan it and test it once you have finished the functions. Usually a two weeks test is advisable.

If it was developed for two or three months before testing, then the accumulation of problems too much. If you know about the error at some point, the long development cycle can also cause errors to be hard to fix.

In the entrepreneurial team, do not fantasize about a special tester, more is the full test. Everyone in the entire entrepreneurial team acts as a tester, testing every feature in the app, documenting the problems found, sorting them out, and submitting them to the relevant responsible person for repair.

Official Launch phase

When the app was tested, it felt like it was no problem and started to get ready for the shelves.

If it's an iOS app, it takes 7-15 business days to submit a change AppStore audit.

If it is an Android application, it will be submitted to various application markets, such as the Xiaomi application market, pea pod, and application treasure.

But even if submitted to the various application market, your potential users may not download the app ah?

Not every user knows about this app?

Know this app, how to let the user press the download button?

These are issues that the marketing staff in the entrepreneurial team need to address.

When the user downloads the application, how to ensure that users will often use the app, how to ensure the user's activity, this is the work of operators.

Postscript

This is probably the entire app development process.

The above project Management Section, described relatively simple, detailed project management please see I previously published blog: http://blog.csdn.net/newjueqi/article/details/19011017

It is difficult to distinguish the powers of many entrepreneurial teams. For example, in a startup team, the app backend is a part-time operation, even a front-end. The reason is simple, no extra staff to do.

Moreover, in many teams, there is also a multi-job situation. For example, I know a startup team, on 4 people, one founder, 1 backstage, 1android,1ios, according to this personnel distribution, in addition to development, all the work is the founder to do.

In short, in a startup, the ability to grow quickly, because a lot of problems to you to deal with, rather than in large companies, only a screw. But at the same time, in the start-up company, the requirements of personnel is relatively high, a special how long, overtime rather than what strange things.

App back end series articles Total Directory

   "author" 曾健生
" QQ "190678908
" public number " Appbackend
" Sina Weibo "@newjueqi
" blog Http://blog.csdn.net/newjueqi       

How the 4.app is tempered