As mentioned in this post, Android has split into two camps, the Open Handset Alliance version, which includes Google services baked right in, and the version for the Android Open Source Project (AOSP).
The other side is the Android Open Source Project (AOSP), a far-freer version that lets device makers tinker with all manner of elements of the software. Often that means ripping out Google services, and customizing the handset to run other software and services. Google apps are still accessible, but are not central to the experience as they are in OHA Android devices.
Samsung’s Tizen is based on their own customized version of Linux and is designed to work with their Galaxy Gear line of watches. Samsung has just inked a deal with Nokia (note that this is Nokia and not Microsoft — h/t to Janne Ojaniemi) to use Nokia’s HERE maps for turn-by-turn and offline directions. Just as Apple has reduced dependence on Google by rolling their own maps, Samsung has done the same by rolling their own OS and allying with Nokia for mapping.
Whether this alliance was forged by strategy or necessity (would Google have to cooperate to get Google Maps ported to Tizen?), this is sure to splinter Android further still.
If Apple does roll out the iWatch on September 9th, it will be interesting to see how the iWatch OS interacts with iOS and whether mapping is part of the picture.
there is no reason to believe that Google’s efforts to unify Android are going to have long term success. My guess is that splintering like this will occur as handset makers search for ways to increase their profit share.
We’re constantly reminded of the desktop market share issue. In mobile, the pressure to profit will be more forceful than at any time during the low margin pc wars. These are different players with different goals than their desktop counterparts.
Correction: Tizen is NOT a customized version of AOSP. Tizen, like AOSP, is based on Linux. Tizen has an Application Compatibility Layer (ACL) for running Android apps (so long as they don’t depend on Google Play Services APIs that have not been cloned by Tizen). This is a very important detail because it is how Samsung is able to free itself from the contractual chains with Google while still producing a device that can run Android apps.
If Tizen was based on AOSP then Samsung would be breaking the contractual agreement as a member of the Open Handset Alliance (OHA). The OHA is ironically named “Open” but actually forces members to ship the OHA-version of Android that Google provides in order to gain access to Google services and apps. Google says they do this in the name of “compatibility”, but it is their legal means of preventing every manufacturer from doing what Amazon has done. Members of the OHA (including Samsung) cannot simultaneously ship handsets running AOSP and OHA versions of Android. If they ship AOSP-based variants they are restricted from further use of the OHA version. In 2012, Google blocked Acer from shipping a new AOSP smartphone just before launch by threatening to pull Acer’s OHA membership (see http://www.computerworld.com/article/2492550/data-center/google-blocked-acer-smartphone-on-android-incompatibility-concerns.html).
However, the OHA membership does nothing to prevent a manufacturer from shipping phones based on other operating systems such as Windows Phone, MeeGo, Palm-OS, and even Tizen.
Pity the fool who ends up with a Tizen phone.
I just don’t think Maps on the small screen like Watch will be a good idea.