Contents

Page

The Big Question: 4 - 5Webite or client application?Symbian C++ 6 - 7Qt on Symbian 8 - 9Open C and Open C++ 10 - 11Python 12 - 13Widgets 14 - 15Web Browser 16 - 17Java MEFlash Lite 20- 21Symbian Books 22- 23

The Hitch Hiker’s Guide to the Runtime Space

18- 19

A web application can use a login page,but asking users to type in details using anumeric keypad is undesirable and addsto the time taken to access your service. A client application, however, can store

local conguration and details and offer

one-click login.

How important is speed to your usecase?

To use a web application, a user musttypically launch a browser, access themenu and select a bookmark (or enter

URL). Each of these stages takes time andthen the speed and latency of the network

determines how long the user has to wait. A client application, on the other hand,launches quickly and is usually accessible

from a menu or idle-screen shortcut. Oncerunning, applications also perform much

more quickly than websites on comparabletasks.

The BIG Question:

Website or client application?

How technically sophisticated are your users?

Your target audience might not be as

tech-savvy and fearless as you are. Forsome users, the process of downloading,installing and conguring an application

can be a daunting prospect. Resolving this

issue is a trade-off between easier rst

time access (i.e., through a website) andsuperior user experience in repeat use (i.e.,using a client application).

Does your application or service need toknow who your user is? Does it need tomaintain user history or store personalpreferences?

Mobile network operators are increasingly

preventing third parties from receivingany identifying information about the user

in HTTP requests. Handset numbers areblocked and IP addresses are removed

from the network operator’s proxy server.

You may have discovered that the RuntimeSpace is not only mind-bogglingly big

and bewildering, but also that most of

the things that happen in it are deeplyintertwined with the user experience.

While all questions of the runtime features,

the pros and cons, the cost, the requireddeveloper skills and the market share areto be resolved, one big question stands

out: ‘website or client application?’ That

is, should you use a website or a clientapplication to deliver your services to theend user?

A growing number of entrants to themobile space see the option of buildinga mobile-specic website as a cheaperand more exible alternative to developing

a client application. However, there areadvantages and disadvantages to both

depending on the details of your serviceand, as always, there is a trade-offbetween quality, functionality, speed of

development and cost.

Here are some fundamental argumentsthat are worth bearing in mind before you

stick your thumb out into the Runtime

Space and hitch a lift.

The Hitch Hiker’s Guide to the Runtime Space

Do you use third-party content in your service?

It is more challenging to include third-party

elements (for example, ads from an ad

serving aggregator) in an application thanin a website.

Do you regularly change the look-and-feel of your service?

As soon as you change the les on yourweb server, every user of your website

sees the changes.In contrast, updates to an application

must rst be delivered to the handset, and

then the user must accept the installation.Ultimately, you cannot guarantee that allyour application users will be using themost recent version.

Do you need your users to be able toaccess your application’s services

ofine?

If you do, you need to use a client

application.

Now you’re wondering, ‘Where shouldI start?’

Getting started building mobileapplications is no easy task.

The rst thing to do is to decide which of

the many runtime environments is the best

t for your product. This Guide is intendedto help you make an informed decision,even if you are completely new to mobiledevelopment. We look at some of the most

common environments available on mobiledevices and provide an overview on key

metrics such as market share, functionalityand development effort. We also providean objective analysis of the pros and consof each, and try to dispel some common

myths.The Guide is not meant to be anexhaustive technical analysis – thoughwe have included links to examples

and further resources for each runtime

environment – but it will give you a good

indication of what you should investigate

in more detail.So, hold on tight and have a stunning ride!