Group items tagged

Awareness of the problem is growing, from Google's catastrophic launch of its social network Buzz in 2010, which shared users' contacts without their permission, to the revelation last year that Facebook was still tracking users' browsing information after they had logged out.

The new possibilities for surveillance undermine the fundamental privacy of the act of reading.

LG has indicated that it will be using webOS in its Smart TV line (which, in passing, suggests that Google's hopes of having a multi-manufacturer-pronged assault on the living room with Google TV are being chipped away; Samsung has gone its own way, Sony offers a mixture of Google and its own smart TV offerings, and now it looks like LG isn't exactly all-in). Though that might, in time, become something that it uses on phones or tablets, you'd be crazy to bet on it. LG is smart enough to know that TVs are a world away from phones and tablets, both in terms of the user interaction experience, and the demands that they make for user acceptance.

But the siren song of open source OSs becomes deafening when you look at the other announcement to come out of Mobile World Congress, in which Mozilla is touting its Firefox OS as the anathema to the world's ills - or at least those afflicting the smartphone industry. What does Moziila chief executive Gary Kovacs think is going to be the unique selling point of the Firefox OS phones that he expects to see in 2014? "Our goal is to level the playing field and usher in an explosion of content and services that will meet the diverse needs of the next two billion people online," he said in Barcelona, adding "We're not trying to get in the middle of an operating system fight; what we are trying to do is be the catalyst to drive more development around the open web."

The problem for Firefox OS is that it doesn't have a dedicated hardware backer. Sure, Sony has said that it will make some phones using it. ZTE and Alcatel say they will build hardware that will run it. And Kovacs points to the fact that Firefox OS will run HTML5 apps - not "native" apps (in the sense that iOS or Android apps run natively). That might put a questionmark over whether, by some analysts' measure, the FFOS phone is truly a "smartphone", since their definition for that includes "running apps on a native API". (That's why Gartner and IDC don't class Nokia's Asha phones as smartphones.)

So how did Android succeed? Three things. First, Google get a vibrant app ecosystem going even before there was a single phone: it had competitions for apps, with a $10m fund to seed developer ideas. By April 2008 there were almost 2,000 Android applications; two-third came from outside the US. Among the offerings: photo-enhanced driving, on-the-fly party mashups with maps, maintaining passive surveillance on your family's whereabouts. (Some things never change.) Second, it was able to go to Verizon, which was looking enviously at how AT&T was able to offer the iPhone, and suggest that Android phones - when they came along - could be the answer to that competitive challenge. And third, it was Google - the gigantic search-engine-and-everything-else company with the international reputation. If Google was doing a new generation of smartphone software (and if Apple had validated the idea), then it looked like a good deal for everyone. And handset manufacturers were eager to find an alternative to Microsoft.

Android is gigantic - some version of it might be on a billion phones this year - meaning there's no obvious need for another open source OS. What, after all, is FFOS actually going to do that Android doesn't, or that iOS or Windows Phone or BlackBerry can't? Yes, we've heard that the target isn't the west, but the developing world; that still doesn't explain why a Chinese handset manufacturer would deploy FFOS rather than Android, whether the Google version or a forked one that could connect to a local app store.

Even worse, FFOS is at an immediate competitive disadvantage because the principal browser on smartphones now is based on WebKit. Chrome uses it, MobileSafari uses it, BlackBerry uses it, and Opera uses it too now. That leaves only Internet Explorer on Windows Phone standing alone. Developers writing HTML5 apps will naturally write for compatibility with WebKit, which is always going to behave slightly differently from Firefox's Gecko rendering engine. For FFOS's sake, you have to hope the differences aren't big.

That's the trouble with the magical thinking that often attaches to open source projects. Making webOS open source didn't solve its problems; it simply shoved them off into a siding. Having an open source mobile OS didn't guarantee Android's success; the efforts of Google, and the timing in the market, did that.

Perhaps for that reason, people have high expectations for the Ubuntu OS and phone, with its fabulously complex array of gestures for control. Bad news, dreamers: it's going to fail in the market too if Canonical attempts to market it as a hardware-software combination - that is, sells Ubuntu phones at retail.