Seven aspects to describe the Android operating system

The following seven parts describe what is the Android operating system? Through its open-source, demanding Activity, device debugging, application will never exit, developer collaboration, Java-success is also Xiao He, Intents (purpose, intention) these seven aspects are learned.

The development of Android is indeed a thousand miles away, but many aspects are relatively immature to iPhone and Windows Mobile, and the market share is still far behind systems such as Symbian and iPhone. The road to future growth remains rugged. Android has also encountered many problems today. Operators and device manufacturers will fight independently, which is the biggest obstacle to the development of Android systems.

Only by keeping innovation and development at all times can we be invincible. Today, Windows Mobile is booming, but with Microsoft's penetration into the Internet field that Google is good. Therefore, in the near future, Windows Mobile will have a fight. Let's wait and see how the Android operating system goes further.

1. Open Source

Google open-source all the code on its mobile phone platform, but this does not mean that anyone can download and compile a new version of the Mobile Phone firmware, but it does mean that any mobile phone manufacturer can launch its own Android device. I am also looking forward to seeing the Android oven immediately.

But what's worse is that Google knows how to protect valuable Code. Its Map, Gmail, and Store applications are not open source. When you use these applications in your applications, you may encounter legal issues. This is just the beginning of complaints, because many people are planning to buy Android-driven devices, the more users, the more problems exposed.

2. demanding Activity

With Activity, Android forces developers to build applications in smaller blocks. For example, in their sample text editor code, they have an Activity to select from an editable file list. Another Activity is responsible for editing the file content. Android also encourages developers to use Intents to communicate with each other between their activities.

This kind of design is a good thing for mobile apps, but there is a nickname: No one works in this way. The concepts of centralized application objects (Blackberry/j2's Midlet or BREW's IApplet) are used by both the iPhone, Brew, and Blackberry ).

In contrast, Android forces you to design small, self-sufficient mimi applications, which leads to some very interesting behavior, such as, by default, when a user rotates the screen or releases a keyboard, Android ends the current Activity and recreates it.

Finally, professional mobile developers have only two options:

First, they use the Activity/Intent model on other platforms to design their software so that it can be easily migrated to Android;

Second, hacker behavior is implemented to change the Android operating system behavior to that of other platforms.

3. device debugging

Two years ago, debugging on mobile devices was very difficult. At that time, I had to write a j2_log system by myself to track and monitor the sound and logs. Google now provides better tools to help us. It is simple enough to simply press F11. It is not only easy to use, but also cross-platform and supported on Mac, PC, and Linux.

Why do I hate this excellent tool? I hate it because it makes 40% of my debugging skills almost useless. Next, you will know that Google will allow anyone to design the UI of mobile apps without anything else, only XML.

4. Applications will never exit

Once an application is started on Android, it will never exit. The application can be temporarily returned to the background, but the icon will always be in the list of running tasks, this problem caused by the core architecture has brought about some interesting software bugs that require some fancy application design methods to be avoided.

5. developer collaboration

In Android, memory, processor, and battery resources are public resources. Unfortunately, any application, even a backend application, can use these resources in an unlimited amount, this is why the performance and battery life of Android phones are so unstable.

Google wants developers to use the front-end and back-end loops wisely, but if a developer is not careful, the battery that could have been supported for less than an hour may be exhausted, collaboration between developers has never become so tight as it is now.

6. Java-Success and Failure

I have to admit that the Java language is indeed very powerful. There are two reasons for listing it here: first, it is too big, and second, it is difficult to optimize. As a programmer, it makes me feel like a long procedure, although it can speed up product marketing.

This can free us from memory leaks and stack damages, but it is almost impossible to write an anti-sawtooth library and render it within a reasonable time, although developers can use their NDK to develop custom libraries in C, We Have To debug both languages at the same time.

7. Intents (purpose and intent)

This is the third serious syntax nightmare of a developer. An Intent in Android is used for communication between two Activities, services, or content providers. Intent is a term, but it is also often used as an adjective, but it should not be used as a plural number at any time (for all Intent and purpose cannot be counted). In the past two years, it is difficult for me to interact with each other when I use copy editing. Every time I use Intent, I feel like a grammar teacher in elementary school. Whenever I abuse a comma, she will patiently correct it.