Tag: android

Yahoo follows suit: presents development platform for mobile

After all the buzz in the back-end of last year over the Google-led Open Handset Alliance and their Android OS, Yahoo! has now presented its own view on how to reduce the complexity within the mobile landscape by announcing a development platform for “mobile internet applications”.

It is, alas, not the full bag of tricks: Unlike Android, which is of course basically an OS, the Yahoo! scheme only foresees tools to allow the creation of widgets to run under the company’s Yahoo! Go mobile service or in any mobile web browser. This means that “mobile internet applications” in Yahoo speak do not include “classic” mobile applications (developed in J2ME, BREW, Symbian, etc, and then downloaded to a user’s phone), and the latter will not benefit from the initiative.

The question (and this may well be one of the big ones for 2008) is therefore if the (short) age of downloadable applications is already dawning. Because, unlike the Internet, mobile is a cluttered space with a gazillion operating systems and middleware layers on even more different devices competing for market share. Ease to port applications at least across handsets and ideally also across operating systems is therefore the crucial factor. Only if downloadable applications (including indeed a software package like Yahoo! Go) really are displaced by the mobile internet proper would this change.

Commentators note that Yahoo! Go is not normally available on handsets as most tier-1 operators will (and apparently each and every US carrier currently does) simply remove pre-installed applications prior to delivery to customers. However, this does not seem to matter too much as far as the new initiative is concerned as it is said to run on every browser, too. It may take away from discovery and therefore usage so this is where it appears to chip away on the benefits: Whilst the Yahoo! move would seem the much less complex initiative compared to Google’s attempts to take on the OS heavyweights, it comes at the cost of lower usability for users and also less actual benefit for developers: why would you develop for that platform if visibility, discovery, usage and therefore commercial reward are foggy at best?

I’m not convinced (yet).

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.

Page 11 of 11

Powered by WordPress & Theme by Anders Norén