Tag Archives: mobile

Google’s strategy unveiled: a little bit of everything you do

Google CEO Eric Schmidt gave a keynote address at the Mobile World Congress yesterday, which is worth watching if you have an interest in the future of technology or, well, human life.

image

The talk was an informative and open insight into Google’s future direction. It was centred on mobile; but since Google now regards the mobile phone as the primary device for how we interact with the world, that was no limitation. Google is putting mobile first, said Schmidt, because it is the meeting point for the three things that matter: computing, connectivity and the cloud. He believes that phones will replace credit cards, for example, as they are smarter and more secure for financial transactions.

Google’s strategy is to combine the near-unlimited power of server-side computing with its database of human behaviour, to create devices that are “like magic. All of a sudden there are things you can do that were not previously possible.”

He gave an illuminating example: Google voice search. You speak into your phone, and Google transcribes your voice and performs a search. Voice recognition is nothing new, but the difference in the Google demo is that it works. Here’s how. The problem with voice recognition is that one word sounds very like another, especially since we do not speak with precision and every voice varies. Computers cannot understand exactly what we say, but they can use dictionaries to come up with a set of possibilities for what we said, one of which is likely to be correct.

image

The next step is the brilliant one. Google takes this set of possible phrases and compares it to recent Google searches. If one of them matches a popular search, then it is likely to be what you said. Bingo. Google now does this in four languages, with German demonstrated for the first time yesterday.

It works on the assumption that humans are not very original. We tend to do similar things, and to be interested in similar things. Therefore, as Schmidt noted, if you are a tourist walking around a city with your location-aware phone, Google does not only know where you are; it also has a good idea of where you will go next.

Another cool demo is for image recognition. We saw this in two guises. In one, you hold up your phone and do an image search using the camera as input. Result: information about the building you are looking at. [Or maybe the person? Hmm.]

In another demo, you point the camera at your foreign-language menu as you ponder which incomprehensible dish might be one you could eat. Back comes the translation in your own language.

Note that these demonstrations are not really about super-powerful phones, but rather about the other two factors mentioned above, the power of cloud computing combined with a vast database of knowledge.

Schmidt’s blind spot is that he does not really see privacy as an issue. He mentions it from time to time; but he is clear that he regards the trade-off, that we give our personal data to Google in return for these cool services, as worth it. I posted a remarkable quote yesterday. Here’s another one, from late on in the address:

Google will know more about the customer because it benefits the customer if we know more about them.

What Schmidt fails to do is to extrapolate the implications for stuff other than cool services. One is what happens if that huge database is used dishonourably. Another is the huge competitive advantage it gives to Google versus everyone else; Google has this data, but rest of us do not. A third is how that data could be used in ways that disadvantage us. An example is in insurance. Insurance is about pooling risk. The more data insurance companies have about you, the more accurately they can assess the risk, which means a wider range of premiums. If by some mechanism insurance companies are able to analyse Google’s data to assess risk, they can refuse to insure, or charge high penalties, for the higher risks. We won’t necessarily enjoy that, because it means more us may find it impossible to get the insurance we want at a price we can afford.

Google’s business strategy

That’s the technical side. What are Google’s business plans? Schmidt made some interesting comments here as well, many of them in the question and answer session.

Google does not plan to become a mobile operator. Schmidt received some fairly hostile questions on this topic. Since Google positions operators as dumb pipes, stealing their talk minutes and insisting on an open web for services, who will invest in infrastructure? Schmidt denies positioning operators as dumb pipes, but does not leave them room for much other than infrastructure; he says they might have a role in financial transactions.

How do we (both Google and the rest of us) make money? Two main areas, according to Schmidt. One is advertising. He says that online advertising spend is currently one tenth of the total, and that this proportion must grow since “consumers are moving from offline to online.” In addition, mobile advertising will be huge since you can target location as well as using other data to personalise ads. “The local opportunity is much larger, and largely unexplored,” he says.

The other big opportunity is apps. The number of apps that need to be installed locally is constantly diminishing, he says, leaving great potential for new cloud-based applications and services.

As for Google, Schmidt says it wants to be part of everything you do:

We want to have a little bit of Google in every transaction on the internet

Thought-provoking stuff, and a force that will be hard to resist.

