Shulou(Shulou.com)06/03 Report--

This article mainly explains "how to understand retrofit grammar". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to understand retrofit grammar".

1. Pursue high salary

Compared with small factories, wages in large factories will be much higher. The specific number range will not be detailed, but the big companies as a whole will be much more generous, as long as you can pass the interview, you will have a chance to get a 30% or more salary increase, not to mention that the year-end bonuses of big companies will not be arbitrarily deducted by "unscrupulous" bosses.

two。 Pursue stability

Last year, the overall environment was not good, and many companies laid off staff, especially small and medium-sized factories that were not very profitable, such as a regiment or a drop. For large companies, the probability of layoffs will be much less, after all, the benefits of layoffs are far less than the negative effects and falling stock prices.

3. Pursue career development

In the past two years, many fast-growing enterprises use double salary to go to BAT to poach people, such as Toutiao, pinduoduo and so on. Therefore, from the perspective of long-term career development, BAT's working background is as popular as students graduating from Tsing Bei. With the background of BAT, you will have enough initiative to change jobs, be promoted, become a technical manager or an architect in the future.

1. Kotlin

Kotlin is often seen as the next Java, sponsored by Google and JetBrains (Android Studio developer). Java has been the preferred development language for Android applications from the very beginning, but Kotlin has become popular rapidly in recent years, and now nearly 60% of the 10000 Google Play applications use Kotlin [3]. Although you will continue to use Kotlin in a few cases where you need to access the underlying native code, in other cases, Kotlin can be a substitute for Java.

The main advantage of Kotlin is full interoperability with Java, which means that developers can migrate old code as much as possible without having to completely rewrite the entire application. The two languages are so compatible that Android Studio can even automatically convert from Java to Kotlin.

This compatibility, coupled with cleaner syntax and hundreds of minor improvements, makes Kotlin the fourth most "most popular" and fifth most "wanted" programming language in StackOverflow's 2019 developer survey [4], and the highest of all mobile programming languages.

A good way to migrate an existing application is to convert an existing Java file to Kotlin when you modify it. Although this means that you have to convert frequently edited files, which will increase the complexity of code review (such as facing potential conflicts), because the converted area can be reviewed, you can ensure that any problems can be found.

Currently 86% of the Kotlin code used in Candyspace (and growing), the remaining 14% is utility / conversion code, which has not been changed for some years.

2. Jetpack

Google's AndroidX/Jetpack library is a set of utilities designed to simplify common application requirements. For example, Room [5] for a database on a device, or LiveData [6] for updating the display when the underlying data changes.

With the Jetpack library, the new project saves the hassle of reinventing the wheel and does not have to wait for other developers to open up their implementation, and every developer now has access to those basics. These libraries are updated frequently, new features are constantly introduced, and bug fixes are released in a timely manner. Because these libraries are built to work together, more use of AndroidX libraries helps minimize accidents in applications.

Using Jetpack libraries from the start of development work can save hundreds of hours, but we can also migrate existing applications to Jetpack libraries. Although it may seem troublesome, because these libraries are very popular, guidelines for migration efforts are also easy to find. At the very least, the underlying Android elements (views, fragments, and so on) can be automatically converted [7].

At Candyspace, we used Data Binding and ViewModel, and may soon add Room and Navigation.

3. Modular design

For a long time, the application has been built into a huge "application" module, which contains everything the whole application needs. While this does make it easier to share resources, it also means that some parts of the application cannot be reused by other applications / open source projects; more importantly, the entire code base must be recompiled when changes are made to the application.

In contrast, if the application consists of many smaller modules, you only need to recompile the code that made the changes, greatly reducing the build time. In addition, modular design opens the door for advanced Android features, such as real-time applications-users can use some of the functions of your application without installing any content, and dynamic features-install various parts of the application on demand.

Splitting an existing application into multiple modules can be a complex task, as it will uncover previously hidden problems ("what is DateUtility? why does every class need it!?" But once the transformation is complete, the code base will enter a healthier state In addition, if a new application requires similar functionality, existing modules can be quickly reused, saving a lot of time!

An example of modular application architecture

While designing a modular architecture can be a complex task, I have written some guiding principles [8] that were inspired by Nikits Kozlov's article on modularity and build time [9]. Plaid also wrote an article about their experience in migrating to modular design [10].

At Candyspace, our application designs are fully modular to minimize the disruption of build time to development work.

4. App Bundle

When using traditional APK to distribute applications to users' devices, all resources prepared for all devices must be installed. This means that there may be five copies of each bitmap image (for different screen precision), multiple library versions for different device architectures, and even multiple sets of margins and padding values.

When you use App Bundle to distribute an application, users download APK that contains only the resources they actually need. As a result, the average application size will be reduced by 20%, and the application size will be reduced more significantly after the unoptimized application changes the format.

Example of reducing the size of an application

App Bundles was born 18 months ago, but more than 25% of applications have been installed using this format! This is the format recommended by Google [11], and most apps can use it with little change, simply by processing App Bundle's signature on the Play store.

At Candyspace, we are migrating to App Bundles while trying to avoid disrupting our existing workflows (Slack, QAing builds, non-Google Play installations). Alistair Sykes's article is a great migration reference [12], taking into account CI servers, Slack, and Google Play internal application sharing.

Thank you for your reading, the above is the content of "how to understand retrofit grammar", after the study of this article, I believe you have a deeper understanding of how to understand retrofit grammar, the specific use of the situation also needs to be verified by practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.