Tag: google Page 7 of 8

Linux Mobile pouts its LiPS

Now there’s been a lot of talk about Linux Mobile recently, with all that Google‘s or rather the Open Handset Alliance‘s Android stuff floating around (see e.g. here and here), and the good folks who aim to push this operaing system are quite naturally busy to ride the wave of excitement and attention over this (and are always very keen to stress that Android is a welcome addition to the forces rather than a bad competitor). LiPS is one of two consortia besides Android (the other being the LiMo Foundation) who intend to further the footprint of Linux in mobile, too.

And, just in time for Christmas, LiPS (whose members include Orange, France Telecom, MontaVista and Access) now has released its first specification. Well, to be honest, it is only the second half of what was already released in June but, hey, now it is complete: it provides APIs for telephony, messaging, calendar, instant messaging and presence functions, as well as – unspecified – “new user interface components.” LiPS stresses that it wants to allow developers to develop applications that will work on all phones under the standard, and from that point of view the voice API should be particularly interesting (voice-controlled games? Ah!).

Unlike its “competitor” (compatriot might be the better word) however, there have been no news on any handsets developed under that specification yet. The LiMo Foundation scored first-line honours here with NTT DoCoMo recently announcing its impressively spec’ed P905i (by Panasonic; using the Viera brand – see here for similar use of brands) and N905i (by NEC) handsets released under the LiMo Foundation specs (see for a showcase of the FOMA 905i series here and here).

A lot of action happening, and good stuff, too! Now, bundle your resources, folks, and conquer!

Verizon's group hug: now it also supports Android

Verizon‘s U-turn continues: the carrier now announced that they would support the Android OS promoted by the Google-led Open Handset Alliance. This comes only days after Verizon was met with a lot of raised eyebrows after it declared it would open up to handset manufacturers, service and application providers. Upon the launch of Android, Verizon was amongst a select few that were visibly reluctant to support the initiative, reportedly for fear of impinging on their customer base by not being able to control the user experience.

This move may well be an attempt to prevent Google from bidding in the 700 MHz spectrum, the auction for which goes ahead tonight: Google may not see the necessity to bid just as aggressively if it can basically fall back on an OS-agnostic carrier as it can then continue doing what it does best, namely sell ads. The proximity of the dates may indeed point into that direction.

Verizon Wireless had created the most profitable U.S. cellular business by tightly restricting the devices and applications allowed to run on its network. However, its management apparently now came to conclude that it was time for a radical shift: this will have been out of fear to be isolated in a niche when the rest of the market was overrun by new, more powerful devices as well as media empires old and new both of which would bring a richness of offerings mid-term that Verizon could not have supported within the constraints of its tightly-controlled environment.

It may also have thought that opening up would help them to keep growing while containing costs; probably a bit of everything. That last bit is of course one of the reasons that led many partners to throw their weight behind the various OS campaigns that recently appeared to have picked up pace: the LiMo Foundation, C-based Nokia-owned OS Symbian and the Sony Ericsson and Motorola-owned UIQ (in which Motorola had just acquired a 50% stake; see here) will also be driven by the OEM’s attempt to contain cost. Unified OS make mass production much cheaper (and the famously robust Linux kernel also will allow stability whilst being flexible enough to allow enough flavours to keep every marketing and UI expert happy, too).

Everyone coming to their senses? Oh, brave new world.

Verizon opens up

US #2 carrier Verizon, the famed high priests of the walled garden said they would open their network to 3rd party devices, applications and services. Skeptics say this might just be a move ahead of the spectrum auction for the 700MHz range, in which Google had declared an interest, too. Commentators say it might be an attempt to discourage Google from throwing its head into the ring but they maintain that VZW will not be seen to reducing itself to a bit pipe.

However, the commitment to open its network may also mean that Google, in the wake of its Android OS promoted with the Open Handset Alliance (see here), may no longer feel that they have to spend billions of dollars to acquire the bandwidth necessary to pave the way to customers: with an open network environment, Android-based devices may very well also be running on Verizon’s network so Google may no longer need to go to the expense to providing an alternative route.

