Detailed steps of the Android build Module

You may still remember that we introduced some basic concepts about Android modules in an article by BKJIA. I believe you can have a deep understanding of these modules. Here, we will explain in detail the knowledge of the Android build module in different steps.

• Android onKey Operation Method
• Analysis of Android message passing application functions
• Android plotting application method summary
• Android Activity lifecycle Overview
• Summary of key Android development experiences

You can think of an Android application as a collection of different types of modules. Most of these modules are loosely integrated, so that you can accurately describe them as a consortium, rather than a single cohesive application.

Generally, most of these modules run in the same system process. It may or is very common to create multiple threads in this process. If you need it, it is also possible to create a complete independent sub-process. This is not very common, because Android has made great efforts to make the process transparent to your code.

Here is the most important part of the Android build module:

AndroidManifest. xml

This file is a control file that tells the system what to do in the top-level modules you have created. These modules include Activities, Services, Intent Receivers, and Content Providers. For example, this is actually a kind of adhesive that your Activity can receive that Intent.

Activities

Basically, Activity is a life-cycle object and a piece of code for some work. If necessary, this work can include the display UI to the user. Of course, if not necessary, the Activity may not display the UI. Typically, you can define an Activity in your application as the entry point of your application or application.

Views

A view is an object that knows how to draw it on the screen. The Android UI is composed of view trees. If you want to complete some custom image technologies, such as writing a game or building an unusual UI Widget, you need to create a view.

Intents

Intent is a simple message object that represents something to do or an Intent. For example, if your program wants to display a WEB page, it wants to browse the Intent of a URI by creating an Intent instance and processing it to the system. The system is used to locate other codes. In this case, it is a browser.) This code knows how to handle this Intent and run it. Intent can also be used to broadcast interesting events to the system, such as javasicaiton)

Services

Service is the code that can run in the background. It can run in its own process, or in the Context of another program process, which is determined as needed. Other modules are bound to a service through remote method calls. A Service example is a media player. Even if the user exits the media selection interface, it can still play its music, but when the interface is complete, is a Service to keep the music playing.

Notificaitons

A javasicaiton is a small icon that appears on the status bar to avoid confusion with Alarm. You can interact with this icon to obtain information. As we all know, javasicaiton is a text message. History and voice messaging, but applications can create their own icons. Notificaiton is the optimal mechanism to remind users to pay attention.

Content Providers

Content Provide is a data storage warehouse that provides access to data on devices. A typical example is that CP is used to access the user contact list. Your program can range the data exposed by other programs through CP. You can also define your own CP to expose your own data.

The above is the details of the Android build module.