Transcript
Page 1: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 1

Page 2: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 2

VisionMobile Market-How Application Environments

Andreas Constantinou, Ph.D. Research Director

August 2008

Page 3: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 3

Looks confusing?

WebKit core

Page 4: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 4

What is an Application Environment?

Page 5: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 5

It is a software platform to:

Develop + Deploy + Execute + Deliver mobile handset applications

What is an App Environment?

Page 6: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 6

What this means:

Develop + Deploy + Execute + Deliver

What is an App Environment?

Open Simplify Manage Support

Market Distribute Install Monetise

Integrate Interoperate

Web Widgets Synchronise Manage OTA

Page 7: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 7

So far the focus has been on:

Develop + Deploy + Execute + Deliver

(focus in bold)

Where are we today ?

Open Simplify Manage Support

Market Distribute Install Monetise

Integrate Interoperate

Web Widgets Synchronise Manage OTA

Page 8: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 8

Who’s who and who’s what

Page 9: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 9

A diversity of AEs exists..

WebKit core

Page 10: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 10

Two key criteria for AEs

designed for 2nd parties vs (OEMs, MNOs, and partners)

designed for 3rd parties (any developer)

-  written by an inner circle of trusted parties -  familiar with C/C++ and proprietary toolchains -  with access to expensive tools and NDA’ed SDKs -  resulting in 100s of applications

-  written by anyone -  with basic (e.g. JavaScript) development skills -  with low cost access to tools and SDKs -  resulting in millions of applications

for core applications vs (dialler, idle screen, main menu, inbox, ..)

for downloadable applications (games, utilities, messaging, VoIP)

- embedded into the phone - used most often and - easily accessible from main menu and hard keys

-  usually downloaded -  used least often -  accessible through deep menus

Page 11: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 11

Order from chaos for 2nd parties for 3rd parties

Cor

e ap

ps

Dow

nloa

dabl

e ap

ps

WebKit core

Page 12: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 12

Where are AEs moving to?

Page 13: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 13

Application Environments are moving towards:

Develop + Deploy + Execute + Deliver

Where are AEs moving to?

Open Simplify Manage Support

Market Distribute Install Monetise

Integrate Interoperate

Web Widgets Synchronise Manage OTA

Page 14: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 14

-  Extend more parts of phone development to 3rd parties by exposing more APIs and richer tools

-  Simplify discoverability of 3rd party applications through direct links from the active idle screen (e.g. idle screen widgets)

-  Simplify development environment with languages and tools familiar to web developers and scripters

-  Integrate more deeply with the handset events and user data allow the application to react to incoming calls and to tap into contacts, call logs and messages

-  Streamline go-to-market channels lower the barriers to applications reaching the market (e.g. BREW delivery system, Apple AppStore)

Five clear trends

Page 15: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 23

Addendum

Behind the Android phenomenon

Page 16: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 24

Behind the Android phenomenon - The model Modular platform for mobile phones

- Every application (incl. idle screen, dialer, main menu) is a Web 2.0 citizen.

-  Designed to facilitate connected application development, both intra and inter-device.

- Declarative XML UI framework + inheritance help rapidly develop the UI for new applications.

- OEM-friendly license

-  source code to be released under Apache 2 (non-copyleft license); modify code, ship, retain IPR

- zero royalty to use the Android OS (purported but not confirmed)

- Developer-friendly

-  free development and debugging tools, unlike all other platforms.

-  Java SE-like platform deeply integrated with OS; a departure from Linux development

- With the right industry ingredients

-  OHA members were hand-picked as the right technology and commercial ingredients to take

Android to market (contrary to LiMo). :HTC is crucial with know-how from maturing Windows

Mobile

Page 17: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 25

Behind the Android phenomenon

With dark sides, too -  “Build it and they will come” mentality does not work in mobile Handset production economy is controlled by a handful of handset OEMs and network operators.

- Only a platform, not a market-ready OS Requires 3rd party component sourcing, integration, optimisation and certification

There is no provision for ‘baking in’ operator requirements which adds 6 months to production cycle

-  Leaves out the hardest part of protocol & hardware integration Stabilisation of an OS is a matter of testing 1,000s of corner cases with telephony stack integration

-  Not 100% royalty free and not 100% under APL due to IPR encumbered code

-  All warranties/indemnities are disclaimed under APL2.

-  Poor documentation and samples, APIs and lack of expert support

Page 18: Application Environments: Order from Chaos

Copyright VisionMobile 2008 Page 26

Thank you !

Contact: [email protected]

Further reading: Mobile Megatrends

www.visionmobile.com/research


Top Related