Individual developers' ups and downs [change]

Currently, mobile development is very popular. Many individual developers are developing applications independently, and some even use business time to develop apps. I have experienced these experiences. The ups and downs are only clear to myself. The only sweetness is the moment when I get the money, but I am tired and depressed.

 

Background:

I started a project and developed an Android app to check whether I would like to participate. At that time, I was learning about Android development. I made two simple apps and agreed quickly. After the meeting, it was said that it was based on app development in the current market. The function points were on an A4, including the teacher version + fmaily version.

The features of teacher/fmaily are about 15 pages each. Including common login, registration, list, details, chat (refer to the existing code framework), message reminder and so on. The functions are simply checked and required to be completed in two months. Although I know the time is very tight, it's okay to hurry up. As a result, it is a tragedy.

 

1. Develop two apps for a company (teacher version + fmaily Version)

1. task: Android client + IOS Client

2. Personnel: one android client (me) + two server developers (C ++) + one IOS developer. The artist is in charge of the newly recruited mm.

 

Ii. Development

In the early stage, we spent two weeks porting a certain app and simply Porting some of the same functions, including chatting. In this way, the basic skeleton of the fmaily version is displayed.

 

Two weeks later, the company mm sent several prototype images. Let's do it first. Then, I took advantage of the evening and weekend time to deal with it quickly, so that I had to go through the three days, according to the prototype picture to get the interface out, everything went smoothly.

 

After a week, the server chatted with several interfaces, and the related protocols of the interfaces changed. Then I modified the protocols based on the original foundation and found that there were too many things to be changed, this is not the case. After three nights of modification, the program can finally be compiled but cannot run. Then, I stayed up late to call the joint call interface, and joined the weekend for a week. The chat function can finally run. At this time, you can still stick to your teeth ......

 

In the next week, the server interface and UI design were gradually processed. Every night, we spent three or four hours to implement the basic functions. The time seemed quite long, but on the evening of the hot day, in fact, it cannot do much ......

 

 

Continue to suffer, just like this for a month. Later, the company hoped to give a demo one week later. At this time, we found that our overall progress was somewhat delayed. First, only a small portion of the server interfaces are provided, and only some of the UI interfaces are provided over the past two days. We spent five nights and a weekend, thinking, we had to stay up late again .......

 

It has caught up with many versions of the company's requirements recently and is already very tired at the company. It has actually been around. when I got home, I didn't even want to open my computer, but I still had to work hard on my head. I improved some basic functions and went to bed at every night, day after day .......

 

After the weekend, I thought I could relax a little. As a result, during the joint debugging of basic functions, the progress of the joint debugging was too slow, the server would not work for a while, and the program would be suspended for a day, I only called a few interfaces, so I had to have a short break and have dinner with my classmates (my wife's dinner is full, so we should be rewarded ). After dinner, I continued to fight until. At this time, I was exhausted. After taking a bath, I went to bed ......

The next day, I slept a little late and got up. After that, I started coding and got stuck for a day. At, some functions were finally used, so I went to bed.

 

After that, the demo was sent to the company. The company experienced a lot of problems and asked us to change the listed problems. There was no problem with the next acceptance and a deposit was made. at this time, I am exhausted and have no joy in this reply.

 

In this way, we entered the tense coding .......

 

I don't want to say anything when I get home except work or work every day, but I still have to do my work. After a long time, my wife has an opinion, which affects my rest and daily work. Because I didn't talk to my wife a few words every day when I went home in the last month, and my husband and wife had to get up at every morning (work at), while I went to work. I have had a quarrel with lop several times. I always said that you should share more housework and be considerate of me. Now, it's really embarrassing for you to think about it!

 

In the future, the pace of life has passed another month. At this time, I am exhausted. In my heart, I really don't want to do it, and I don't want any money. This time I learned it.

 

Finally, after all, I had to stick to it for another two months. The teacher version and the basic fmaily version both came out, but there were still many problems, however, you cannot solve these problems.

 

Iii. Summary

Now, in retrospect, it took four months to complete the basic functions planned to be completed in two months. At this pace, it would take two months. Here, we will summarize the reasons that make it easy for you. I hope to provide some reference for independent developers.

1. The requirement function is too simple. It is just a little simpler than the function. I think it is okay. It is too simple to identify potential risks.

2. During workload evaluation, check whether the existing functions meet the requirements, the UI is changed, and whether the existing protocol interfaces are copied. It's just taking it for granted that it can be changed. when the results are done, it's totally different.

3. No detailed work plan or schedule has been prepared. There is no time to process server interfaces and UIS. We are doing things step by step.

4. Human factors: The uidesign is a novice mm. The design pictures are simple fixed width and height pictures, and the picture at won't be done; the uidesign comes late and thinks it is the same as the existing app function. During result processing, although there are no major changes, it is time-consuming to modify the changes here.

5. Time factor: everyone is using their spare time for development, and time cannot be blank. Catch up with the company's heavy tasks, time cannot be guaranteed.

Iv. Dream

Although I have not lived a person's life over the past few months, I still have my own dream: to be an app of my own. No, it took another two months to live a non-human life. I made an app for programming and learning. You are welcome to download and try it out. I will write down all my development experiences in the future.

Individual developers' ups and downs [change]