What about the source code? This is a headache, but the source code must be read. When reading the source code, don't delve into the details of the code, but pay attention to the flow of the code and try to dig out useful conclusions for application layer development. In addition, read carefully the comments about the class or method in the source code. When you don't understand the source code, comments in the source code can help you better understand how it works. Although this process is hard, there is no other way.
How to play custom view? My suggestion is not to learn custom views by learning custom views. Why do you say that? Because there are too many kinds of custom views and too many gorgeous custom effects, how to learn to play! We should look at the essence through the phenomenon and pay more attention to the knowledge points needed to customize the view. The following is a summary:
-Understand the sliding principle of views.
-Know how to achieve elastic sliding.
-Understanding the sliding conflict of views
-Understand dimensions, layout and view drawing.
-Then learn a few examples of existing custom views.
-finally, you can get a custom view, and the so-called change is the same.
It will take about 1-2 years to reach the technical level of senior engineers. Personally, I think this process can be shortened to 0.5- 1 year through the exploration of the art of Android development and the biography of Android. Note that reaching the technical level of a senior engineer does not mean that you can become a senior engineer immediately (affected by opportunities and job hopping), but it is very simple to become a senior engineer when you reach the technical level.
Technical requirements:
-A little deeper knowledge.
AIDL, messenger, binder, multiprocessing, animation, sliding conflict, custom view, message queue, etc.
-Book recommendation
Exploration of Android development art, Android group biography.