Android big face...

On Valentine's Day in February 14, Google published a new version of Android on its official Android blog.
SDK publishing message (according to the date on the website, the SDK should have been updated in December February 12. It seems that Google's public relations are indeed not very hardworking ...). The SDK version is
M5, in theory, this should be the last version before the first round of the preliminary round. Before that, we will better adapt to the new SDK for everyone, google postponed the end date of the first round of the preliminary round by nearly half.
Month, which means that this version of the SDK will be greatly changed. But when I couldn't wait to start a new simulator, I was so scared that I could only read three words in my heart and make a big face.
Institute
The "big face" has two aspects. One is to use a brand new style interface. You can see a few distinctive interface diagrams. Even those who have been working on Android may
It seems that the earlier Android interface is still quite regular, and the style is quite "traditional". There are many similar interfaces and operation methods with operating systems such as Symbian. This time
Actually made some special features.

Figure 1: new initial interface	Figure 2: new contacts and pop-up menus	Figure 3: new notification system	Figure 4: New Expanded menu

Set
With the classical line of the Olympic spirit, the new Android interface is bigger, more Q, more fancy. Bigger is the most obvious. The icons and fonts used now are at least twice as big as the old ones.
More than half of the displayed content is missing, but it is extremely clear and dazzling. My personal analysis is closely related to Android positioning. Android positioning is based on a mobile phone platform with a certain hardware base.
Support for low-configuration mobile phones. There is no doubt that a certain hardware base includes a large enough screen, especially the increasingly popular large touch screen. The larger icons and text enable users to fully enjoy the better visual effects brought by the large screen.
You can also perform touch operations more conveniently.
Of course, this new interface is not the same concept as the revolutionary UI of the iPhone. Some cool UI features of the iPhone (dual-touch,
Automatically turn off the touch screen and so on...) are dependent on XX sensors and other hardware infrastructure. After all, Android is an open software system, which requires a high hardware base and cannot be as high as that of the iPhone.
. However, in the new SDK, we can see that android is compatible with different hardware in another way. Added touch in Activity
Mode Interface, used to provide better user experience (mainly focus on...) with touch screen conditions ...). I think there will be more and more APIs available based on different hardware conditions.
The sample API must be simple and easy to use. Otherwise, it will increase the burden on developers.
In addition, it is interesting that Google uses a Q style in Android. The icons are all cute arc angles, and the font is also round. This is probably a good example for Android development engineers. This can be seen from earlier Google videos.
Q comes along with a more fancy interface style. Big icons are everywhere and the colors are quite gorgeous, what's more interesting is that the animation effect of viewgroup is more exaggerated and useful than the original one.
Of course, all these changes in the interface style are not passive. To better support new interfaces, all view parsing methods have changed, and the android
Cursoradapter, notification, viewgroup, menu, and other classes have all made many changes,
Simplecursoradapter can directly support the display of images, so that more people do not duplicate the wheel. notifaction is changed to figure 3, with icons and more abundant
Rich Content; viewgroup supports better animation display, which can be seen in the demo; menu is greatly changed (2, figure 4), and the menu with icons can be quite comfortable
Easy to handle.
Of course, this is not just a teaser. In order to better display icons, animations, and so on, view introduces the drawing cache (in fact, it is a dual buffer policy ...) new mechanisms, such as latency and late binding, improve loading efficiency.
Changes in the New Territories also require some changes in user usage. The new start interface, as shown in 1, adopts the sidebar mode. Top icons (such as apidemos,
Is dynamically updated based on your last usage. Although it is cool, I personally think it is quite messy. The new notification is no longer displayed through the up/down key,
The drop-down is needed. Although it is still cool, it is still not easy to use. The new menu is separated and divided into Icon menu, expanded menu and context
Menu. The most common menu is in the icon mode. If there are more than six menus, you can use the more button to convert them into the expanded mode, while the context
You need to press the center button for 2 seconds to bring up the menu. Everything is against the normal operation method. It is cool, but it takes time to test.

Another huge change in the new SDK is the massive API changes. This change is painful for old projects to be transplanted, but it is definitely a good thing in the long run.
The most significant change in the API is the change in naming, and many unreasonable names are changed. Some unclear APIs are more specific. For example, some SQLite-related APIs are attached
SQLite prefix. Some methods that have been marked as expired in the document have been permanently abolished this time, such as the query method of contentprovider.
Adjustments were made. For example, the position and index in listview were unified into the position, which solved the problem that I had a headache. Some naming styles were unified.
1. For example, the URI adopts a uniform Uri and the ID adopts a uniform ID. In other aspects, some items in androidmanifest. XML are also unified, which can be easily handled.
. In short, there are still many such changes, and a large number of APIs are clearer and easier to understand. This is also the result of Google testing by all programmers who are tempted by the world.
Some classes are restructured to separate and Expand functions. The most typical is contenturi, which is split into the contenturis function class and the URI entity class.
The use of Members provides better guidance. Another typical change is cursor, which adds an extras interface to transmit additional data, this is a timely mess of rain,
This makes it easy to do a lot of things. Another one is that the notification is split, and the notification only refers to the icon on the top of the home page.
The output text or view is separated into toasts, which makes it possible to develop separately.
A special change is alerts, which adopts the new builder chain construction method instead of the constructor construction method. The constructor structure is more flexible. In contrast, notification has a longer constructor, which is difficult to use. In my opinion, this is not a good change.
This
Android also adds some practical classes. The newly added expandablelistview is a level-2 tree adapterlistview, which is a very non-
Commonly used View Controls. I think this is the result of a large number of developers. I personally wanted to customize this wheel, and then implemented it in the first-level simulated second-level mode. This is good and easy to understand. Another
The revolutionary thing is search.
Manager interface, which is a hooker interface. Android provides a cool search interface and interface for your activity (see sample ),
By implementing hooker, you can achieve unified search, which has a great impact on many people who do the same search as me. In the short term, porting is very painful. In the long term, it is quite
The changes in Google flavor have greatly promoted search. Another change that compares Google's taste is to rename xxmp to Gtalk, and Google's ambition is exhausted.

In addition to these face changes, the SDK has greatly changed the plug-in. It supports multiple devices and merges the device view and process view. It also adds a new traceview tool, this is a visualized log analysis tool that makes the android log system more powerful and the debugging time is expected to be further reduced.

All these observations are based on my observations over the past two days. They are just blind people. For more information, see here, here. Unfortunately, most of the SDK documentation is not keeping up with you. If you want to learn more, I hope you can directly read the SDK sample instead of reading the examples in the document.
After these changes, Android is becoming more and more perfect, and Google's investment in the Grand Prix does not seem to be white. This is also a better opportunity for all Android users. Whoever can adapt to the new SDK can take a better place.