Runtimes Roadmap Q3 2009 v0.4

8/14/2019 Runtimes Roadmap Q3 2009 v0.4

1/19

Copyright 2009 Symbian Foundation.

RuntimesTechnology Domain Roadmap &

Strategy

A run-time is a collection of software designed to support the execution ofcomputer programs. Some services of the run-time are accessible to developersthrough an application programming interface (API); but some services (such astask scheduling and resource management) may be inaccessible.

DRAFTFordiscussionwithFeatureandRoadmapCouncil


2/19

Strategy in a Nutshell


Qt

UniversalWebRuntime

Orbit

PIPS / POSIX

Symbian Kernal & Middleware

UniversalInstaller

Applications

Runtimes

Runtime PluginFW

Core Symbian(CompatibilityManaged)

OptionalSymbian(Community Managed)

MobilityAP

I


3/19


Runtimes- Overview

Definition:The Runtimes Technology Domain encompasses the native and non-native technologiesdirectly related to application execution, application services and application lifecyclemanagement on the Symbian platform. It does not include the tools required to authorand debug applications, which are covered in a separate document.

Key Drivers:Rapid growth in the adoption of mobile applications and services has created anopportunity for device creators, operators and service providers to diversify and growtheir revenue streams. Runtimes are the key enabling technology behind theseapplications and services and are the signature feature of open operating systems.

Primary Stakeholders:Runtimes are an enabler that allow device creators, operators and end-users tocustomise the applications on mobile handsets. Developers typically write applicationsusing a tool-chain targeted towards a specific runtime and sell the application eitherdirectly or through a third-party application store.


4/19


Runtimes- Packages

Current Packages:Applications: Java, Web UIsMiddleware: App Installation, Generic App Support, Service API, Service API FW, Web,Web Services

Operating System:XML Services

Upcoming ChangesThe System model and packages in the Apps and UI layer will be radically changed with the planned introductionof the Qt application framework, Orbit UI framework and re-worked DirectUI applications. These changes willresult in the creation of a large number of new packages and deprecation of a significant number of currentpackages.


5/19


Stakeholder Needs Slide 1 of 3

Device CreatorsDevice creators require runtimes to have the capability and performance

to provide seamless and engaging applications to end-users and network

operators. They also want efficient runtimes that offer good compatibility

to allow applications to be used across a range of devices at difference price-

points. Device makers need to balance adoption, which provides a wide

range of ready-made solutions with the ability to extend runtimes

independently to their strategic advantage. Finally, device makes want runtimesthat are simple to productise and well integrated.

Network OperatorsNetwork operators require runtimes to have the capability and

performance to allow them to provide innovative services to end-users that

make use of their network and billing assets. They also require runtimes to besecure protect their customers, revenues and network assets and

compatible to allow applications to be used across a range of devices.

Another key consideration for network operators is balancing adoption, which

provides a wide range of ready-made solutions with the ability to use and

extend runtimes independently to their strategic advantage.


6/19



Application DevelopersApplication Developers require runtimes to have the capabilities and

performance to allow them to write compelling applications that making use

of the latest device capabilities. They also require runtimes to be simple, using

familiar languages and easy-to-learn tools, and extensible to allow them to

innovate. A large market is essential for the success of applications, so

developers like to work with runtimes that have high adoption from device

creators, operators and end-users, or runtimes that are compatible acrossdevices.

End UsersEnd-users dont care about runtimes, but they do want cool applications with

great performance that make use of all the capabilities on their device.

They dont want to know about technology, so they value the simplicitythrough ease of use and compatibility of runtimes between devices. They

want a huge choice of applications, which they get if they choose a phone with a

runtime that has been well adopted by developers, device makers and

operators. Finally, although end-users dont want to be aware ofsecurity, they

value the protection of their private data and hard-earned cash.


7/19Copyright 2009 Symbian Foundation.


DeviceCreators

NetworkOperators

ApplicationDevelopers

EndUsers

Capability

Performance

Efficiency

Compatibility

Security

Simplicity Adoption

Extensibility



General Objectives

These are common to the entire platform and included: ease of productisation, userexperice competitiveness, battery life, performance improvement, open source and free.

CapabilityExpose as much handset functionality as practical to allow creation of competitive

applications without the need to extend the runtimes.

PerformanceEnable smooth, responsive and great looking applications, even for demanding use-

cases and when the user is running applications and services concurrently.

Adoption

Symbian runtimes should be widely adopted by device makers, operators, developersand service providers which in-turn will stimulate adoption by end-users.

CompatibilityUnify runtimes where there is industry-wide fragmentation to enable compatibility with a

large number of applications.

Objectives Slide 1 of 2



Objectives Slide 2 of 2SimplicitySimple to develop, debug, profile and test applications and straight-forward to monetize

applications. On-device application management should be simple and seamless.

SecurityProvide robust mechanisms to allow awareness and protection from malicious

applications where there is potential for exploitation of end-users or network assets.

EfficiencyConsume the minimum practical resources to allow the platform to be deployed to

