beginning
In Android development, hot fix technology is used by more and more developers, and there are many mature open source frameworks on the market. But for most developers, hot fix is still a familiar and unfamiliar word. Just knowing the role of hot repair and using the framework is not meaningful. We also need to know the principle of hot repair, so that no matter how the framework changes, as long as the basic principle remains the same, we can quickly master it, or write a hot repair framework suitable for the project by ourselves.
A few years have passed, desktop development has basically died, now it’s Android development’s turn?
Have you noticed the difference between these? Desktop development is dead to the entire ecology, just like the real economy has turned to Internet shopping, the entire ecology is dead, resulting in all kinds of desktop development positions no longer recruiting people, making development, product, and operation must be original SEO optimization, looking for website traffic to move to the mobile terminal.
Now Android is different. It is not dead. On the contrary, the mobile Internet is now very mature, and with the advent of 5G, the opportunities will greatly increase.
So why do people think that Android development is not working? It's nothing more than the gradual transformation of native Android development, because Native development is time-consuming but cannot be cross-platform. It cannot be like RN\Weex\Flutter, writing the code once and running on multiple terminals.
Capital is profit-seeking. Gu Jiahui once said: Companies that are not profitable are all playing rogues. Faced with such an efficient production method, if you are the boss, would you not choose? Especially startup companies.
So the question is, why is there still Android Native development? Because it is native, all interactions and efficiency are the highest. For large companies, not only speed, but also APP operating efficiency and various indicators must be emphasized. Therefore, large companies are more inclined to Native development, while small companies are more inclined to rapid development.
Therefore, many small companies no longer recruit Android Native development, which leads to the reduction of Android native jobs. For beginners, small companies have few jobs and large companies can't get in. This is why training companies no longer train Android. This brings up the argument that Android is dead. So, it's not that Android is dead, it's that the threshold is high.
Now training companies like to train H5, and the promise of learning to ensure employment will never change. This is because the syntax of RN\Weex\Flutter is similar to H5. After learning H5, in addition to being able to do the original WEB development, the cross-platform language RN\WEEX\Flutter greatly increases the number of H5 positions, so H5 is not easy to learn. It is not because of its popularity, but its employment threshold is low.
Similarly, even if you enter the cross-platform development language from H5, do you think you don’t need Android native if you know RN\Weex\Flutter? It's just that the underlying architecture of Androd remains the same. Android native is always something to learn. All upper-level cross-platform applications are implemented by native controls. There may be exceptions to Flutter, but Flutter is written in the Dart language, and everyone does not, and don't look down on anyone, and Flutter is perfectly compatible with Android natively.
From the perspective of the nature of merchants' profit-seeking, cross-platform development is a trend. Even if RN\Weex\Flutter hangs any day, another cross-platform language will come out to dominate the world. In this world, the only constant is change.
Therefore, Android will not die, but the threshold for Android will increase. If you want to make a difference in the Android field, you need to understand cross-platform development in addition to Android native. If you are a newcomer, I suggest that after you understand the basic use of Android, you should focus on cross-platform development and study, and find a job first (except for those who graduate from school and enter large companies). If you are an Android practitioner, I suggest that you learn cross-platform languages to make yourself invincible forever, and don't wait until the day when the black swan comes, crying without tears. (The full name of the black swan is the black swan event, which refers to unexpected events that are currently unpredictable)
Finally, in order to help everyone deeply understand the principles of Android-related knowledge points and interview-related knowledge, here are the 24 sets of Tencent, ByteDance, Ali, and Baidu interview questions that I have collected and compiled. I will organize the technical points into the video and PDF (in fact, than expected to spend a lot of time), including knowledge context + many details .
There are also advanced architecture technology advanced brain maps, and Android development interview special materials to help you learn and advance, and save everyone's time to search for information on the Internet to learn, and you can also share with friends around you to learn together.
Click:
" Android Architecture Video + BAT Interview Special PDF + Study Notes " can be obtained for free~
%E9%AB%98%E8%96%AA%EF%BC%81.md)" can be obtained for free~
There are a lot of materials for learning Android on the Internet, but if the knowledge learned is not structured, and when you encounter problems, you just taste it and stop studying it in depth, then it is difficult to achieve real technological improvement. I hope that this systematic technical system will provide you with a direction reference.