Android may still be growing its share steadily, but Google has an increasingly tough battle to maintain that momentum and ensure the experience is centered on its services and revenues. It is more and more isolated in its own world as its remaining applications ties to Apple get cut; former allies like Facebook, which previously depended on its Android developments, assert their independence; and significant OEMs like Samsung take an interest in the new breed of browser-oriented operating systems, which could eat into Android’s power in the future.
Facebook is the latest challenger to Google’s control of the Android user experience, as the social networking giant, which abandoned an HTML5-based strategy last year, finally finds its mobile feet. Like Amazon, Baidu and various carriers before it, it has created an overlay for Google’s OS which puts its own services at the heart of the platform, sidelining Google’s own. Indeed, CEO Mark Zuckerberg highlighted the search leader’s dilemma when he launched the new Facebook Home product last week, saying: “Google’s Android is open, so we don’t have to work with them,”
Facebook Home sees the web giant stopping short of launching much rumored own-branded handsets and, instead, creating a more sophisticated mobile experience which will eventually run on any Android smartphone ‘ though initially it is available for key HTC and Samsung devices.
‘You can see how Home takes over the phone, and you see more and more of what Facebook wants you to see and less and less of what Google wants you to see,” Ben Bajarin, an analyst at Creative Strategies, said.
HTC, along with Sony and some operators, has worked before on ‘Facebook phones’ which put the social service at the center of the homescreen, and some operators are even starting to offer special contracts which include dedicated Facebook units. However, Home goes further than these efforts, or Facebook’s current mobile app, and gives the company greater influence over the platform, without having to invest in its own operating system or hardware brand. Last year, struggling to create a viable mobile business model, the company abandoned a major push to create an HTML5 platform and developer base, saying this technology ‘ which has the advantage of spanning different OSs and bypassing policed app stores ‘ was not ready yet.
Home provides an overlay for Android. It is downloaded free from the Google Play store and replaces the usual homescreen with Facebook’s own ‘Cover Feed’, centering on updates from friends. The usual homescreen, lock screen and wallpaper are all replaced. Other key functions include ‘chat heads’, which tie other mobile apps and messaging platforms into the Facebook service, making it the hub for all a user’s communications activity ‘ and in the process, making Google’s voice, messaging and other key functions almost invisible. Google has been trying to improve its competitive position in the important social networking space since the launch of Google+.
Initially the software is available for the HTC One X and One X+, and the Samsung Galaxy S3 and Note II. It will also work on the forthcoming HTC One and Galaxy S4, and on more devices in the coming months. Home can also be pre-installed on phones through the Facebook Home Program, an initiative which is being supported initially by HTC and AT&T, The former will deliver the HTC First on April 12.
Facebook has further enhanced its mobile activities by acquiring start-up Osmeta. The Silicon Valley team is likely to be attractive mainly for its talent rather than its products, which are pre-commercial and remain shadowy. The firm’s web site touts its skills more than concrete offerings, saying modestly: “We have the most formidable programming talent density imaginable under a start-up’s roof, or any other roof for that matter …The breadth and depth of computer science knowledge contained within the brains of our team is remarkable. Most of us have had illustrious careers at places such as Google, IBM Research, Yahoo Research, and VMware.”
Google will also be keeping a close eye on new mobile OSs, though it has its own HTML5-oriented offering in Chrome OS. One of the most potentially dangerous is Mozilla’s Firefox Mobile, which has attracted considerable operator support, especially for bringing the mobile web experience to emerging markets. Another contender is Tizen, which combines the former Intel/Nokia platform, MeeGo, with another carrier-backed Linux variant, LiMo. Tizen’s main claim to the big time rests on the support of Samsung, which is merging it with its own Linux OS, bada, as well as backing from Intel.
However, Samsung famously keeps its platform options open to maximize its presence, and its latest interesting software move is to collaborate with Firefox. Although it has said it will not support Firefox Mobile, it is working with the open source organization to bring a new browser engine called Servo to ARM/Android devices. Servo aims to address many of the remaining limitations on the mobile browsing experience, including in security, by rebuilding the browser from the ground up, and specifically for ARM-based device hardware.
Servo is written in Rust, a new, safe systems language developed by Mozilla and its supporters. With the Samsung collaboration, Mozilla will bring Rust and the experimental browser engine, Servo, to Android. The Korean giant has contributed an ARM back end to Rust and the build infrastructure necessary to cross-compile to Android, along with other improvements. Rust has been in development for several years and aims to support strong security and precise control over hardware resources. It claims to be “safe by default”, preventing entire classes of memory management errors that lead to crashes and vulnerabilities. It also makes it easier for programmers to harness the power of multicore ARM architectures. In the coming year, Mozilla is aiming to complete the first major revision of Rust.
The Servo product may be far from commercial reality as yet, but it shows how hardware-driven Samsung is becoming a major mover in software, providing a challenge to Google as well as being Android’s biggest revenue generator. It also highlights the critical importance of influencing the next generation mobile browser, the foundation of the web experience as streaming and cloud services start to take over from downloads.
Ericsson, Microsoft and others have shown off experimental mobile HTML5 browsers, but this is another furrow Google is going to have to plow alone. This week it emerged that the search giant had ended a long marriage of convenience that linked its browser technologies to those of Apple, once its close collaborator, now hellbent on excising Google software from the iOS experience (though making that move with Maps proved premature and exposed Apple’s own vulnerabilities in molding the new mobile software platform).
The latest tie to be severed between the former friends sees Google creating its own fork in the WebKit browser engine project. While Google has used the standard WebKit code base for Chrome, and worked heavily with Apple to contribute to that open standard, it will now evolve a separate offshoot called Blink. That will mark the end of years of direct WebKit programming cooperation between the two rivals and allow both Chrome and Apple Safari to take separate, and differentiated, directions.
The challenges ‘ and potential developer backlash ‘ of creating a major fork will be worthwhile, says Google’s VP of engineering for Chrome, Linus Upson. “We’re confident this will allow us to move faster and allow the rest of the WebKit community to move faster, which ultimately will allow the web to move faster,” he said. According to CNet, many Google Chrome executives believe their platform is already diverging and will be more innovative when separated from Apple and mainstream WebKit. For instance, Chromium (the open source basis of Chrome) has a very different multiprocessing architecture from other WebKit browsers. Google wants to make some changes, such as assigning iFrames to their own computing processes, which could be very divisive if it tried to impose them on the whole WebKit project.
Google will have to convince developers to support its variant, but in practice, WebKit has been fragmenting as more companies have become involved, and as it becomes more critical to web and mobile strategy. Opera recently scrapped its own Presto engine and adopted WebKit, and Google has been converging its Android and Chrome browsers. Apple is also ‘upstreaming’ elements of its iOS browser into WebKit rather than keeping it separate, which has also caused some tensions in the Google collaboration. Chrome programmers have sometimes objected to what one, Adam Barth, called ‘a growing trend of unilateral action by Apple in this project’.
Such tensions and politics are inevitable in open source and standards processes, but these comments highlight a more important element ‘ Google’s need to control its software destiny as it gambles on being able to keep its Android (and Chrome) user experiences dominant. This is essential to ensure its operating systems drive usage and revenue of its search engine and applications. It can no longer rely on partners like Samsung and Facebook to create that business for it, and so must seek to make its own implementations pre-eminent by investing heavily in ensuring their differentiation, and superiority to the emerging alternatives, whether within the Android community or beyond it.