I recently saw a girl in the group, telling her that she chose Android from the beginning, and after studying and struggling very hard, she finally had to give up facing the current environment. After reading it, I really feel sorry for her. If I entered the industry a few years earlier, the result would be much better than now, but unfortunately, this is the reality.
This is the era of making fine products, not the era when a product could attract investment and cheat clicks. Boutiques need more professional talents, which means that the quality requirements of APP developers will be higher. The market will return to a normal rhythm. How much money you spend depends on your ability and product.
What is the role of Android Jetpack components?
-
Navigation: A tool class used to manage Fragment switching. Visualization, bindable controls, and support for animation are its advantages.
-
Data Binding: Needless to say, we all know that to accelerate the creation of MVVM.
-
Lifecycle: It is an important reason why we can handle the life cycle of Activity and Fragment. Fragment and Activity in AndroidX have provided default support for Lifecycle.
-
ViewModel: As the ViewModel layer of MVVM, it has lifecycle-conscious processing and UI-related data.
-
LiveData: Like RxJava, it monitors data. The advantage is that there is no need to deal with the life cycle, no memory leaks, etc.
-
Room: A powerful ORM database framework.
-
Paging: An easy-to-use data paging library that supports RecyclerView. WorkManager: a flexible, simple, delayed and guaranteed execution background task processing library.
Why you might choose Android Jetpack
The following may be the reasons why you would choose Android Jetpack:
-
It is more convenient to use together: Because many libraries in the Android Jetpack component provide support for other libraries, for example, Room and Paging provide support for LiveData.
-
Backward compatibility: Basically every component provides support for lower versions.
-
Support RxJava: Due to RxJava's powerful ecological environment, almost all data-related components support RxJava.
-
Reduce the amount of code: The MVVM mode built with Data Binding + ViewModel + LiveData or RxJava can significantly reduce the amount of code, and it will be more convenient than the usual MVP mode, without the need to actively update the UI.
-
No need to bundle: Android Jetpack series components can be used without bundles. If you only want to use a single library in it, you can rely on only one library.
Should I learn Android Jetpack?
To learn, you must learn. For Google, Android Jetpack is a manifestation of their determination to reorganize and unify the Android ecosystem. The content displayed by Android Jetpack is also the direction Google wants to expand and maintain. For the majority of Android developers who have long struggled with the choice of third-party libraries, this is a beacon provided by Google.
Perhaps, some of the libraries of the Android Jetpack series are not mature enough to become your first choice for work, but in-depth study of Android Jetpack components will provide you with an opportunity to communicate with Google's bigwigs and bring some ideas for your daily development.
At last
For the convenience of friends with learning needs, I organized all the materials into video tutorials (in fact, it took a lot more effort than expected). Due to the limited space, they are all placed on my GitHub. Click to get them for free!
Androidndroid architecture video + BAT interview topic PDF + study notes
It’s easy to be a programmer. Being a good programmer requires continuous learning. From junior programmer to senior programmer, from junior architect to senior architect, or to management, from technical manager to technical director, every stage Need to master different abilities. Determine your career direction early to get rid of your peers in your work and ability improvement.
- No matter what your current level is, you must continue to learn that there is no chicken soup. Others seem to be effortless, but in fact they took a lot of effort. These four words are my advice! !
- I hope that every IT engineer who works hard will get what he wants, because we have worked so hard and we deserve it.
It’s easy to be a programmer. Being a good programmer requires continuous learning. From junior programmer to senior programmer, from junior architect to senior architect, or to management, from technical manager to technical director, every stage Need to master different abilities. Determine your career direction early to get rid of your peers in your work and ability improvement.
No matter what your current level is, you must continue to learn. There is no chicken soup. Others seem to be effortless. In fact, it takes a lot of effort. No one can casually succeed.
。
No matter what your current level is, you must continue to learn. There is no chicken soup. Others seem to be effortless. In fact, it takes a lot of effort. No one can casually succeed.
Come on and encourage each other.