The critical differentiators in handsets now relate to making the mobile internet experience easier, and that means a shift in focus from the operating system to higher layers of software, notably the user interface architectures and tools. The famous touchscreen UI has been at the heart of Apple’s push into the handset market with iPhone, but while pointing the way that many phonemakers will need to follow, this remains proprietary. The company has already been forced to do a U-turn on opening the iPhone to third party developers (see separate item) and may find itself forced to make other compromises on broadening availability of its UI technologies, in order to gain mass in a mobile market whose dynamics Apple does not yet fully grasp. This is because the handset majors are rapidly catching up with the iPhone’s more advanced features, with Nokia and the Koreans, in particular, showing off Apple-like interfaces, but many of them are also promising to open up their UI platforms to gain market traction quickly and seek to set and control de facto standards. So last week saw Nokia reiterating promises to open up a new, advanced version of its Series 60 UI platform, just as Motorola acquired a 50% stake in Sony Ericsson’s S60 rival, UIQ, with the two companies pledging to extend cross-industry licensing. Meanwhile, rumors abound that Samsung is to adopt Sun’s Java FXMobile technology, also aiming to be a standard in mobile internet software environments, for its latest assault on this emerging sector.
Sony Ericsson acquired UIQ from Symbian, the Nokia-dominated mobile OS company, in February (see Wireless Watch February 19 2007), to provide a counter-balance to the most powerful platform, Nokia’s Series 60, and by pooling its efforts with Motorola ‘ which has lagged behind in the mobile internet UI stakes ‘ this challenge becomes really viable. Under the agreement, whose financial terms were not disclosed, the two handset makers will collaborate on and jointly invest in the development of UIQ, and will license it openly as an independent UI for smartphones and consumer electronics multimedia devices. Outgoing Sony Ericsson CEO Miles Flint said the deal “demonstrates the increasing importance of open operating systems for all handset vendors. By working together in a strong, mutually beneficial partnership, handset vendors can reduce development costs and help operators launch more consistent services with greater efficiency.”
Motorola has been a licensee of UIQ and SymbianOS for years, but has not exploited either technology nearly as significantly as the Scandinavian giants since it sold its share in the Symbian company four years ago (see Wireless Watch September 4 2003). Despite increasing activities in Linux and Java, Motorola has not made a major impact on this year’s rapid developments in web-oriented handset UIs, appearing to find it hard to escape its roots in the US, described by NTT DoCoMo last week as ‘the black continent’ in terms of uptake of mobile data services. Now its closer partnership with its rival Sony Ericsson, an advanced player in mobile web services, and its stake in UIQ should strengthen its hand.
The first sign came in May, when Motorola announced its first handset to feature the UIQ interface ‘ the RIZR Z8, based on designs acquired with UK phonemaker Sendo. This has been one of Motorola’s key launches this year, as it struggles to come up with another killer handset to follow the RAZR and boost its fortunes in its largest market. Satellite broadcaster BSkyB is offering the handset, allowing subscribers to access Sky’s mobile content services including its ‘Anytime’ application, which provides an access point to Sky’s live mobile TV services and the ability to programme Sky+ set-top boxes remotely. Such deals, outside the realm of traditional cellcos, are of huge importance to phonemakers as they seek to broaden their reach, and one of the critical factors will undoubtedly be the user experience.
However, buying 50% of UIQ rather than just licensing the technology is less about improving Motorola products than gaining influence over potential standards in a vital area of the market, and so hoping to weaken Nokia, which has been by far the most impressive phonemaker in terms of moving into advanced, vendor-neutral mobile software platforms, and is busily reinventing itself as a web services company. In these strategies, Series 60 and its related products, such as mobile browsers and widgets, are absolutely vital to Nokia, and it is also seeking to place itself at the heart of mobile web standards by licensing its platform to others.
Hitting back at this, Motorola and Sony Ericsson will aim to reinforce the message that UIQ has always been licensed to partners, and will try to build a power base around it. Important licensees already include embedded microprocessor leader ARM, Ericsson, and Texas Instruments. UIQ and Symbian are the basis of a joint development between the last two, which are working increasingly closely together as TI becomes less dependent on Nokia, focusing on reference platforms for 3G and beyond (see Wireless Watch July 30 2007). UI Holdings, the Holland-based parent company of UIQ, and Motorola also stress that they are hoping to expand the shareholder base of the venture, and are particularly keen to get other cellphone makers to participate.
UIQ was originally developed by the old Ericsson handset business, now part of Sony Ericsson, and it became part of Symbian in 1998, just after the OS venture was formed between most of the leading handset makers (see inset). However, UIQ was overshadowed when Nokia stuck with its own UI platform, and licensed this to Siemens, then the fourth largest phonemaker.
Reviving its flagging interest in Symbian technologies will bring short term benefits to Motorola ‘ allowing it to join the current trend for touchscreen phones; hedging the heavy bet it has made on the as-yet unproven mobile Linux; and strengthening its hand against Nokia S60 and the iPhone, even perhaps luring developers away from S60 by increasing support for UIQ. However, as with S60, broader ambitions will rest on opening up UIQ further, to open source communities and to other operating systems, rather than keeping it in a Symbian ghetto.
It may prove inevitable that, eventually, the UI architectures become OS-neutral, but for now, Symbian itself, of course, still aims to see off Linux and other operating systems by retaining the technical lead in key areas like the UI. For the short term at least, its latest developments will keep the Symbian option important to Motorola, despite its interest in Linux ‘ Linux UI and graphics systems like Motorola MOTOMAGX are not yet at the level of the advances unveiled by Symbian last week. At the Symbian Smartphone event the company showed off ScreenPlay and FreeWay, new graphics and communications architectures for SymbianOS itself. ScreenPlay promises iPhone-like graphics performance, including support for high definition video, through a set of fully open APIs. FreeWay extends communications support in Symbian to WiMAX, LTE and future wide area wireless technologies. It also supports seamless hand-off between connections to avoid interrupting user sessions. ScreenPlay and FreeWay are supported by the introduction of symmetric multiprocessing, enabling SymbianOS to run across multiple chip cores, through an agreement with ARM (see Wireless Watch October 15 2007).
Despite UIQ’s revival, Series 60 remains the strongest player in the mobile internet UI race, althoug challenges are promised from new Linux-based iterations of the Palm interface (from Access and from Palm itself), and from other Linux and Java oriented systems, notably Sun’s JavaFX Mobile, which complements its purchase of the SavaJe Java operating system (Qualcomm’s UIone is also a powerful offering, though still mainly confined to CDMA). Nokia is determined to keep S60 ahead of the game, and in the past year has made aggressive improvements to its developer program; has placed some elements into open source processes; and has hinted that it will port the Symbian platform to Linux. Now it is promising a new version of the platform.
This was shown off at last week’s Symbian Smartphone Show in London, and will be offered for license to Nokia’s rivals. As with the launch of the Ovi web services portal a few weeks ago, Nokia’s timing shows it trying to dilute the impact of the iPhone’s European launch on November 9 (see separate item). The Finnish giant said its new Series 60 will enable ‘new types of mobile devices, applications and services’. New features will include support for touchscreen interfaces with stylus or finger input, and with tactile feedback, with or without Qwerty or traditional keypads. This range of qualities addresses some of the criticisms of the iPhone, such as the lack of Qwerty.
Despite the competitive issues that other phonemakers will have with licensing from Nokia, the market leader aims to make Series 60 so far ahead of the pack in mobile internet interfaces that this will overcome other conflicts of interest. But the newly strengthened UIQ grouping could provide a powerful counterpoint, and Sun is attempting to build its own alliances around Java technologies and FXMobile.
There are widespread reports that Sun is partnering with Samsung to develop a handset ‘ inevitably nicknamed jPhone (for Java) ‘ based around FX Mobile and SavaJe. The latter’s aim, by pushing a cutdown version of desktop Java for mobiles rather than the mobile specific J2ME, was to encourage ‘write once run anywhere’ universality, and increase Java developer interest in the mobile platform by avoiding the fragmentation that has afflicted J2ME once it is deployed on diverse handsets. SavaJe gained significant operator lip service but few commercial sales ‘ only LG in Asia, plus Group Sense and Longcheer of China, agreed to deploy it – but it makes a logical fit with Sun’s Java portfolio, especially since the Java owner unveiled its FX Mobile range last May. This is based on a scripting language designed for creating rich content and applications to run consistently across all mobile and embedded Java devices. It is available to license by carriers, content owners and consumer electronics manufacturers and will also be available to the free and open source community via the GNU General Public License.
There are two areas where SavaJe, when combined with FX Mobile, is important to Sun in boosting its influence over the mobile platform. One is to counter the threat to Java ubiquity that may arise from the creation of mobile OSs that are open to direct downloading of applications, reducing the need for one of Java’s key functions on the cellphone. The other is to feed SavaJe’s strongest suits, notably its support for customization, into a potential Sun interface architecture that could challenge the existing players before the market gets too settled. Some useful aspects of the SavaJe IPR could aid in this process, particularly the high degree of customization it offers operators to differentiate their handset environment – something in which Qualcomm also excels since purchasing UIone. The all-Java OS uses deep theming functionality to implement operator specified applications and menus, as well as color schemes, sounds, background images and icons that affect both built-in and downloaded applications.
With UIQ and Series 60 gaining new momentum, and Symbian improving its graphics functionality ‘ all of these bringing in features that match or surpass those of iPhone ‘ the Symbian community is riding high and Apple’s usability lead under severe threat, making it more reliant on its brand to keep users signing up. But for all their faults, Sun’s Java developments are pointing the way to an OS-neutral, harmonized, end-to-end system, which could build a vast developer community and run across all kinds of devices, not just smartphones. To retain control of the direction of future standards, the handset majors will need to look beyond a single OS, however ahead of the smartphone game this may be, and start to port their platforms to multiple platforms.
Series 60 goes open source:
In May 2006, Nokia took its first move to make Series 60 truly open source, when it released to the open source community the engine underlying the S60 mobile browser.
Lee Epting, head of Nokia’s global software development community, said that by releasing the S60 engine to the open source community Nokia can encourage much needed innovation in the browser space while keeping the browser experience consistent across hundreds of smartphones. The S60 Webkit is available to anyone with an open source BSD license, a highly permissive license commonly used by free software developers worldwide.
The kit comes with the sourcecode of the browser engine codeveloped with Apple and based on that company’s Safari browser. At this point it does not contain other Series 60 components such as the user interface, allowing developers to create differentiated browser interfaces, although further release of S60 elements is widely expected.
‘If we can get to a point where we have one primary engine that runs all browsers, that’s what we’re aiming for,’ Epting said. As in other open source efforts, the most innovative additions to the platform coming from the developer community will be adopted by Nokia for the standard browser kit, making them universal components.
To assure itself of adoption by smartphone vendors worldwide, Nokia will almost certainly have to make further moves towards full Series 60 openness, such as offering a free license for the user interface and middleware, and porting it to non-Symbian operating systems such as Linux. Given that nearly all Series 60 devices currently available come from Nokia itself, only whole hearted openness ‘ with the economic benefits this would bring for licensees ‘ is likely to overcome the natural unwillingness of handset vendors to put themselves into the hands of their greatest competitor.
Other Nokia open source projects include Maemo, URI Query Agent and Python.
The Series 60 browser uses the same components as Apple’s Safari browser and is powered by the same open source technology, KHTML and KJS ‘ key elements of the open source Konqueror browser, of which Safari is a commercial implementation. It uses the WebCore and JavaScriptCore currently used in Safari and also incorporates mobile specific functions from the current Series 60 browser, such as small screen rendering and keypad shortcuts. Within the open source community, Nokia will bring this mobility expertise to bear on future releases of Safari.
Background to UIQ:
When Symbian was founded it was envisioned that it would provide a full software suite from kernel and device drivers to user interface. The OS was based on one created by co-founder Psion, but the company had already created six reference designs around this OS with different user interfaces (before the idea of a single UI for multiple devices was really taking off).
These early reference designs later evolved into Pearl (Smartphone, later S60), Quartz (Palm PDA, later UIQ) and Crystal (Clamshell PDA, later Series 80), after being mixed with the ideas and R&D of the other Symbian founders. Crystal was basically a port to Symbian of GEOS, which powered Nokia’s Communicator PDAs, a move that effectively killed off Psion’s own Eikon UI from its Psion-5 platform. Nokia was also developing a software platform for non-Communicator handsets, which became merged with Pearl and went on to be S60. It was at this point that Nokia decided to make Symbian its main route for smartphones, having also considered Linux and PalmOS. Ericsson’s Mobile Application Lab contributed its own UI development to Symbian, and this effort was merged with Psion’s Epoc Release 5 to create the interface for the R380, the first Symbian smartphone.
Around 2001, it became clear that Symbian’s ambition to create the full software value chain, including a choice of UIs, was beyond its resources ‘ and was probably obstructed by Nokia in its bid to dominate the process and push S60 as an openly licensed platform of its own. Nokia preferred to take SymbianOS but build its own upper layers and this would have significantly harmed any Symbian effort to create a collective end-to-end solution.
The Ericsson-derived Quartz UI was now being used in the Swedish company’s own Pamela PDA, plus a Sanyo tablet and the ill-fated Psion/Motorola Odin project, but none of these made it to market, leaving the future S60 well in the lead. Quartz was then redeveloped to become UIQ 2, which was used in the Sony Ericsson P800, one of the most successful early smartphones. In 2002 Motorola licensed UIQ and the system was included within the Symbian product, partly to meet the demands of NTT DoCoMo, but Nokia signed up the other Symbian partners, Samsung, Siemens and Matsushita, and gained greater commercial reach.
By the time Sony Ericsson took control of UIQ earlier this year, it had moved to its third iteration, UIQ 3, which is used in Sony Ericsson smartphones like the P990 and Wlakman 950. It is unique in that it offers support for multiple input types and form factor regimes from a single code base, something that Nokia will offer with the next S60, and that Microsoft is also promising for Windows Mobile.