Android Architecture and Development library that every Android developer should know

English Original: Android Architecture and Libraries every Android Developer should Know

Android's architecture encourages component reuse, allowing developers to publish data that shares activity, Service, and access to other applications, and can be managed based on security restrictions developed by the developer. That being said, today I will share some information about the Android architecture and Development library for developers to create the next killer app to use. You ready? Please continue reading below!

Don't be intimidated by the pictures above, you don't need to know everything.

Android architecture enables developers to create their own contact apps or Phone Dialer. You can publish your app's components, and let other developers create new user interfaces on this basis, for functional expansion or other work! How wonderful is this?

　　Anatomy of Android Architecture

The first list will show developers the app service, which is the cornerstone of Android's architecture. You can also call it a pillar framework for all Android applications, providing support for all development applications.

• Activity Manager: Controls the life cycle of the interface, including the management activity stack.
• Views: View builds the user interface for the application.
• Notification Manager: Provides a consistent, non-intrusive mechanism to notify users (for example: When you are playing a game when someone sends you a text message, the notification does not terminate your game, you will hear a sound prompt).
• Content Providers: Let developers share data between different applications.
• Resource Manager: Supports non-code resources such as strings and graphics being externally instantiated.

Now that you have an understanding of the first major part, we can look at the Android library, which will make it easier and more fun to develop Android apps. As you know, these are just short descriptions that you can learn more through the links I share!

　　What developers need to know about Android libraries

Android also offers a number of API development applications. So in this list, you will help developers understand which core APIs are available. All Android devices will provide at least these API support:

• Android.util: The core Toolkit contains the underlying classes, string formatting and XML parsing tools, and the underlying class??。
• Android.os: The operating System package provides access to basic operating system services such as messaging, interprocess communication, clock functionality, and debugging.
• android.graphics: The graphics API provides low-level graphics classes that support canvas, color, and draft entities and supports drawing the canvas.
• android.text: A text Processing tool for displaying and parsing text.
• android.database: Provides the underlying class support when the database handles cursors.
• android.content: Content API manages data access and provides services to manage resources, content providers (contents provider), and packages.
• Android.view: The view is the core user interface class. All user interface elements use a series of views to form the components of user interaction.
• * * android.widget**: Built into the View package, the Widget class is "Here is the user interface element we created earlier" and can be used in your own application. Includes lists, buttons, and layouts.
• com.google.android.maps: Advanced API that provides access to local map controls that can be used in your own applications. Includes Mapview controls, overlays for labeling and control of your embedded maps, and MapController classes.
• Android.app: A high-level package that allows access to the application model. The application package includes Activity the Service API and the like and is the basis for Android applications.
• Android.provider: For developers to access standard content providers (such as contact databases), provider packages provide classes to developers to access standard databases.
• android.telephony: Telephony API gives developers direct access to the bottom of the phone, and developers can call, answer, display call logs, call status, and short messages.
• Android.webkit: WebKit's software package features APIs that work with Web-based content, including a WebView control that embeds the browser and cookie Manager in your activity.

Again, what you've just seen is an Android library that can help you quickly build a simplified list of applications! In addition to the Android Api,android stack also includes a set of C/C++ libraries that can be published through the application framework. They include:

• OpenGL: Used to support OpenGL-based ES1.0 API, 3D graphics library.
• * * freetype**: This supports bitmap and vector font rendering.
• * * sgl**: A core library for providing a 2D graphics engine.
• IBC: standard C library, optimized for Linux-based embedded devices.
• SQLite: A lightweight relational database engine for storing application data.
• SSL: Supports secure Internet communication using Secure Sockets Layer encryption protocol.

　　Note: There's too much to introduce, and I'm going to end up here. Just one more part, you can do your own thing. If you can't read the entire post, you can bookmark it for future reference. Because, most of the content here won't change much!

　　Advanced Android Development Library

The core libraries we have seen so far provide all the features needed to develop Android applications. However, delving into the advanced API will use more advanced features and bring extra fun.

However, it is important to note that because Android wants to be more adaptable to mobile hardware, it is important to note that the following APIs are suitable for the occasion and whether the device is conditional upon use.

• android.location: The location-based service API that enables applications to access the device's current physical location. Location-based services provide common access to location information that is available on fixed hardware or technical devices in any location.
• Android.media: The media API provides support for playing audio and video media files, including streaming media and recording.
• Android.opengl: Android provides a powerful 3D rendering engine using the OpenGL ES API that you can use to create dynamic 3D user interface for your application.
• Android.hardware: If possible, the hardware API exposes the sensor hardware, including cameras, accelerometers, and compass sensors.
• android.bluetooth,android.net.wifi,android.telephony: Android also provides low-level access to hardware platforms, including Bluetooth, Wi-Fi, and telephony hardware.

Of course, you can also read more about the Android architecture and Development Library, you can click here to start.

Thanks for reading, if you like this article, please use the button below to share with your friends online! If you have any questions, please let me know. Feel free to ask me for advice and advice, and contact Facebook, Google and Twitter. Oh, please subscribe to other excellent articles.

Android Architecture and Development library that every Android developer should know