Thinking about the growth path of Android programmer

I had thought about writing this topic before, but I didn't know it before, I was just reading other people's opinions. Last night, I read this article "Product Manager Yonghao: User experience Exploration, no end", this article describes Yonghao on the hammer mobile phone design details, and Yonghao on the product manager's view, understanding. It happened to read this article, I think of the Android Programmer's growth path.

One of the growth paths, you can make the various interface effects required by the product manager.

Android programmer, is the application of the Android system, an application is a product. I think so, you can make good products, then, you are a good Android programmer. The growth path one, is from the good product realization angle to look at. That is, in fact, for a good product, design and consideration, most of it is done by the product manager, then, the Android programmer only need to be responsible for the implementation.

Of course, some good products, their implementation is not difficult, is easy, but most of the good products, their implementation, not very easy. For example, the following products (with Word of mouth products):

Efficient TODO:

, click on the record icon, when it comes in, is a well-arranged animation, it is not stiff to arrange, it has an arrangement of the process. This animation process is not easy to implement.

There are also some small animated details for other applications. I used the process, I found that most popular, easy to use, to attract users of the application, they will be used in the details of the animation effect, not stiff changes, there is a gradual process.

Pea Pod Mobile Client:

When you swipe up, the icons for "apps", "Games", "Videos", "e-books" will also slide up, and will gradually shrink to the top, which shows a process on top. This process, I kind of like it. Not all of a sudden, suddenly, at the top. This is also an animated detail, this implementation, and not immediately be able to work together.

Hammer Clock:

The stopwatch will change when the button on the right side is down. This is also an animated effect. This kind of effect, realize, I think is not immediately made out.

In general, in this growth path, the product manager requires, or think of a variety of effects, you have to find a way to achieve, and can achieve. In short, if the system does not provide a ready-made effect, you have to write a set of code to achieve. In fact, I found that at least my own use of the good app, its function and effect, are not directly using the system-provided classes, can be implemented in a few.

Walk down this path, you are the equivalent of a variety of mobile phone plaything of the realization. Because good app, good product, I think, it is actually a plaything of human life.

Growth path two, go to Product manager, project manager direction

I think, an Android programmer, because the everyday thing is to do the development of the app, then, he will inevitably come into contact with the various apps, or I think, he should be exposed to various apps, so that is good. In this case, learn about the various apps, and familiarity, which is helpful for becoming a product manager and project manager. Because, in fact, product managers, project managers, the purpose of their existence, is not to organize people to get something to come, and then make sure that the user pays for the item. Then, you touch and use a variety of apps, and you will have to make something out of it and feel it. Because, you are in the process of using, you will experience the various details, and then, you will be in the product, will trigger you to do more associative thinking.

This is a reason. Another reason, when you are in the realization, hear all kinds of needs, hear the product manager's narration, in a word, I think, you will always know, why your product to do so, you always know how the user's needs are related to your implementation. This is a second reason.

Of course, with the above accumulation, you have to learn the user's psychology, demand and other aspects of knowledge, if you are going in this direction to go.

The above is my understanding of the growth of Android programmers, thinking about the results.