The State of Android Development in 2023
The current situation of Android development is roughly like this. Talents are seriously oversaturated, coupled with the prevalence of cross-terminal and small programs, the jobs of native clients (Android and iOS) are further shrinking, and it is extremely difficult to find employment after entering the industry. The current situation is that there is a serious surplus of mobile terminals, hundreds of people are vying for a job, the competition is fierce, and the involution is tragic.
In general, the status quo of the Android development market is fierce competition and serious involution. Many companies have higher and higher requirements for developers, while the benefits are shrinking.
So why is Android development facing such a crisis?
Now the programmer industry is as long as you have a hand, the threshold is getting lower and lower, no education is required, and there is no gender restriction. As long as you want to, spend some money to study for half a year, and you can directly play. This kind of wholesale is extremely efficient. As a result, Android developers have come in one after another, and the explosive growth of the number has had a great impact on the original older generation of Android development. Newcomers in the industry bring new work models, new work attitudes, and better energy and lower wages for the boss to choose.
With such conditions, it is understandable that you have been optimized. For the same thing, others are more cost-effective and have higher output than you. Why not use young people with high cost-effectiveness? Of course, people will grow old, which is an endless loop for most people.
Knowing how to draw a UI is called client development? Remember, what is lacking is always real talents, not make up numbers. When the tide recedes, you will know who is "swimming naked".
And now no one can "swim naked" in the Android industry.
How to avoid being optimized?
Widen the gap with programmers of the same age and become a big brother in his eyes, who can optimize you.
How to widen the gap with programmers of the same age:
1. Poor knowledge:
For those who are new to Android, they may not know how to display a picture on the phone, or how to create a custom view. But for skilled Android developers, these are the basics. This is the gap in knowledge reserves.
Knowledge and information are key factors in analyzing and solving problems. When the knowledge reserve is insufficient, it will feel overwhelmed and unable to start. Therefore, the knowledge gap is the main difference between developers at different levels. So this is why you should read more books and see the output of some big shots. Standing on the shoulders of giants, you will not only broaden your knowledge, but also increase your reserves very quickly.
2. Poor skills:
A new Android developer may only have mastered some basic technologies. But if he is asked to be responsible for the architecture and design of the front-end module of a new project, he may not be competent. Because he does not yet have such architectural capabilities, design capabilities, and abstract capabilities. Without the corresponding skills, he cannot handle complex problems.
Developers at different levels have significant differences in skills. A high-level developer has a whole toolkit, while a low-level developer might only have a screwdriver.
Nowadays, many people are not interested in new technologies and are unwilling to touch them. This is when you will widen the gap with your peers. Although you will feel tired for a short time, if you really want to do this job, you will quickly devote yourself to it. ,
3. Differences in motivation
If you pay attention to the colleagues around you, you will find:
Some people are proactive, willing to do everything, enjoy doing everything, and can learn quickly, act quickly and produce results that meet expectations.
For some people, every time you assign a task to him, even if he can handle it, he will push back and forth. This is the motivation gap.
When you know how to do it alone, but choose not to do something, it is often a lack of motivation to do it; when you don't want to do something, you can always find thousands of reasons to refuse.
No matter what the reason is, if you don't do something, you will have one less opportunity to hone and harvest. Over time, others will grow up in action, while you are still standing still.
4. Differences in habits:
Some developers plan what to do today every morning, review what they have accomplished and what they have not accomplished today, and plan what they will do tomorrow at night; some developers don’t, they arrive at work every day, turn on the computer, browse news, play games, drink tea, and chat with people.
Some developers will review and summarize every week, write a weekly report and send it to their immediate superiors; for some developers, even if the manager emphasizes a hundred times that "the weekly report will be issued every Friday", he will turn a deaf ear to it.
Some developers will say "impossible" when encountering a bug in the test; some developers will say "let me see".
Some developers will say "let me try" when they encounter a problem; some developers will spread their hands and say "this is too difficult, I can't handle it".
When working on a project, some developers will sort tasks by priority, and do the high priority and difficult ones first; some developers will pick the simple ones first every time.
Accumulated behavior becomes habit, accumulated habit becomes character, and accumulated character becomes life. Good habits lead to good results, and bad habits lead to unsatisfactory results.
Your future is determined by your habits. So, please take a look at yourself, what habits will allow you to accumulate more and more abilities and consolidate them; what habits will make you lower and lower, weaken them, and discard them.
It takes 21 days to form a good habit, so you need to persevere.
5. Environmental differences:
Everyone knows that those who are close to vermilion are red and those who are close to ink are black, and the environment will shape people to a certain extent. You will become the average of those around you.
If you are in a team with a strong technical atmosphere and many excellent developers, you have a high probability of growing faster.
It's not that you deliberately alienate those colleagues who are not in the atmosphere. You just need to do what you should do, and try to refuse when you should not do what you should do.
raw materials needed
If you want to widen the gap with programmers of the same age and stand out among high-end talents, you must continue to learn and improve your technology. Many people are unable to learn effectively due to lack of information. Here I will share with you an advanced learning guide for Android Framework to help more programmers accumulate knowledge and improve quickly!
Due to the excessive content of the document, in order to avoid affecting everyone's reading experience, only some of the content is shown here with screenshots, and there is a free way to obtain the full version at the end of the article! (At the end of the article, there is also a small benefit of using the ChatGPT robot!! Don’t miss it)
"Android Framework Source Code Development Secret"
This learning manual deeply analyzes the Android system source code, explains in detail the initialization process of the Android framework and the working principle of the main components, and aims to introduce the core concepts and technologies of the Android Framework through examples and cases, so as to help developers better understand the design and development of Android applications.
This manual is suitable for programmers with certain experience in Android application development, hoping to help developers better understand and master this technology through in-depth study of Android Framework.
Chapter 1 System Startup Process Analysis
The complete startup process of the Android system can be divided into three stages: the Linux system layer, the Android system service layer, and the Zygote process model from the perspective of the system level; knowledge points: the first section Android startup
overview
,
the second section init.rc analysis,
the third section Zygote, and
the fourth section Interview questions
Chapter 2 Cross-process Communication IPC Analysis
As a mechanism for Android inter-process communication, Binder can be regarded as a driver. In Android, common inter-process communication such as system class: phone calls, alarm clocks, etc.; self-created: like WebView, video playback, audio playback, large image browsing, etc.
Chapter 3 Handler Source Code Analysis
Section 1 Source Code Analysis
Section 2 Difficult Questions
Section 3 Handler Frequently Asked Interview Questions
Friends in need scan the QR code below to get it! ! ! !
At the same time, a WeChat group chat robot based on chatGPT was built here to answer difficult technical questions for everyone 24 hours a day .
