Distilling market noise into market sense

The VisionMobile blog is a space where VisionMobile analysts and industry insiders exchange views on the fast-changing mobile market and the trends that define the future direction of telecoms.

  • 20
    Oct
    2008

    Who will win the race of mobile application runtimes?

    [Flash Lite, WebKit, Java ME, Silverlight, Qt, Lua, Python… Research Director Andreas Constantinou takes an analytical look at the new battleground for mobile application runtimes and the struggle for dominance.]

    Flash Lite and Java have been quietly penetrating the mobile handset market. Both application runtimes have in a sense shown that openness is not an exclusive privilege of open operating systems, but of the majority of mobile handsets.

    A new set of application runtimes have also surfaced in the form of WebKit, Silverlight, Qt and Lua – shifting the battleground for software platforms from the OS level in 2002 up to the application runtime level in 2008.

    We have explored the wide range of application runtimes before – but we have recently analysed how the key contenders compare and contrast. The next table lists the commercial, product, licensing and technology terms for seven leading runtimes. I will be discussing this analysis with a panel of industry execs at the Symbian Show on October 22nd in London.

    Mobile application runtimes

    Java ME is the most pervasive application runtime, installed on approximately 8 out of 10 handsets shipping in 2008/9 by most analyst estimates. Java’s proliferation looks set to continue as Motorola plans to release the MIDP3 source code under an APL2 license by April 2009, which should reduce both fragmentation and the costs of implementing Java ME for handset OEMs.

    Adobe’s Flash Lite reached the 500 million installed base mark in May 2008 and looks set to penetrate even further thanks to the zero royalty fees that Adobe has pledged. The exposure of the underlying Flash Lite device integration layer should enable OEMs to develop more tightly integrated and more consistent FL implementations. Nokia has already integrated Flash Lite 3 on the latest S40 6th Edition platform; note that the S40 operating system is on more than half of Nokia’s 40% share of annual handset shipments. The Finnish OEM also plans to integrate Flash Lite more tightly on S60 through Platform Services. Sony Ericsson has also been pushing Flash Lite integration into Java apps through project Capuchin (see earlier analysis).

    WebKit has been a surprise in the making during the last 5 years. Although initially developed as the engine to Apple’s Safari desktop browser, the software has been evolved and optimised significantly; Nokia’s mass-market S40 6th edition OS features WebKit, as do Nokia’s S60, Motorola’s WebUI, Adobe’s AIR and Google’s Android.

    Silverlight is a newcomer from Microsoft, aiming to compete head-to-head with Flash Lite, and initially expected to appear on Nokia S60 handsets.

    Qt presents an interesting riddle. We believe that Qt is Nokia’s technology platform for deploying Ovi services across mobile devices and consumer electronics. Longer term Qt should be forming a platform for Nokia to deploy their own apps and a consistent signature UI environment, although the transition will take 2-3 years to materialise.

    Lua is an interesting new contender; it is a scripting language optimised for embedded environments and is known for both its simplicity and flexibility compared to JavaScript. It’s also licensed under the permissive MIT license, which has resulted in it being adopted and embedded into games SDKs and most notably as part of the BREW platform and Qualcomm’s uiOne SDK 2.0 (see details here).

    I will be moderating the panel ‘Who will win the Runtime race?’ at the Symbian Show on October 22nd in London. joined by well-respected representatives from Adobe, Microsoft, Nokia, Sun and Symbian:
    - Jürgen Scheible, author ‘Mobile Python – Rapid prototyping on the mobile platform’
    - Pete Barr-Watson, Senior Business Development/Deployment Manager, Microsoft Silverlight
    - Terrence Barr, Senior Technologist and Community Ambassador, Sun Microsystems
    - Antony Edwards, VP Developer Product Management, Symbian
    - Matt Millar, Director of Mobile and Devices, EMEA, Adobe
    - Benoit Schillings, CTO, Trolltech/ Nokia

    If you are attending the Symbian Show, do join – I do expect an intense and stimulating debate as we discuss which application runtime will win.

    Thanks to Erik Jacobson, Timo Bruns and Terrence Barr for their feedback on the comparative table of application runtimes.

    Update: The keynote panel session went well. I did not expect any revelations, especially in front of an audience of 1,000+ people attending the panel. But there was one very interesting announcement at the Show; the role Qt will play for Nokia’s applications, devices and Ovi.

    Qt's role for Nokia

    This slide, originally from Nokia’s analyst webcast on Qt on Oct 28, is quite revealing. Nokia is planning to use Qt, its cross-platform application environment, to port its own core applications and Ovi services across a broad range of devices. Qt will then be ported onto S60 (as Nokia announced) as well as across the Nokia device portfolio – which includes S40 – as this slide reveals. Naturally, Nokia’s Ovi services should expand to non-Nokia phones and desktop PCs. We predicted this strategy for Qt in earlier research notes here and here, but Nokia is moving much faster than we were expecting.

    Another interesting quasi-announcement was that WebKit will be one of the key pillars of the Symbian Foundation efforts, as announced by Lee Williams, the newly appointed head of the Foundation. WebKit is already integrated on Qt, so we should see the Qt + WebKit stack penetrating mobile devices very fast very soon. In the light of these announcements, we have upped our estimates of Qt embeds in 2009 to 50M handsets, assuming S60 starts shipping with Qt from 2H09.

    So which application runtime will win? If Google searches is anything to go by, then WebKit is clearly the ‘runtime of the year’ for 2008. As for the foreseeable future, one thing is certain; there will be more runtimes supported by mobile devices, before real consolidation settles in.

    Google Trends - runtimes

    - Andreas

    Andreas Constantinou

    Andreas Constantinou

    As Managing Director, Andreas oversees the growth and strategy of VisionMobile. He has twelve years experience in mobile, having worked with the top brand names in the mobile industry including Telefonica, AT&T, Telenor, Vodafone, Deutsche Telekom, MTS, Nokia, Sony, RIM, HTC, Qualcomm, Ericsson and Microsoft. Over the last five years, Andreas has grown VisionMobile into the leading, most respected research firm on telco economics and developer economics, with a client base and reputation that out rivals companies many times the size.

