foreword

The daily work of most Android programmers in China is in the business layer, that is, they are constantly writing the code of the "application layer" according to various needs. In this area, enough experience and proficiency in commonly used development tools and third-party open source are enough to deal with it.

What's more, we strive for perfection in some subtle details, such as good programming standards, solid bug handling methods, and a better working attitude. The in-depth technology has little meaning. The memory mode, multi-threaded development, HashMap principle, etc. answered in the interview will not affect your daily work in most cases. This is a comfort zone. If you don't seek a breakthrough, you will sit back and eat nothing. There are many programmers like this on the market.

In the domestic environment, company layoffs, application market saturation, small programs, hybrid programming, 5G era, etc., continue to compress the living space of traditional Android programmers. Older Android programmers are not younger than younger, and their "net worth" is generally higher. Core competitiveness has been weakened.

Do older programmers have no advantage?

Of course not, the following points are the advantages that young people can’t compare to:
1. After seeing enough codes and technical solutions, many problems that novices don’t know how to start are already familiar with the road. Many solutions do not need to be created by themselves. Similar problems have been solved before, so just use them directly. save time and energy.

2. The time for coding and debugging is much less than when I was young. On the one hand, modularization is done well, and a single module will not be complicated. On the other hand, the pits that novices are easy to step on have basically been stepped on, and writing code will be avoided instinctively. Even if you accidentally step on it, it is easy to realize the problem.

3. With the accumulation of programming experience, the development ability will continue to improve. For the same business, experienced people can implement it in a more elegant and flexible way. When the business is modified, only simple modifications are needed to adapt to new needs;

4. With the accumulation of experience, the perception of performance will continue to improve, and you can realize programming in a more efficient way to improve the performance of the program;

But the above points are very barren in the Android application layer development. If you are a programmer at the Framework layer, it will be different. Not only that, age is no longer a barrier to your threshold, but a stepping stone on your way to success! !

When it comes to this, there must be some friends who don’t believe it and think I’m talking nonsense, but don’t worry, just read on and you’ll know if I’m talking nonsense.

Let's speak with facts. The following job map clearly states that programmers aged 30-40 are needed , and they can get an annual salary of 500,000-800,000 .
insert image description here

It can be seen that the industry still needs programmers with rich development experience, so older Android programmers should not be discouraged, because it is not completely without direction, Android Framework is a clear way! ! !

For friends who have no direction and learning materials, I have prepared a Framework knowledge system diagram and learning materials for you "Android Framework Source Code Development Secret"

Due to the limited space of the article, the content of the information has been presented in the form of screenshots. If you need complete information, you can scan the QR code at the end of the article to get it! ! !

First of all, I will post a map of the Frmaework kernel source code knowledge system compiled by the big guys of Ali P7. Everyone knows that a word is wrong, and efforts are in vain . I hope that everyone can learn according to the following system's Android Framework learning roadmap, so that the established knowledge system is strong enough!

insert image description here

study plan

At the same time, we have prepared the corresponding Framework source code study manual "Android Framework Source Code Development Secret"

Content coverage : Combined with project cases, analyze each part of the source code of the Framework layer in detail. The source code includes: system startup process analysis, cross-process communication IPC, Handler, AMS, WMS, Surface, SurfaceFlinger, PKMS, etc...

"Android Framework Source Code Development Secret"

Chapter 1 System Startup Process Analysis

The first section Android startup overview
Section 2 init.rc analysis
Section 3 Zygote
Section 4 Interview Questions

Chapter 2 Cross-process Communication IPC Analysis

The first section Service can also be understood in this way
Section 2 Binder Basics
Section III Binder Application
Section 4 AIDL Application (Part 1)
Section 5 AIDL Application (Part 2)
Section 6 Messenger Principles and Applications
Section 7 Server Callback
Section 8 Get Service (IBinder)
Section 9 Full Analysis of Binder Interview Questions

Chapter 3 Handler Source Code Analysis

Section 1 Source Code Analysis
Difficult questions in the second quarter
Section 3 Handler Frequently Asked Interview Questions

Chapter 4 AMS Source Code Analysis

Section 1 Introduction
Section 2 Android Architecture
Section 3 Communication Methods
Section 4 System Startup Series
Section 5 AMS
Section 6 Analysis of AMS Interview Questions

Chapter 5 WMS source code analysis

Section 1 WMS and activity startup process
Section 2 WMS Drawing Principle
Section 3 WMS role and instantiation process
Section 4 WMS Working Principle

Chapter 6 Surface source code analysis

Section 1 Creation process and software and hardware drawing
Section 2 Double Buffering and Surface View Analysis
Section 3 Overview of Android Graphics System

Chapter 7 Analysis of SurfaceFlinger Source Code Based on Android 12.0

The first section application establishes a communication bridge with SurfaceFlinger
Section 2 SurfaceFlinger's startup and message queue processing mechanism
VSyns of SurfaceFlinger in the third section (on)
The fourth section of SurfaceFlinger's VSyns (middle)
VSyns of SurfaceFlinger in the fifth section (below)

Chapter 8 PKMS source code analysis

Section 1 PKMS calling method
Section 2 PKMS Startup Process Analysis
Section 3 APK Scanning
Section 4 APK Installation
Section 5 PKMS Permission Scanning
Section 6 Silent Installation
Section 7 requestPermissions source code process analysis
Section 8 PKMS Interview Questions

Chapter 9 InputManagerService Source Code Analysis

The first section Android Input input event processing flow (1)
Section 2 Android Input input event processing flow (2)
Section 3 Android Input input event processing flow (3)

Chapter 10 DisplayManagerService Source Code Analysis

The first section DisplayManagerService starts
The creation of the second section DisplayAdepter and DisplayDevice
The third section DMS part of the process of turning on and off the screen
Section 4 Brightness Adjustment
Section 5 Proximity Sensor off-screen principle
Section 6 Update of Logical Display and Physical Display Configuration

Can code farmers only eat youth food, does the Internet really not require qualifications and experience?