lower-cost handsets and to enable high levels of concurrency.

ExtensibilityAllow the community to easily add and extend runtimes to meet their near term

strategic objectives, and with the opportunity to contribute back to the platform.



Competitive Landscape

Actively promoted runtimes from the iPhone 3.0, Android 1.5,Windows Mobile 6.5, Palm WebOS & RIM have been included inthis analysis

Symbian isbetter than the

industry average

Symbian isworse than the

industry average

GeneralObjectives

Capability

Perfomance

Adoption

Compatibility

Simplicity

Security

Efficiency

Extensability



Platform Challenges Slide 1 of 4

CapabilityRuntimes live and die by the capabilitiesthey expose and the level of abstractionthey provide to developers throughpublic APIs. Native runtimes have astrong advantage in exposingcapabilities, but can be hard work due tolack of abstraction

Perceived capability is influenced by:

API mapping to core nativefunctionality Abstraction layers and helper functions Language syntax and semantics

Initiatives:

Improved abstraction through the adoption of Qt as the primary runtime Orbit & Qt Mobility APIs to expose mobile specific capabilities through Qt Adoption of HTML5 to improve Web Runtime Capabilities Extension of JavaScript libraries

Opportunity



Efficiency &

PerformanceEfficiency and performance aresomewhat related. The Symbian kernelis already well optimised for mobiledevices, so runtime implementationsshould be able to offer superiorperformance for a specific hardwarebaseline and offer superior scalability tolower-cost hardware.

Efficiency & Performance are influencedby a number of factors:

Platform & Runtime architecture

Efficiency of implementation Ability to utilise hardware accelerationInitiatives:

Have ongoing community profiling initiatives to ensure optimum software performance Enable all runtimes to take full advantage of hardware acceleration when present Create a community benchmarking initiative based on reference hardware Adopt a JIT JavaScript interpreter as soon as practically possible

Opportunities




Simplicity & AdoptionThe majority of competing platforms havesimpler runtimes. This is stronglycorrelated with developer adoption and theoverall attractiveness of the platform tostakeholders with an interest inapplications and services.

Runtime simplicity is influenced by:

Number of runtimes supported Programming language Documentation & Support Tool-chain & route-to-market

Initiatives:

Focus on a smaller number of core runtimes Introduce Qt as the new simplified signature runtime Improve and promote web-runtimes for simple applications Provide industry leading community driven documentation & support Provide industry leading tool-chain and direct access to application stores

CommunityEngagement Initiatives

Threat




Compatibility &ExtensibilityRuntime compatibility is an ideal that hasyet to be successfully realised.Compatibility is typically achieved througha lowest-common denominator approachand therefore unattractive. Symbian

foundation is uniquely positioned to take amore inclusive approach through platformextensibility.

Compatibility is influenced by:

Runtime availability & pervasiveness Fragmentation of capabilities

Adoption & trendsInitiatives:

Aim to have 90% of all mobile web-widgets supported in Symbian^5. Drive inclusion of community supported plug-in runtimes starting with Symbian^J Expand PIPS and develop a framework to allow easily extension or new runtimes*

Opportunity

* Plug-in runtimes be made available through theSymbian foundation but will not be actively promotedas core runtimes.

Threat



15/19

Strategy in a Nutshell


Qt

UniversalWeb

Runtime

Orbit

PIPS / POSIX

Symbian Kernal & Middleware

UniversalInstaller

Applications

Runtimes

Runtime PluginFW

Core Symbian(CompatibilityManaged)

OptionalSymbian(Community Managed)

MobilityAP

I



Roadmap Scoped ItemsSymbian^2

Includinghome screenwidgets


17/19



Feature Target Objectives Contributor

Qt 4.6 for Symbian option (High Risk) Simplicity Nokia

Adobe Flash (EULA) Compatibility Adobe

Symbian^J runtime for Java programs Compatibility NokiaJ9 JVM (R&D) Compatibility IBM

Universal Software Installer Extensibility Nokia


18/19



Feature Target Objectives Contributor

Adopt Qt 4.6 as the primary runtime Simplicity Nokia

Orbit Extensions to Qt 4.6 Capability Nokia

Qt Mobility Extensions (Phase 1) Capability Nokia

Direct UI Webkit Browser (HTML5) Capability Nokia

Common Web Runtime Capability & Compatibility Nokia


19/19

Copyright 2009 Symbian Foundation

Items for Contribution Solicitation

Feature Target Objectives

Symbian^J MIDP 3.0 support Capability

JIT JavaScript Interpreter Performance & Efficiency

Qt Performance Test Suite Performance & Efficiency

WRT Performance Test Suite Performance & Efficiency

Python Scripting plug-in Compatibility

Ruby Scripting plug-in Compatibility

Bondi Widget support Compatibility

BAE / JIL Widget support Compatibility

Runtimes Roadmap Q3 2009 v0.4

Documents

Transcript of Runtimes Roadmap Q3 2009 v0.4