kadypk

You are aware that Qualcomm has announced that it has licensed Adobe's Mobile Client (latest incarnation of Flash Lite) for the next generation of BREW Mobile Platform. One might speculate/conclude that they will be ditching UIOne in favor of Adobe's mobile Flash technology.

 
22Oct
David Mery

A requirement for a "winner" is to be shipped in ROM/Flash. The story of OPL makes that clear. Another related requirement again exemplified by both OPL and Py60 is for the environment to be stable, have major number (i.e., changing the name from 0.9 beta to 1.0 final with no other change has a dramatic effect on adoption) and have a roadmap (i.e., be officially supported). This has a chicken and egg effect. It meant for example that OPL had more, about 1.6x, downloads than Py60 and hence was considered more of a success.

The main difficulty is not so much the interpreters (at least if speed is not essential) but the availability of a rich set of libraries. This in turn raises the question of whether the winner is to have a set of common libraries with bindings for most/all of the interpreters available or focusing on one or a few runtimes.

BTW, there have been several ports of Lua to Symbian OS. I can think of two (pre Symbian OS v9) off the top of my head: one by the Chinese company Noumena to use in its games and another by Intuwave to create a command interpreter for its test solution. There were/are likely other such ports. There also have been ports of many other interpreters to Symbian OS such as IO, Ficl, VisualBasic, Simkin, Perl, GOO, Squeak, EMP and probably more; and of course Ruby 1.9 was demonstrated at the show <a href="http://(http://www.pragmaticomm.com/MobileRuby)” target=”_blank”>(http://www.pragmaticomm.com/MobileRuby)

br -d

 
22Oct
Andreas Constantinou

Kadypk,

Yes, Qualcomm's licensing of the Adobe Mobile Client should mean a tighter integration of Flash Lite onto BREW. One could speculate on the repercussions for uiOne, but I wouldn't risk any conclusions yet.

David,

Very good points. It is debatable how important is a consistent addressable market vs a rich set of libraries, for the success of a runtime. Sun would argue that Java ME has the richest set of libraries, but then again the installed implementations are far from consistent. It is interesting to observe here that Nokia's Platform Services is an API integration layer that connects WebKit (and soon FL) to the S60 APIs. It does seem that Nokia's approach is

