Yahoo: The heavy tech behind the scenes
Yahoo, however, is also platform-neutral when it comes to mobile operating systems, and it’s very active in creating technologies specifically for the mobile web.
“On the desktop, you can get away with murder, but on mobile, it’s another story,” Fernandez-Ruiz told me. “You’re on a 3G network, an edge network, you get packet loss, you get disconnected for a while. It makes the experience on mobile phones and tablets much worse than on your PC at home.”
A big part of Yahoo’s solution is a toolkit it’s building around Node.js. This toolkit is collectively called Cocktails. The company first starting talking about Cocktails at the end of 2011 and open-sourced Mojito, the first of several Cocktails, earlier this month.
“Node.js is, in a way, like a browser that runs on the server,” said Fernandez-Ruiz. “The browser on the mobile phone isn’t that powerful, so Node.js becomes more important.”
Yet in spite of all this activity and advocacy around making the mobile web better, Yahoo has not joined the W3C group along with Facebook and Mozilla. Yahoo is a member of W3C, and Gil Yehuda, the company’s open source director, services as its representative on the Advisory Committee representative. However, Yahoo is not involved in any of the mobile-focused groups under W3C’s purview.
It’s worth noting that the W3C mobile web group was formed at a time of unprecedented tension between Yahoo and Facebook. In the middle of March, Yahoo filed a patent lawsuit against Facebook. In typical patent-law fashion, Facebook fired back with a patent suit of its own.
For now, one interesting and powerful voice is being left out of the conversation, but it’s not even the most deafening silence in this community group.
Google: The conflicted isolationist
Without question, the voice most missed in the W3C conversation is that of Google. One of the two most popular mobile-browser vendors in the world, Google owns and operates the Android mobile OS, which now has two separate mobile browsers: Chrome for Android and the native Android browser. (Of course, those two competing products will eventually be combined.)
One would think Google would be all over the W3C group, having so much at stake in the matter and being so frequently vocal about mobile openness and innovation.
“With Chrome for Android in particular, we thought about how we’d build a mobile browser from the ground-up, including thinking about how to make it run much, much faster taking advantage of hardware acceleration capabilities in Android,” an unnamed Google spokesperson told us via email.
It’s clear the company does indeed care about making its own version of the mobile web a best-in-class experience for both developers and users — and it’s in the company’s financial best interest to do so.
The spokesperson said the new Chrome on Android mobile browser, which just launched in February, brings a different approach to tabs and navigation that makes it simpler for a normal consumer to use. The rep continued, “We’re actively exploring how to take advantage of Android’s multi-layered security model now that we’ve built the world’s first multi-processor mobile browser. We are evaluating additional features like sandboxing for individual tabs within Chrome.”
It sounds like Chrome for Android is aiming to become the best-in-class kind of browser that Facebook et al. are attempting to regulate or mandate or at least define. So why is Google not coming to Facebook’s table?
Answering that question is simple and so very complicated at the same time. I’m not sure any two companies in Silicon Valley have developed as much enmity between them as have Google and Facebook.
It started when Facebook began nipping at Google’s heels in terms of ad revenue several years ago. Nowadays, Facebook is a legitimate contender for online ad dollars. Even though the social network’s ad take is still a fraction of Google’s, it poses a threat. Any competition is a threat when advertising makes up 96 percent of your revenue.
And based on that low-level inherent tug-of-war for revenue, Facebook and Google are more or less destined to dine at separate tables in perpetuity.
The other issue is that, in addition to running a mobile web browser, Google is also running a mobile operating system and has a certain amount of investment in keeping a somewhat walled garden of approved native applications that are distributed through a proprietary marketplace. While the company naturally claims no conflict of interest between the two aims, it doesn’t have the ability to achieve same level of agnosticism in the native-versus-web debate that’s ripping the mobile industry a new one.
When mobile titans compete, who wins?
The primary dictum of capitalism is that competition is good for everybody. But while that may or may not be true for some aspects of business, it’s much less certain whether competition is good when it comes to something as universal as the standards to which we, the technology industry, decide to build the mobile web.
In fact, Google, Yahoo, and Facebook seem to be the only three major parties that can’t come together on this issue. Verizon and AT&T are working together in the W3C mobile web group. HTC and Nokia and Samsung are all participating with one another. It’s not the carriers and it’s not the OEMs — it’s the software makers themselves that are holding back, embroiled in lawsuits and the cutthroat competition of a lifetime.
In my fantasy world, Google and Facebook and Mozilla and Yahoo and all the brilliant men and women who make those companies up would be able to sit down at the ultimate round table and hash out a mobile web that was good for everyone — great for developers, great for users, great for manufacturers. Everyone would win.
But in my fantasy world, there are no lawyers, no patent trolls, no limited streams of income, and definitely no online advertising. In the imperfect world, where lawyers and advertising rule the day, the round table is broken, and the deafening din of talk about the mobile web remains fraught with discord.
Image courtesy of Rafael Edwards
Mobile developer or publisher? VentureBeat is studying mobile marketing automation.
Fill out our 5-minute survey
, and we'll share the data with you.