Apart from the considerations mentioned above, Verizon is under pressure to encourage device makers also from the neighbouring areas such as tablet PCs, dedicated gaming devices, etc to build hardware that works on its on EV-DO network rather than only on the UMTS-powered networks of most of its competitors. With ongoing convergence of the various screens and their inherent agnostic approach to whichever technology is being used, it is important not to fall behind as Verizon’s network might otherwise become an isolated island with only sub-par devices and less choice than with competitors.

So whichever good or bad intentions Verizon may have, it is opening the walled gardens a little bit more, and that surely is a good thing!

The G-System: Google's mobile OS aka Android arrives

So, no GPhone — yet. Google, with quite a number of partners, today announced the already much-rumoured “Open Handset Alliance” under which a Linux-based OS, nicknamed Android has been launched (the SDK will allegedly be available in a week’s time). Here’s a video explaining the deep thoughts of the creators (be quick: YouTube has removed it already…).

The whole industry had been waiting for this, and Google seems to have come up with a black-white thing: it goes back to its roots in open source but overlays it with Java, which has caused the content community a lot of headaches (every mobile phone translates it slightly differently, so one needs a gazillion ports). However, Google has teamed up with no less than 34 partners for the launch alone, including such giants as China Mobile, KDDI, Sprint Nextel, TIM, T-Mobile, Motorola (who seem to be dancing on a lot of weddings recently: UIQ and Linux Mobile are also on their plates), Samsung, HTC, Intel and eBay.

So what does it all mean? According to the members of the alliance, it will be better, bigger, faster for everyone: open source means more applications, less bugs and less cost. According to Google CEO Eric Schmidt, it is “a fresh approach to fostering innovation in the mobile industry will help shape a new computing environment that will change the way people access and share information in the future.” Commentators note that there is apparently one caveat: you’ll have to use Google for navigation. Now: does that bother anyone? Give me Internet on my phone on broadband speed and I happily surf with whoever gives it to me, I’d say. To enact a platform, supported by a lot of sector muscle, that makes the developers’ life easier should be good for everyone indeed as it will undoubtedly bring more usage. Traditionally, carriers feared for the consistency of the user experience. Apparently, Verizon and AT&T have already voiced such concerns also here although the explanation sounds defensive at best: they fear too much advertising. Would it be safe to say they rather fear loss of control?

Quite a few companies have tried to take on mobile as the next frontier and quite a few fared rather miserably on the complexities of the environment presented by the sector (Disney’s MVNO attempts, Infospace and a few others spring to mind). With Google’s might this might be about to change though. A fresh breeze and a unified development platform would, in any event, be a good thing.

Interesting though that, as in recent releases on OS-driven initiatives, Nokia is again absent. This is not promising any good in terms of unifying the landscape, it seems. However, both Linux Mobile (on which Android is apparently based) and Symbian (in which Nokia holds a huge stake and which it intends to make its platform of choice) are C++-based. And that would be easing development pains after all: much easier to deal with than the Java layers, which until now were statutory but might only be optional going forth.

UPDATE 7 Nov 2007: Nokia has said its participation in Android is “not ruled out at all”. It would work with it if it would see sense. Now, a convincing statement sounds differently but it IS noteworthy that the Finnish giant felt the need to comment on it so quickly.

Google goes "livestreaming", acquires Jaiku

Now, this is not strictly mobile BUT then it is considering that the target of which I report here today is heavily using mobile as a tool to feed its community, namely SMS (plus web and IM). It morphs online and offline worlds (nicknamed “bothline”; see here), and mobile is a huge component of this.

Anyway, Google, it was announced, has acquired the good folks from Jaiku. For those not that familiar with the radically new web 2.0 applications: Jaiku is a Twitter competitor where you basically “speed-blog” or “live-stream”. Jaiku adds proximity settings: users in the same area can/will be able to get in touch with each other and interact.

At PICNIC’07, I recently had the pleasure of listening to Jaiku’s co-founder, Jyri Engestrom (plus the good guys from Twitter, Plazes, Dopplr and Hyves), talking about the relevance of applications such as Jaiku. There is a video of the session available here.

It is (still) all about relevance and context. Jyri observed that context evolves around objects (such as office, Manchester United, kite-surfing, babies, red Bordeaux, and, yes, location…). The object defines the (social) context: you might be interested in the capability of webservers in your professional environment and discuss this wholeheartedly with someone else with who you would not have a single point of mutual interest outside of work. Change the object, change the context. Jyri (in his rather interesting blog) calls this object-centered sociality (yes, he is a sociologist).