a) promiscuity to many runtimes – WebKit, FL, Java, Python, with

b) consistency of platform integration, via Platform Services.

Very interesting to here about the breadth of other interpreters ported to SOS, incl. the instances of Lua. Thanks for sharing.

Andreas

 
23Oct
Mark Wilcox

Hi Andreas,

I think your estimate for devices addressable by Qt is way too low. It should be possible to target all devices from S60 3rd Edition onwards with Qt (currently it's officially 3rd FP1 but there's no technical reason for this). Also, Qt is already available on Windows Mobile and embedded Linux platforms.

Since Qt is native code it isn't really a "runtime" and the necessary DLLs can simply be packaged with your application.

Generally I'd agree with David, a runtime has "won" when it gets included in ROM, which Qt (and I think probably PyS60) will eventually. Other than that there will be no outright winner since they'll all be used for different purposes. So in essence the "who will win" question is pretty pointless.

In terms of winning over developer mind share, the ones with the handicap are Java ME (previous bad fragmentation experiences) and Flash Lite (high cost of tools). The web runtime (although I'm no fan) has a massive head start since almost anyone can code JavaScript.

Mark

 
24Oct
Andreas Constantinou

Hi Mark,

Following Nokia's announcement of Qt on S60 (and across the Nokia device portfolio) I have up'ed our previous estimate of Qt in-ROM embeds for 2009 to 50M handsets.

You make a fair point on the Java ME and Flash Lite handicaps – and WebKit is perhaps the revelation of 2008, evolving from a new kid on the block to stardom, thanks to Nokia's commitment for deploying WebKit on S40 and Symbian Foundation code.

Andreas

 
29Oct
Stormy

Andreas,

Thanks for the detailed post with tables and graphics. I always enjoy reading them.

I was confused by your definition of "runtime". I wouldn't have put Qt, Webkit and Python in the same category. Would you also include GTK+ and Moblin your runtime category? Or are they separate?

Thanks,

Stormy

 
03Nov
Andreas Constantinou

Hi Stormy,

Technically I would define a runtime as an application environment that manages the application lifecycle, communication and memory use (in the traditional sense of a Java VM or Microsoft COM). In this sense Qt, Flash Lite, Java, Python and Silverlight fit well within the runtime category. Lua is on the borderline of this definition because it is a blueprint for a runtime implementation. GTK+ is a set of graphical libraries and primitives, so it doesn't manage application lifecycle as far as I know. Moblin is a complete stack including OpenedHand graphics libraries and its own application framework – so in this sense Moblin is a superset of an application runtime.

Andreas

 
03Nov
Erik

Instead of WebKit as the winner, I've been thinking it's actually AJAX, thus WebKit's JavaScript engine is just one of various JavaScript engines (in fact Google used a different one for Chrome). We'll have to see if multiple [open source] JavaScript engines can survive.

However I believe that actually AJAX is the winner for fast delivery of services/apps (and thus fast-changing apps), however for middleware/servers/daemons that are not written in C/C++, it's more subtle. I was impressed by Sean Moss-Pultz OpenMoko replacing C/C++ with Python.

http://www.iconocast.com/EB000000000000027/S5/New

 
04Nov
Erik

Oops! I meant to say that I was impressed by Sean Moss-Pultz from OpenMoko, talking at OSiM Berlin about replacing C/C++ middleware with Python!

 
04Nov
Andreas Constantinou

Hi Erik,

JavaScript engine fragmentation is a new problem and I wonder how Apple will react. The Google fork is unsettling the equilibrium of power around WebKit code development.

As for Javascript winning, I don't see Javascript deployed as a standalone engine far beyond WebKit and Flash Lite. So I would consider FL and WebKit as the main two contenders which encompass a Javascript interpreter. So I agree that Javascript will be most widely deployed, but not as a standalone runtime, rather as a component of WebKit and FL.

- Andreas

- Andreas

 
04Nov
Erik

JavaScript engine fragmentation might not be such a big issue. As Jon Ferraiolo from OpenAJAX pointed out to me, these days AJAX frameworks take (most of) the pain out of developing for different browsers (quirks). Thus let the framework vendors/providers take the pain.

In fact, about a year ago in an internal report I predicted the bundling of something like JScript or Prototype on the phone – then in September this came along: http://jquery.com/blog/2008/09/28/jquery-microsof

I agree that JavaScript will be mainly deployed as a component of WebKit and FL; but that other runtimes will be used for system components (not apps). This may end up as a couple of common runtimes (e.g. JVM or MS CLR) with various different language bindings.

 
06Nov
Andreas Constantinou

Hi Erik,

Interesting factoid about jQuery being adopted by .NET and Web Runtime. I agree re: JVM being used for system components. MS CLR: not sure how long can Microsoft continue supporting .NET CF on mobile.. it would be interesting to see stats on .NET vs native apps that have been written for Windows Mobile, but my guess would be that most developers go for native.

Andreas

 
06Nov
Rapid Prototyping

well it be good luck for all those contestant in that competition

 
02Feb
Aida Kreuzfahrt

So far it looks like Nokia will win the competition but I think Apple is pretty close. Lets see what 2011 will bring and what new developments will happen.

 
06Apr

Vision Mobile Blog

Distilling market noise into market sense

The Mediatek Phenomenon: the new smartphone disruption shutterstock_106186655

[The next disruption in smartphones comes not from the power struggle between Apple, Google and Amazon, but from silicon. Guest…

Continue Reading
[Infographic] Developer Economics 2013: Dev tools are the foundation of the app economy DE13_preview

We’d like to present our latest infographic, based on the latest Developer Economics report – themed around dev tools. This…

Continue Reading
Connecting the next 5 billion users: Emerging markets and the need for new business models Business model innovations for connecting the next 5B users

[With so much excitement about smartphone growth, we often forget that the biggest opportunity still lies ahead, in connecting the…

Continue Reading

Vision Mobile Research

Analytical reports on emerging solution markets

Mobile Insider Oil pump on the sunset sky

Mobile Insider is a monthly publication that examines under-the-radar and forward-looking trends in mobile. Each issue focuses on a specific…

Developer Economics 2012 Developer Economics 2012 - VisionMobile

Welcome to Developer Economics 2012, the third in the report series that set the standard for developer research. This report focuses…

Mobile Innovation Economics MIE

“Mobile Innovation Economics” is a strategy workshop that delivers a 360 degree view on how the telecoms industry is disrupted…

Vision Mobile Strategy

Market Sonar MarketSonar_ill

Market Sonar is a customisable reporting service, based on Big Data from all major app stores. We deliver monthly, quarterly…

Report: Telco Innovation Toolbox Telco_web

Telco Innovation Toolbox showcases 10 economic models on how Telcos can manage disruption and reinvent themselves. This report, produced in…

Telco Innovation Toolbox VM029 - SEBroc_V0.5_HR-1 copy

“Telco Innovation Toolbox” is a strategy workshop introducing the new economic thinking necessary for successful innovation by telcos. Aimed at…

Privacy Policy

1. Introduction

VisionMobile Limited (referred to as “VisionMobile”, “we, or “our”) is committed to protecting the privacy of visitors to the VisionMobile web site(s) together with all related surveys, discussion forums, directories and databases. This privacy policy explains how we collect and use the information we collect about you.
By accessing and using this web site, you agree to the terms of this privacy policy.
As used in this Privacy Policy, the term “Personal Data” means data such as: your name, mailing address, e-mail address or other personal information that may be supplied by you or collected about you. We hope that this Privacy Policy helps you understand what kind of Personal Data, if any, we collect at this site and how we handle and use any such personal data after collection. Please note that we may provide aggregate statistics about our surveys, sales, traffic patterns, and related site information to reputable third parties, but these statistics will not include personally identifiable information (such as name and email address). VisionMobile is committed to protecting your privacy and does not engage in the practice of selling or trading Personal Data to other companies for promotional purposes.

2. Personal Data Provided by You

To respond to your questions, fulfill your requests or manage our online Surveys, it may be necessary to ask for or obtain Personal Data. If you provide us with any Personal Data, we may use it to respond to your requests or manage our surveys. By providing information to VisionMobile through this Site, you acknowledge and consent to the collection, use and disclosure of personally identifying information of the type and for the limited purposes described in this Privacy Policy.
If you place an order for a product, request a service or submit content to this site, we may need to contact you for additional information required to process or fulfill your order and/or request. Unless compelled by applicable law or administrative or judicial order, we will not provide this information to a third party without your permission, except as necessary to process your order, fulfill your requests, manage interactive customer programs or, if you are a corporate user, enable administration of access and usage of this Site by authorized personnel in your organization.

3. What type of information is collected?

To provide you with our Services and/or Products and to collect your views via our online surveys, we collect certain personal information about you. The information we collect may include, but is not limited to, your name, address, email address and work details.
We do not store credit card or debit card details. If you have given us your credit card or debit card details, we will only use this information to process your order and we will delete this information once your order has been completed.
We do not collect any sensitive personal information such as information on your racial or ethnic origins, political opinions, religious beliefs, trade union affiliations, sexual life, health or criminal history.

4. How is information collected?

We may collect personal information about you from the following sources:
4.1 Personal details registered by yourself in relation to VisionMobile online surveys.
4.2 Personal details registered by yourself in other ways e.g. via our website feedback forum or our Blog
4.3 Information about your visits to our web site(s);

5. How long is the information retained by us?

We only collect information which is necessary for the operation of our web site(s) and for the provision of our Services. We will not keep your personal information for longer than necessary to provide the Services or as required by law.

6. External Web Sites

This privacy policy only applies to our web site(s). Our web site(s) may contain links to external web sites. Please note that we are not responsible for the privacy practices of other web sites. We recommend that you check the privacy policy of any other web sites you may visit through the web sites.

7. Changes to Privacy Policy

We may amend this privacy policy from time to time. If we make any changes we will post them on the web site, so that you will always be aware of the way we use your personal information.
terms of use.
The contents of the VisionMobile Forum are licensed under a Creative Commons Attribution 2.5 License. The contents of the downloadable papers published through this website are licensed under the terms specified within each paper. The remaining contents of this website are licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License.

8. Cookie Policy

Cookie Name Info URL Info
_vm1 VisionMobile The purpose of this cookie is ensure that a user is authorized to download the report . Vision Mobile does use the data stored in this cookie in any other way.
_prli_click_? Pretty Permaling The purpose of this cookie is to log information from the Pretty Links Lite Plugin in order for the plugin to know that the user has clicked in the pretty link of the (id=?) to go to the VisionMobile website.
mp_2dccbf28670dda1c8b77def198be2f89_mixpanel MixPanel The purpose of this cookie to use mixpanel to identify the mixpanel user to track the flow of the visitors from page to page. No personal or any other private information is captured.
(a)_utma
(b)_utmz
(c)_utmb
(d)_utmc
Google Analytics (a)This cookie tracks the number of times a visitor has come to www.visionmobile.com including their first and last visits.
(b)This cookie tells VisionMobile from where you, the visitor, were referred to www.visionmobile.com
(c)This cookie is used to determine the length and time of your visit to www.visionmobile.com
(d)This cookie works with _utmb to determine the length of your visiting session to www.visionmobile.com and when that session has ended.
VisionMobile does not use the data stored in these cookies in any other way.
(a)__qca
(b)mc
Quantserve (a)The _qca cookie may use your computer’s IP address, pixel code, referring HTTP location, current HTTP location, search string, time of the access, browser’s time, any searches made on the applicable website, and other statistics” in order to “analyze Log Data from different websites and combine it with other non Personally Identifiable Information to produce the Reports that are made available on the Quantcast.com Site, to enable web publishers and advertisers to deliver audience segments that are appropriate for their products or services.
(b)The mc cookie set by Quantserve is related to advertising, and may track your behaviour on the VisionMobile website.
PREF Google cookie This cookie remembers users basic search preferences. The Google “PREF cookie” is used to remember our users’ basic preferences, such as the fact that a user wants search results in English, no more than 10 results on a given page etc. Expiry is set to 2038 in order to preserve user preference information. See here for more information.
Please enter your email to receive weekly updates from the VisionMobile blog
I also want to subscribe to the monthly newsletter, with updates on VisionMobile news and research (you will receive a separate email for this list, please subscribe to both to receive the newsletter and blog updates)