About whether Microsoft should do the branch version of Android devices

For a long time, the discussion of whether Microsoft should do the branch version of Android devices has never stopped. Many of the smart-savvy analysts believe that Microsoft apps can grow and split Android by leveraging the ecological integrity of Android's application.

In fact, no one can really separate android. If Microsoft really chooses the path of Android's mobile smartphone, that would be an irreparable mistake.

Speaking of which, I believe many friends will think that these words are sensational, do not worry, please continue to look down.

First, Android's core has become increasingly closed. The Android system is fundamentally composed of two parts. The first part is open source Aosp (Android Open source project). This resource is part of the Google Developer Alliance, which provides Android infrastructure code based on the Linux kernel and Dalvik virtual machines. In this framework, although Google also encapsulates some of the applications and APIs, but most of these applications and APIs are no longer updated. When docking with the latest applications provided by developers, it is often impossible to implement or bug out.

The second part is Google Mobile apps (GMS), or Google services, Google Store services, and so on. This part is called the "living soul" of the Android system. This includes all kinds of Google Apps, as well as some of the most important and timely APIs for developers.

Unlike at home, one of the most important reasons Westerners choose Android devices is that they can use Google's various "native apps". Because services such as Gmail have been deeply rooted, even affecting their work and life. It is hard to imagine how Android, without Google's services, can be accepted by Westerners. In China, on the contrary, Android, which has been castrated of Google's services, is mistaken for the face of Android apps. In this way, a variety of shoddy services, is full of our "Cottage Android".

The key problem is that GMs, as the core of Android, has become increasingly closed. First, AOSP's phone can get the basics of the Android framework, but not its soul. Second, Google no longer provides API updates for AOSP users. It is reported that many AOSP mobile phone API still stay in the Android 1.0 era. How important is the API? APIs that are not upgraded in a timely manner may cause many applications to be unusable after an update, or a variety of bugs.

Second, all roads lead to Android, but no one fits Microsoft. Some time ago, the news that Nokia has developed or is developing a mobile phone based on the Android affiliate system has aroused widespread debate. Many analysts think it is a clever way for Microsoft to borrow chicken eggs. But this is not really suitable for Microsoft, but the wishful thinking of good people. To figure this out, we need to analyze what kind of hardware vendors are doing with Android devices.

The first: Listen to Google, and rely on AOSP and GMS.

This is Google's most willing to see the direction of development, prominent representatives are Samsung, HTC, LG and so on. These manufacturers, as members of the AOSP, have obtained Google's special certification. On the one hand, Samsung and other manufacturers can use Open-source Android code, on the other hand, they as Google "reliable" ally, enjoy Google's rich proprietary services and timely updating of the API. Companies that do this can benefit largely from Android's vibrant ecosystem of applications.

Not only that, these obedient "boys" will also gain some freedom, such as adding customized skin or their own application. Of course, these people simply do not have the ability to split Android. Once they accidentally cross the line, Google restricts it. Before the Hunt Cloud Network editor June has reported, Samsung because in a few years CES launched the "magazine" interactive style, and was summoned by Google. Although Samsung said it would maintain its innovation independence, it agreed with Google on the issue of "maintaining a more unified Android style".

Second: Completely castration Google service, only as a aosp version of the andoid.

The market to take this road is represented by China. These countries or regions for this or that reason, thoroughly proposed Google services, only the use of Open-source Android framework code, to create a localized color system platform. Use one word-"silly love"-to describe these users as the most appropriate. Still, these Android phones can be downloaded to the latest apps through pirated app stores. Of course, they will also play a "self-developed" banner, the introduction of a variety of shoddy applications to meet the needs of users. Since most users in these markets are unable to use Google's native apps, they are not aware of the real Android. More tragically, because of the habit of using garbage, users in these places have greater latitude than Western users. In addition, for the inability to obtain (or timely access to) the official API upgrade, many Shanzhai Android machine is basically "timely occasion" of the product, only after a period of time, basically equal to the function machine.

Third: Between the first two, the use of AOSP, the introduction of their own GMS.

This approach is most aptly represented as Amazon's Kindle series. Amazon uses the Android infrastructure to "play the Ring" with Google's native service on the basis of Android apps--with a wide variety of proprietary apps like Google's services (or apps using companies like Microsoft). In addition, when Google upgrades the API, Amazon will also upgrade the API. (The updated Android application cannot be used without an upgrade). Although this "catch-up" path has cost Amazon a great deal of time and manpower, the effect is often not always good.

Fourth: Using AOSP code, another portal, to create a new operating system.

Represents the Ubuntu (Android version). Handset makers such as Ubuntu, using open source Android code, have developed a number of apps that Android phones do not have, and have a brain that overrides Android with its existing system. Although its API is similar to Android at the bottom, it does adopt a new docking style. In other words, this kind of dash wants to merge Android, build its own new system, and eventually split Android.

With the first approach, it's basically a choice to give up splitting Android. Because in the strict certification terms, Samsung and other OEM manufacturers Street. Samsung can basically be said to be stuck, and by exploiting Tinzen to challenge Android, it's a bit of a dig to the grave. This is the way Microsoft will not go anyway. As a software and services giant, allowing Aosp+gms to exist is tantamount to becoming a pure hardware manufacturer of Google Android.

Similarly, Microsoft does not seem to need to adopt a second approach. Most mobile phone manufacturers based on AOSP code are limited by the local market, which makes it difficult to grow into international handset makers. These phones will support some Android apps, but the number and duration are uncertain. Because of the lack of official APIs, these mobile users often miss out on some very good apps (and, of course, the power of piracy is quite strong in China). WP's current application of the ecological environment is relatively scarce, why still have to open up an uncertain future, difficult road?

Amazon has huge financial and material resources. But catching up with Android has put it in a mood. Analysts believe that if Microsoft is also higher than an Android branch system, the introduction of a rival to the GMs application, and continue to follow the API, its cost can be almost re-built WP. Moreover, Microsoft has always been the ideal of its existing software advantages to move the platform to shift, the aforementioned "thankless" approach is not very sensible.

The fourth approach is not appropriate for Microsoft. WP has its own proprietary system kernel architecture, he does not need to use AOSP code. Moreover, Microsoft's existing WP development strategy is to create a different platform than Android, why do you have to like Ubuntu as a self-reduction of identity?

The production of the branch version of Android devices for Microsoft, how to see how unreliable. Instead of thinking about how to split Android, learn Android. Refine, the integration of their own innovation is enough. This, Apple's iOS 7 quite a bit of experience!