So who can compete with Google? Making equally capable phones is easy; building an equally good database of human intentions not so much, particularly since it is self-perpetuating: the more we all use Google, the better it gets.

No wonder Microsoft is piling money into Bing, with limited success so far. No wonder Apple’s Steve Jobs is concerned:

On Google: We did not enter the search business, Jobs said. They entered the phone business. Make no mistake, they want to kill the iPhone. We won’t let them, he says. Someone else asks something on a different topic, but there’s no getting Jobs off this rant. I want to go back to that other question first and say one more thing, he says. This don’t be evil mantra: "It’s bullshit." Audience roars.

Eric Schmidt: we can literally know everything

I am watching Google CEO Eric Schmidt’s keynote at the Mobile World Congress today. I am only 10 minutes in, but I was struck by these comments, as he talks about improving connectivity across the internet:

Think of it as an opportunity to instrument the world. These networks are now so pervasive that we can literally know everything if we want to. What people are doing, what people care about, information that’s monitored, we can literally know it if we want to, [pauses, lowers voice] and if people want us to know it.

A comment full of resonance. Who is “we”? You and I? or Google? The enthusiasm for knowing everything about everything, the reluctant-sounding concession to privacy at the end. The sheer bravado of it; the word “literally”, which means in actual fact, without hyperbole; and yet which is obvious hyperbole.

For another view on this, see The Onion’s piece on Google’s opt-out village.

Flash developers are now mobile developers

Adobe’s announcement of AIR for mobile today at the Mobile World Congress means that any Flash or Flex developer can compile an AIR application that will run on a supported mobile device. I understand that AIR for mobile is a subset of desktop AIR, but does include Flash Player 10.1, local database support with SQLite, and access to local storage, so it is not lacking in capability. Apparently it will be possible to have a single .air file that will run across desktop and devices, perhaps with conditional code to account for differences in device capability. Some features, such as multitouch and accelerometer support, are more likely to be found on a mobile device than on a desktop, though things like screen size and available storage will be more constrained.

Until now it has been Java that comes closest to providing a common runtime across desktop and devices. Flash promises a more consistent runtime as well as stronger multimedia and graphics capability. Thanks to Apple, the app store concept is now well established and AIR applications fit well with this model, though not exclusively so. It will also be possible to deploy AIR applications from your own web site. I think there will be considerable interest and take-up for AIR on mobile.

Initial support will be for Google’s Android OS, with others to follow – with the exception so far being Apple.

This is where it gets interesting. Whereas Flash in the browser is blocked on Apple iPhone and (as far as we know so far) iPad, Adobe has a native compilation option for Flash applications targeting these devices, preserving some kind of deployment story. Clearly from Adobe’s perspective it would be better and easier if Apple allowed the AIR runtime onto the device. It’s less clear that Apple device users are really losing out though, and there is even an argument that they benefit, if you think that native code is a better solution for a mobile device.

In other words, the introduction of AIR for mobile does not really put any pressure on Apple, since Adobe has already come up with a good alternative. There may be some indirect pressure, since growing use of the Flash runtime outside the browser may also increase its significance within the browser.

A lot hinges on the quality of the mobile AIR runtime, particularly in respect of memory usage, which has tended to be greedy in desktop AIR.

Going Mobile

In the back of my mind I knew that this blog looked terrible on a mobile, but I did nothing about it until @monkchips complained that it was unreadable on his HTC Magic, which runs Google Android 1.6.

I don’t have an Android device, but I grabbed the SDK, ran up the emulator, and had a look. The page took ages to load, and did not work properly even when fully loaded.

I figured “there’s a plugin for that”, and there is – several in fact. I settled on the WordPress Mobile Pack. Installed, configured, and a short time later was up and running.

I had a few hassles, mainly because most of my wordpress installation is not writeable by the web server, and this plugin needs to write themes on installation and temporary images after that, so I had to loosen permissions slightly. I then set the themes directory back to read-only, and configured the cache so that Apache will only serve images.

I still only get a score of Fair (2 fails) from the MobiReady report. Still, progress. I am ahead of bbc.co.uk which gets Bad (10 fails); but behind microsoft.com which rates Good (0 fails).

The plugin also tells me that 5% of the traffic to this site is from mobile users. More than I had expected.

Beep beep.