Six phases and six realms to become an Android guru

To become an Android player is generally divided into six phases:

Stage 1: proficient in Java SE, especially for its internal classes, threads, concurrency, and network programming, which requires in-depth research; proficient in HTTP-based programming, the process and details of POST and GET requests are clear; Basic Java Web programming can be performed, which is better if Java EE can be used;

Stage 2: proficient in the use of Android core APIs, such as the APIs and Context involved in the four major components, and proficient in the programming of core interfaces, such as ListView; at this stage, most basic application development can be done;

Stage 3: proficient in the principles of the application framework, especially the understanding of IoC and Its Application in the Android Application Framework, and proficient in the application of 23 basic design modes in Android;

Stage 4: proficient in JNI, proficient in C/C ++ component development in the Android class library, and be able to use the JNI mechanism to port the existing C/C ++ component into the core component of the application framework; ability to modify and compile your own application framework;

Stage 5: Make your own Android system, both at the underlying layer and at the upper layer. You can design and implement a relatively large Android system based on your actual needs, for example, lead a large team to make their own Android mobile products;

Stage 6: potential. All thinking goes into the "trend" thinking. Everything is a matter of thinking. It judges and predicts the situation of Android, leads the market, and leads to a paradise of freedom.

If you are determined to become an Android expert, if you are patient, you will be satisfied ".

"Is it easy to do things in the world? For this reason, it is easy for the hard person. If not, it is also difficult for the easy person. Is it easy for people to learn? It is easy to learn. If you don't learn it, it is also difficult to learn it ." Want to become an Android guru? This is not as easy as writing a few lines of code, but it is not impossible.

How to do it?

1. Learn to be lazy! Strange? However, you must have heard and experienced that the world is promoted by lazy people to some extent. The life lies in laziness, and lazy people create the world. Of course, laziness is also really silly to stay there and do nothing, but to say that we should be good at coming up with a better way to do things, so that we can save a lot of time, there will also be more opportunities for laziness, and colleagues will also become lazy. How to be lazy in Android? The article "How to become an Android guru" describes how to learn laziness in Android and share it with friends.

2. proficient in Android architecture, MVC, common design patterns, and control reversal (IoC): Is this difficult? "It is easy to learn. If you don't learn it, it is also difficult to be easy ."

3. code with high reusability, scalability, maintenance, and flexibility: Android Application Development uses purely Object-Oriented Java as the development language, naturally, it inherits the excellent idea about Object-Oriented Java. How can this problem be solved? The article "How to become an Android guru" shares with friends how to write reusable, scalable, maintained, and flexible code in Android.

4. Efficient code writing: efficient code writing and efficient code writing seem to be a natural enemy. It seems that the development speed is up, and the execution efficiency of the program goes down; the execution efficiency of the program goes up, and the development speed goes down. Please refer to the article "How to become an Android player" to learn how to solve the problem.

5. learn at least one server-side development technology: Isn't it wrong? Do you still need to learn server-side development technology to become an Android master? Yes, yes!

"Cool, there are two monks: one is poor, the other is rich. The poorest man said in the rich: "What is the South China Sea I want ?" The rich man said: "Why is the child moving forward ?" Said: "I have a bottle ." The rich man said: "I have never been able to buy a boat for years. Why !" The more next year, the poorer people will return from the South China Sea, and the richer the people will be pale. When I go to the South China Sea in xishu, I do not know how many miles are there, and those who are rich cannot, while those who are poor are at it. The determination of people is not as good as that of SHU"

If you are determined to become an Android expert, if you are patient, you will be satisfied ".

 

 

 

Android encourages weak coupling and Component Reuse. In Android, MVC is embodied as follows:

1) View layer (View): it generally uses XML files to describe the interface, which can be easily introduced during use. Of course, if you know more about Android, you can think of using JavaScript + HTML as the View layer in Android. Of course, communication between Java and JavaScript is required. Fortunately, android provides convenient communication between them.

2) control layer (Controller): the important responsibilities of the control layer of Android usually fall on the shoulders of many acitores. This statement also implies that you should not write code in Acitivity, another reason for this is that the response time of Acitivity in Android is 5 s. If time-consuming operations are put here, programs are easily recycled.

3) Model layer: database operations and network operations should all be processed in the Model. Of course, operations such as business computing must also be placed in this layer.

3. Design Mode and IoC (control inversion)

There is no doubt that the reason why Android can become an open and diversified system is inseparable from the exquisite application of the design model. As long as you observe it with a little attention, you will find that the combination of A design mode or design mode is everywhere in Android. the following design mode is something you must master to easily control Android:

L Template Method mode

L Factory Method mode

L Observer Mode

L Abstract Factory Mode

L Adapter Mode

L Composite mode

L Strategy Mode

L State Mode

L Proxy Mode

L Bridge Mode

L Iterator Mode

L Mediator Mode

L Fa? Ade Mode

 

The charm of the Android framework lies in IoC. During the development of Android, you will always feel the great convenience that IoC brings. For Activity, the following functions are automatically called by the framework:

Protected void onCreate (Bundle savedInstanceState );

Instead of actively calling the code, the code written by the user is called by the framework, which is reversed! Of course, the meaning of IoC itself is far more than that, but in this example, we can also see the huge benefits of IoC. Such examples can be seen everywhere in Android, for example, database management, for example, the call of the SAX Handler in Android. Sometimes, you even need to write a simple IoC implementation by yourself. The multithreading shown above is now a description.