I often discuss with many entrepreneurs and find that many people have good ideas, but they don’t know how to implement them. Today, I will write an article on how to guide everyone to take the first step. Many people usually misunderstand one thing and think that programmer development can be done one step at a time. Step by step splicing out my own ideas, I have a function point, let the programmers develop it, and one day my ideas will be realized.
It is true that a good programmer can do this, but our thinking is broad and infinite. We can't let programmers write code forever to follow wild ideas and unplanned execution, right? In this era of mobile Internet innovation, I think the first step in APP development should be every entrepreneur thinking about how to define the important attributes of your APP.
If you are a parent, as a teacher, you must often hear:
"I don't know how to write an essay"
"I don't know how to write this report"
and when you ask him further: "Then what do you think is the problem? "
They often answer: "I don't know where the problem is."
From here, it can be found that under the definition of the standard education fool-like thinking, many people are used to waiting for the best solution to appear, which is why many software outsourcing When dealing with users, the company will constantly adjust the development plan in the early stage, and then organize and modify it according to the user's understanding, instead of first developing and then following the user's ideas to make development adjustments. Because once the development process is involved, if a large amount of development labor costs are modified by the first prototype idea, it will be accompanied by a lot of waste of development costs, but the prices charged by outsourcing companies are generally higher, and awareness determines the state of survival. With such fees, outsourcing companies have no profit. In the current commercial society, will most people do things that do not make money?
Now let’s go to the key points, how to define the thinking of APP development. According to our programmer’s 500+ development experience, I have made some simple summaries, which can be roughly divided into: analyzing problems, splitting problems, solving problems , and how to make breakthroughs for everyone These questions are what I will talk about below, taking a recently developed APP as an example:
The first thought: how to use it?
At the beginning, we will guide the customer, the maker of this APP, to start from the user's point of view:
If you want to use the APP to calculate your BMI index, what kind of operation method will it be in your imagination?
At this point, there may be many answers:
I want to say my height and weight, and my BMI index will appear on the screen of my phone.
I want to use typing, first enter the weight, then enter the height, press the OK button, and the screen will appear My BMI
This time when our clients are brainstorming and trying to imagine themselves using this "app that hasn't been developed yet".
The second step of thinking: what does your APP probably look like?
Next, we will guide customers to think:
Based on the ideas and situations you put forward, what do you think the APP will look like?
At this stage, the appearance of the entire APP has probably been sketched, and the elements of each interface and the function of the corresponding users have also been standardized. Although none of us can design, at least, if you are given a pencil , I believe that 90% of people will draw the following things like the customers I communicated with recently. You don't need to know how to operate a computer. You can ask professional people to do these restored designs for you, as shown below:
Schematic diagram (hand-painted by a customer)
The third step of thinking: dismantling and operation
Finally, we will find that the definition of each APP function element should have its own user behavior definition, and each behavior definition is every little function of the APP you want to do At this time, the project manager team of the Programmer Inn will split your idea and function points and explain the development process as follows:
1. Prototype design (high-fidelity restoration)
2. UI design (visual experience in place)
3. Front-end development (Continuous processing)
4. Back-end development (back-end development and back-end development are two different things)
5. Make A function
6, make B function
7, make C function
8, ...
9, test, check and accept
10, pay.
Project Manager's Essay (Graphic)
Finally, the project manager of our programmer's inn will split developers who have work experience in the matching platform according to all the function points, form a development team, and estimate a quotation based on the labor cost to the user. If the user thinks there is no problem, you can The hosting fee is first sent to the platform, and after the final acceptance, the platform is notified to pay the developer.
Although it seems that the whole process is a bit complicated, why do we have to put so much emphasis on process development? Because I am also a pseudo-developer, there is a saying in most programming teams:
"When the problem is clearly described, it is half solved!" (From the American philosopher and educator John Dewey)