Tag: UIQ

Fragmented?

Funny. Sometimes a theme somewhat haunts you… After I have posted about the demise of Tira Wireless (and added some alternative views on the labyrinth that is platforms and handset fragmentation; also go and revisit my posts on the same topic here and here), today we can read that it will all get worse (or maybe not). I bet they read my recent post on the issue… 😉

The article only mentions somewhat curtly two new platforms, namely iPhone and Android (both of which I have covered before, namely here, here and here – amongst others), and then goes on to report on a panel at CTIA where a panel sponsored by the “Symbian stakeholders” apparently dismissed the whole notion, stating that the market would solve it. Now, it will have to, I guess. However, it is not all that bleak: Symbian, UIQ, Linux, BREW, Win ME and ultimately the iPhone OS are all C-based. Most of them (with the notable exception of the iPhone) also run Java Virtual Machines (JVM), so you can either code in J2ME (which is arguably the most widely supported language) or go native and code native in C+/C++ with then much easier ports to the varying iterations.
The challenge naturally remains (and, yes, I have voiced this previously) with a view to supporting all those odd handsets here and there and everywhere but, let’s face it, a lot of them are being imposed on publishers by the carriers who want to make sure that even that last customer that hangs on to his SE T-610 will be served with content (even though he won’t ever download a piece). Wouldn’t it be so much better marketing if they would simply return a message telling that poor customer:

“Hey, we noticed you tried downloading content to your T-610. You may not have realized that this phone is utterly outdated and will give you no joy when playing games. We would like to offer you a discounted upgrade to the brand-spanking new N76/ W880i/ Pearl/ iPhone/ Viewty/… and your life would be so much cooler. We are confident that you would then also have more luck with the girls/boys… Best. Your carrier”

What I am trying to say is that a lot of the fragmentation issues are (nowadays) artificially imposed, not technologically warranted. Any carriers reading this? Think about it, folks. It won’t harm you, I bet!

Mobile Games: Platform Standards!?

Mobile games blogger extraordinaire, Arjan Olsder, provided for a great guest post by Qualcomm games guru Mike Yuen, and it’s well worth a read! Mike addresses this most horrible of issues to mobile game developers that is called fragmentation or, in his words, “[t]he lack of platform and hardware standards continues to be a major inhibitor to mobile game growth in the United States [and elsewhere; ed.]. This diversity in development platforms (Android, BREW, Flash Lite, iPhone, Java, Linux, Symbian, WAP, Windows Mobile) and hardware configurations (display resolutions, RAM/heap memory size, processing and graphics power, audio formats, keypad and other input modes.”

Mike rightly points out that, “[i]n many cases, the costs associated with individualizing software builds to the particularities of each handset, operator and language account for more than half of the overall development budget for new game titles. It’s a simple, but important concept. If fewer resources were diverted to porting a title from handset to handset, operator to operator, more resources could be dedicated to advancing the development of new and innovative gaming concepts.”

He goes on to draw an interesting comparison to the Korean and Japanese markets where there are not as many handsets (and platforms) around and where consumers are more than twice as likely to download mobile games. He then goes on to look at market disruptors like Apple (iPhone anyone?) and others only to conclude, sadly, that “[m]obile gaming is in a state of flux – platform and hardware fragmentation has clouded the once blue sky of gaming’s future and positive disruptive products such as Apple’s iPhone have changed industry perception and consumer expectations about the future of the mobile gaming device. I’m not expecting us to reach consensus anytime soon. Fragmentation is an inherent element of the mobile industry and perhaps always will be.”

Now, is that really so? He is of course right in his analysis of the current environment. But does this really have to be like this? The mobile space suffers from too many very large companies with very large markets. And if this wasn’t enough, there’s two different groups of them, with diverging interests, namely operators (carriers) and handset manufacturers: the former want everyone to be on their network, the latter to be on their handsets. Both are more often than not big old molochs of companies with a lot of market power in their segments. However… the markets seem to gravitate (under consumer demand) towards a more open set-up: operators seem to be accepting the fact that they cannot reign their users into walled gardens forever (more and more resign to flat-rate data and open the mobile web to users) and OEMs seem to realize that they need awesome numbers of users to have a real impact and so most of them gravitate to more open platforms (or, in the case of Nokia, create them).

As most of the newer platforms appear to be based on C++ or siblings thereof (Symbian, UIQ, Linux, Android [yes, I know that they us a JVM], BREW, Win ME, etc), it would appear that a reduced complexity might be nigh. Not as easy as online, mind you, but light at the end of the tunnel nonetheless. And it makes sense as the current fragmentation isn’t really helping anyone: consumers grow frustrated with ever-changing platforms. They want cool content, not a proprietary operator-variant of cool content. Hope, my friends, there is hope!

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.

Motorola loves UIQ

US handset maker Motorola acquired half the shares in UIQ, the smartphone software unit, from Sony Ericsson. Sony Ericsson had bought UIQ from handset OS maker Symbian last year. UIQ is essentially a graphic interface adding components to the Symbian OS. Symbian in turn is 47.9% owned by Nokia. Under UIQ, native programming can be made in C++ although the software does support the – in the mobile games space – ubiquitous J2ME standard. Motorola’s new flagship Z8 (nicknamed “MotoRzr” as in “riser”) is running on it already. The battle of the OS giants begins…

It is an interesting move since Moto has been the most active OEM for the use of Linux Mobile: it has released a whole range of phones for the open source OS featuring the penguin. It is also one of the founding fathers of the LiMo Foundation, an initiative it embarked on together with industry heavyweights NTT DoCoMo, Vodafone, Samsung, NEC and Panasonic (and which was recently joined by LG, McAfee, Broadcom, Ericsson and others). Now, I understand that Linux and C++ work together but must admit that my knowledge is more than limited here. It is in any event noteworthy that Motorola goes with a UI based on Symbian rather than straight-forward Linux. Motorola was quick to state that UIQ would only be “one of the actions to support [a] strategy” adding more investment in multimedia product segments.

With hundreds of millions in development cost at stake, it is probably too early to tell but it certainly is a new twist in the quest to uproot Nokia‘s top position with the Symbian s60 platform. So, what’s next?

Powered by WordPress & Theme by Anders Norén