Jaiku supposedly helps making focus on any object easier as it provides quick and universally accessible tools to see the activity streams of your contacts. The mobile version does this by getting those streams directly into your phone’s contacts. Cool stuff.

However, why would Google buy them (apart from it being cool and Google being cash-rich)? Relevance and context, again. These are the core pieces around which Google’s core business evolves: put ads in a relevant context and you improve click-through. Jyri characterized this by drawing the history of content discovery from catalogue (Yahoo!) via pagerank (Google) to what he termed “facerank”, combining the power of the search algorithms from Google with the power of the social network from Facebook. The latter is e.g. a search result that would take the social context of the, say, search string (the object). Friends, people close to you, colleagues, other fans of your club, etc are more likely to have come across something that is relevant to you than someone who has no touch-point with you whatsoever. You don’t have to know them personally: connoisseurs of Bordeaux wines might only have “met” in the virtual world. Still, since the context evolved around a common object (Bordeaux wine), it is more likely that you will hit a relevant spot through them. The higher the socially-enhanced rank of a search result, the more relevant it is likely to be… Compelling and rather inspiring!

So this is what Google may have in mind: bring the context to the people — again! Well done, guys!

Nokia maps it out, buys Navteq

Nice thing if you can get it: for a modest $8.1 bn ($7.7 bn if you discount the cash the company has in its coffers), Nokia acquired the provider of digital maps, Navteq. Even though this marks Nokia’s largest acquisition ever, it is a hardly surprising move given the recent activities of the company to flex its muscles in the content space. Its Nokia Maps application cried out for something like that (it ran on Navteq-supplied maps anyhow). To combine GPS-equipped phones with the people who power loads of todays digital maps seems smart, in particular when one fairly apparent new competitor in Nokia’s courtyard runs a fairly successful digital mapping solution itself, namely Google: If the proprietor of Google Maps enters the handset market with the already somewhat fabled GPhone (another article here), Nokia is arming itself to withhold and defend its still impressive market share of c 1/3 of the global market for mobile handsets, errh, multimedia devices. Last year’s acquisition of Gate5 seems to not have been enough for that. No other big OEM has come out with GPS-enabled devices with force yet, so Nokia’s move would also cement its positions amongst its current peers.

So what will we see? Easy, huh? After turning mobile phones in multimedia computers and slashing away on the digital camera and music player market along the way, navigation systems (or “sat nav” as your ubiquitous salesman affectionately calls it) will apparently be the next victim: who needs them if one has a GPS-equipped Nokia N95 (which, yes, also comes with a digital camera powered by a prestigious Carl Zeiss lense and has 8GB space to accommodate your music and videos).

This is the near-sighted and easy bit and I am all for it: if I can have the quality of specialist devices merged into one, then that is my device of choice even though the challenge is that you then have to beat every leader in the segment. But the history of camera and music phones shows that there is a niche that is rather a gaping cleft, in particular when also cleverly branded, and one that is apparently growing. So why not for sat nav, too?

The magic word however is context-awareness. It can probably be called the holy grail of service and product discovery and the provision of relevant offers: if I am being offered something in a context that makes the offer relevant, I am much more likely to be lured into using/buying it. This is exactly how Google’s famed AdSense works (and advertising is an area Nokia recently focussed on, too, i.e. with the acquisition of Enpocket).

The principle of context increasing relevance naturally applies to everything: if I am hungry, I am more likely to visit a restaurant. If I am at an airport, I am more likely to be interested in flight times, or travel offers, etc, etc. So combining a device that adds an important context parameter, namely location with a platform like Nokia’s Ovi that adds an array of different services (games, music, maps, etc) looks like a model that should increase the likelihood of a purchase – because it can offer the user a more relevant offering in the context in which he uses the device. Nokia seems to be finding it easier to get its content-loaded multimedia devices past the carriers’ doors, too, that is if Graeme Ferguson, ex-Vodafone Content Meister, is to be believed…

However, I will continue to call it a mobile phone…

Page 7 of 8

Powered by WordPress & Theme by Anders Norén