Escolar Documentos
Profissional Documentos
Cultura Documentos
Change history
14 February 2011 1.0 Initial document release
Updated to include information on Series 40
3 March 2011 1.1
On-Device Debugger
Smartphones, powered by Symbian; the Maemo platform; and MeeGo, offer developers the
ability to create mobile applications using the Qt framework and web technology. For mobile
phones, powered by the Series 40 platform, developers have access to web and Java™
technology. These development technology options offer developers effective and efficient
ways to create apps for consumers, globally.
This document looks at all aspects of the offering made by Nokia to Java developers, from the
Java technology support in Series 40 through tools and development processes to distributing
apps. A showcase of Java applications is provided as well, along with an introduction to the
full range of resources and services offered by Forum Nokia
The use of the Java language for application development opens up access to five hundred
million Nokia device owners worldwide. This is an unprecedented opportunity to build a
mobile applications business: This guide will show you how.
Implementations of Java ME are defined by configurations, which determine the basic set of libraries and virtual-
machine features offered, and a profile, which is a set of APIs that provide a complete Java application
environment. In addition, APIs defined by a Java Specification Request (JSR), created through the Java
Community Process, may be implemented to enable specific tasks, such as accessing contact details or rendering
3D graphics.
Nokia devices implement the Connected Limited Device Configuration (CLDC) 1.1 (JSR-139) and the Mobile
Information Device Profile (MIDP) (JSR-118), with up to 12 JSRs providing additional APIs. In addition, the Nokia
UI API is provided to provide developers with access to enhanced UI features, such as those for gesture
recognition and UI animation for the Touch and Type UI of Series 40 6th Edition, Feature Pack 1.
Java ME offers developers the familiarity of the Java language and the ability to use their skills — possibly
portions of desktop applications also — to create mobile applications. The range of APIs offered on Nokia
For developers who have created Java applications for the desktop, Java ME provides a familiar environment for
mobile apps development. Not only is the language familiar, but much of the toolset is also, with support for
development provided by Nokia for the NetBeans and Eclipse IDEs.
Java ME on Nokia devices opens up wide horizons to Java developers: The ability to create applications for
consumers and businesses alike and, as will be discussed later, take those applications to market through
effective distribution channels.
A result of the platform approach is that there are some 500 million Series 40
devices in use in the world today that developers can target with Java applications.
It’s worth noting that Series 40 devices will continue to be a significant part of the device portfolio offered
by Nokia.
The characteristics of the Series 40 platform are described in full in Chapter 2, ‘The Series 40 platform’.
When it comes to coding, Nokia provides an SDK for each Edition and Feature Pack
of the Series 40 platform. Each of the SDKs includes documentation, the APIs, and
an emulator. The emulator, as shown in Figure 2, enables applications under
development to be run on a PC, mimicking the way they would run on a physical
device. This simplifies testing and debugging of applications. Furthermore, the
SDKs are designed to integrate with the NetBeans and Eclipse IDEs, meaning the
majority of developers will be able to create Series 40 applications using the tools
with which they are already familiar.
Once an application has been written and tested, Nokia offers developers Ovi Store
as a quick and convenient route to market. After signing up (for the princely sum of
1 euro) developers submit applications that, if they pass the QA process, are signed
and made available in Ovi Store. This channel gives developers access to
approaching 500 million consumers worldwide.
The approach to development, tools available, and use of Ovi Store to distribute
Figure 2: The Series 40
Java applications is explored fully in Chapter3, ‘Creating and distributing
SDK emulator running a
Series 40 apps’.
MIDlet.
It’s worth noting that you have the opportunity to deliver Java applications to
Symbian devices also. More details on this option can be found by visiting the Forum Nokia website or
contacting your local Forum Nokia representative.
In this chapter the key characteristics of the Series 40 platform are described. This covers the
platform architecture, the UI, and supported Java APIs. There is a brief discussion of the mobile
phone models based on the Series 40 platform too.
This platform approach enables Nokia to offer innovations in a cost effective manner to the widest
audience globally.
The Series 40 platform architecture consists of the hardware (the device hardware, CPU, memory, and so forth);
the operating system, which provides fundamental services to the platform; and the Series 40 platform services
that consist of:
Media applications such as image viewer, camera, music player, voice recorder, and FM radio.
Personal information manager (PIM) with calendar, tasks, and contacts applications.
Series 40 Java technology services — The Java technology implemented within the platform.
Finally there is the UI that provides a common set of UI components with defined behaviour. These components
can be used in a range of different screen orientations and resolutions, with user interaction provided through a
keyboard or a combination of keyboard and touch interface.
Changes in Edition occur when there is a major change in the underlying technology of the platform, such as the
introduction of MIDP 2.1 support in Series 40 5th Edition.
Feature packs provide for an incremental change that builds on the features of an edition, such as the
introduction of the Touch and Type UI in Series 40 6th Edition, Feature Pack 1.
Lite versions of an edition provide for the creation of more cost effective phone models and generally provide a
subset of the edition and feature pack’s APIs, often with a lower resolution screen. For example, when compared
to Series 40 6th Edition, devices based on the Lite version offer 128 x 160-pixel displays and lack the Location
API for J2ME™ (JSR-179) among others.
Nokia UI API 1.1b provides additional APIs for creating and controlling Touch and Type UI interactions.
Context-sensitive icons.
Figure 4: The Series 40 UI style provides users with a simple, intuitive way to interact with their
device’s functionality.
Gesture API, to capture taps, long presses, repeated long presses, dragging,
dropping, and flicking gestures. Figure 5: The Touch and
Type UI brings a new
FrameAnimator API that calculates motion for kinetic scrolling and dimension to the
linear animations. Series 40 UI.
It’s worth noting that existing Java applications designed for QVGA screens will work on Series 40 6th Edition,
Feature Pack 1 devices. The only change that may be required is to modify controls to enable their comfortable
use with a thumb.
To these basic specifications a number of JSRs and the Nokia UI API have been added.
Early versions of the platform provided support for the Java™ Technology for the Wireless Industry (JTWI)
(JSR-185) specification. Series 40 5th Edition and later (but excluding Lite implementations) support the Mobile
Service Architecture (JSR-248), which is designed to reduce Java fragmentation by defining a consistent set of
This section provides a detailed description of the Java APIs available in the Series 40 platform, along with
information on the versions of the platform that support these APIs.
Series 40 2nd Edition and later provide support for v1.0 (excluding OBEX support).
Availability Series 40 5th Edition and later provide support for v1.1 (including OBEX support).
Not provided on ‘Lite’ devices and other devices that lack Bluetooth hardware.
Series 40 2nd Edition with sound playback support for MIDI and tone sound files.
Series 40 3rd Edition and later provide sound, video, and image rendering.
Availability
Series 40 5th Edition, Feature Pack 1 and later provide for video-progressive playback and
audio-progressive upload, as well as audio mixing.
Series 40 3rd Edition, Feature Pack 1 and Series 40 3rd Edition, Feature Pack 2 provide
support for the XML parsing package only.
Availability
Series 40 5th Edition and later provide support for the XML parsing package and
JAX-RPC subset.
Series 40 3rd Edition, Feature Pack 2 provides support for the SATSA-APDU package only.
Series 40 5th Edition and later provides support for SATSA-APDU and SATSA-CRYPTO
Availability
optional packages.
Not provided in Lite devices.
Content Handler API (JSR-211) enables MIDlets to be specified as the content handlers for
Features one or more specific file types, thereby enabling Java applications to handle multimedia
and web content seamlessly.
Series 40 5th Edition, Feature Pack 1 and later (as well as selected Series 40 3rd Edition
Availability devices from the Nokia 6280 WCDMA/EDGE imaging phone).
Not provided in Lite devices.
Series 40 5th Edition and later provides support for 3D audio and music support.
Series 40 5th Edition, Feature Pack 1 and later provide additional support for audio mixing,
including mixing of 3D audio.
Availability
Series 40 6th Edition, Feature Pack 1 and later provide additional support for
Camera features.
Not provided in Lite devices.
Series 40 1st Edition and later provide support for Nokia UI 1.0.
Availability Series 40 5th Edition and later provide support for Nokia UI 1.1.
Series 40 6th Edition, Feature Pack 1 and later provide support for Nokia UI 1.1b.
Series 40 2nd
Series 40 6th
Series 40 6th
Series 40 5th
Series 40 5th
Series 40 3rd
Series 40 3rd
Series 40 3rd
Series 40 1st
Edition, FP 2
Edition, FP 1
Edition, FP 1
Edition, FP 1
Edition
Edition
Edition
Edition
Edition
CLDC support 1.0 1.1 1.1 1.1 1.1 1.1 1.1 1.1 1.1
MIDP support 1.0 2.0 2.0 2.0 2.0 2.1 2.1 2.1 2.1
Nokia UI API 1.0 1.0 1.0 1.0 1.0 1.1 1.1 1.1 v1.1b
PDA Optional PIM and PIM and PIM and PIM and PIM and PIM and PIM and
Packages for the FC FC FC FC FC FC FC
J2ME™ Platform packages packages packages packages packages packages packages
(JSR-75)
Java™ APIs for v1.0, v1.0, v1.0, v1.0, v1.1 v1.1* v1.1 v1.1
Bluetooth (JSR-82) excluding excluding excluding excluding
OBEX OBEX OBEX OBEX
Wireless X X X X X X X* X
Messaging API
(JSR-120)
Mobile Media API Sound Sound, Sound, Sound, Sound, Sound, Sound, Sound,
(JSR-135) playback video, video, video, video, video, video, video,
and and and and and and and
image image image image image image image
rendering rendering rendering rendering rendering rendering rendering
J2ME™ Web XML XML X* X* X X
Services parsing parsing
Specification package package
(JSR-172)
Security and Trust SATSA- SATSA- SATSA- SATSA- SATSA-
Services API for APDU APDU and APDU and APDU and APDU and
J2ME™ (JSR-177) package SATSA- SATSA- SATSA- SATSA-
CRYPTO CRYPTO CRYPTO CRYPTO
packages* packages packages packages
Location API for X* X
J2ME™ (JSR-179)
Mobile 3D X X X X X* X X
Graphics API for
J2ME™ (JSR-184)
Wireless X X X X X (with X (with
Messaging API 2.0 CBS) CBS)
(JSR-205)
Content Handler X* X X
API (JSR-211)
Scalable 2D Vector X X X* X* X* X
Graphics API for
J2ME™ (JSR-226)
Series 40 6th
Series 40 6th
Series 40 5th
Series 40 5th
Series 40 3rd
Series 40 3rd
Series 40 3rd
Series 40 1st
Edition, FP 2
Edition, FP 1
Edition, FP 1
Edition, FP 1
Edition
Edition
Edition
Edition
Edition
Advanced 3D audio 3D audio 3D audio 3D audio,
Multimedia and and and camera,
Supplements music* music* music and
(JSR-234) music
Mobile Service subset* subset
Architecture
(JSR-248)
Table 1: A summary of the Java technology supported by the Series 40 platform is provided.
* May not be present in devices based on the Lite versions of the respective platforms.
Figure 6: Examples of Series 40 devices showing the varied form factors the platform supports.
The range of Series 40 devices is extensive. To see the range of devices, visit the Device Specifications page
(nokia.ly/hMqCz3) on the Forum Nokia website.
Once a design has been created the application needs coding. In general good Java coding
practices will serve developers well for Series 40 apps.
A good development technology is measured by the ease of use and robust performance of its
development tools. Many Java developers are already familiar with either NetBeans or Eclipse
and the good news is that Nokia leverages these tools to provide a complete environment for
Series 40 applications development.
There are some 500 million Series 40 devices in use around the world that developers can
create Java applications for. The majority of these devices are able to access Ovi Store directly,
either using a device client or xhtml based browsing, or indirectly using the web based Ovi
Store interface on a PC.
This chapter discusses all these aspects of apps for Series 40 devices.
3.1 Prototyping
A useful technique to use as part of the design process is prototyping. By prototyping applications the UI and
basic interaction can be refined and confirmed with
users before the expense of coding is undertaken. To
enable prototypes to be built for Series 40 devices
Nokia provides Flowella (nokia.ly/Flowella). This tool
uses images of the application’s screens — which can
be scanned or photographed hand drawn sketches, or
wireframes and realistic screens created with a PC
drawing package — then enables interaction areas
and the connections triggered by these areas to other
screens to be defined, as shown in Figure 7. The result
Figure 7: Flowella enables the rapid creation of
can be exported to a Flash Lite application and run on prototypes from mocked-up screen images.
The method of interaction through a navipad or a combination of keypad and touch screen.
Simplification of user interaction by, for example, avoiding unnecessary security prompts.
Using the high-level controls applications take on the look-and-feel of the Series 40 platform. This approach has
the benefit of enabling third-party applications that look and feel the same as the standard device applications
the user is familiar with. Elements of all applications, such as settings, and many personal and business
applications will be served well by use of the high-level UI controls.
For games and any application that needs to provide a graphically rich interface, the Canvas may provide the
best implementation approach. Using the Canvas you have precise control over the content of the UI and are not
limited to the standard UI components.
In addition to the standard MIDP APIs for UI development the Nokia UI API is available also. Useful features of
the API include capturing gestures and controlling animation for the Touch and Type UI, a text editor, and the
ability to control custom font size for text drawn on the canvas.
In addition, another option for creating rich UIs is to use SVG in conjunction with the Scalable 2D Vector Graphics
API for J2ME™ (JSR--226).
Whether development starts with the smallest targeted screen size or the largest will depend on the graphic
content of the application. Developers of graphic-intensive applications, such as games, are advised to start with
the largest screen and then optimise the content to smaller screens. This approach is suggested because
graphics will probably use the largest amount of available storage for the MIDlet, so if the application works on
the largest screen, it should still do so for smaller screens, where the graphics size and memory requirements
are reduced.
Developers of more data- and function-oriented applications should start with the smallest targeted screen size
and then work toward the bigger screen sizes. This approach is suggested because it’s far easier to expand an
interface design into larger-screen real estate than to try to compress a design to a smaller screen.
Another aspect of flexible, adaptable applications is the avoidance of hard coding. Where possible, developers
should consider querying screen resolution and facilities such as automatic double buffering on initialisation
within the MIDlet, rather than hard-coding screen dimensions or capabilities.
The [5] key, Send key, or middle softkey on a standard ITU-T keyboard.
The ninth key on the third row or the space bar on a full keyboard.
// To use the Gesture API, the package to gain access to the classes and interfaces needs
// to be imported
Import com.nokia.mid.ui.gestures
GestureRegistrationManager.setListener(this, this);
// Now a GestureInteractiveZone where the touch events will be generated by the user
// is defined as a rectangle half the width and height of the screen in the top left
// of the screen
GestureInteractiveZone giz =
new GestureInteractiveZone( GestureInteractiveZone.GESTURE_ALL );
giz.setRectangle(0, 0, getWidth()/2, getHeight()/2);
Frame Animator API — This API calculates motion interpolation for kinetic scrolling and linear animations
that can be used in response to drag and flick gestures. A typical usage example would be in enabling a
user to traverse a long list using a flick gesture. The Frame Animator API doesn’t draw the UI updates for
an animation; such animation should be created using the standard LCDUI methods for
rendering graphics.
To use the FrameAnimator API to gain the information to control an animation, as shown in
Example 2, involves:
Updating the coordinates of the UI component that is to be animated in the Class that implements
the FrameAnimatorListener update.
public void animate(FrameAnimator animator, int x, int y, short delta, short deltaX,
short deltaY, boolean lastFrame) {
//Do something with the values
}
editable form items, such as DateField, TextField, and Gauge to be set so they provide the inline
or sub-state screen editing style
CustomItem instance to be set so it will receive touch events without having to be set as the current
TextEditor API — This is a floating text editing component that is used on top of the LCDUI Canvas.
TextEditor is similar to the standard LCDUI text editing components, TextField and TextBox. However,
unlike the standard components the client application defines the colours for the editor and draws
Adding colours.
You should be aware that there are some variations in the implementation of the Series 40 platform on specific
devices. These variations may be because of implementation anomalies or because a particular device uses
technology beyond the scope of the platform. These issues are documented in the Forum Nokia Knowledge Base
(nokia.ly/egBZed), which is housed in the Forum Nokia Wiki.
3.3.1 SDKs
To assist in the creation of Java applications, Forum Nokia makes available the Series 40 platform SDKs. These
SDKs contain MIDP APIs, classes, documentation, and sample applications, along with an emulator, as shown in
Figure 2 on page 6. The emulator, in addition to
enabling an application to be run and tested on a PC,
provides diagnostic information, including network
traffic and memory usage. Other emulator features
include security, the ability to run multiple instances,
and support for communications, XHTML and TCP
stacks, and multiple languages. More recent SDKs
provide tools for route simulation, see Figure 9to help
in the development of location-based apps.
SDKs are available for all editions and feature packs of Figure 9: The SDK’s route editor makes testing location
based apps easy.
the Series 40 platform and can be obtained via the
Tools tab (nokia.ly/i6ZqJw) in the Forum Nokia website’s Develop Java section.
Developers choosing NetBeans are able to take full advantage of the features of NetBeans with Java ME support.
NetBeans Java ME provides developers with a rich development environment offering the ability to specify
application-flow and UI component layouts visually using drag-and-drop techniques. In addition, NetBeans Java
ME offers tools to support the use of Scalable Vector Graphics Tiny (SVGT) in creating graphically rich UIs,
eliminating the overhead of low-level graphics coding.
Developers familiar with the Eclipse IDE may want to use Pulsar, which provides a set of tools for creating,
testing, and packaging MIDlets for mobile devices.
Nokia tools can be used in conjunction with other IDEs; however, developers will not be able to benefit from the
efficiencies afforded by the integration provided with the supported IDEs.
The tools device client provides features to capture user level trace also, without the need for an IDE.
The Series 40 On-device Debugger is currently available as a beta release on Forum Nokia (nokia.ly/S40ODD) and
works with most of the most recent Series 40 devices.
For paid apps Ovi Store offers options for credit card and operator billing. Credit
card billing is available in over 170 countries, while operator billing is provided in
32 countries (through 103 operators). The significance of operator billing is that,
where it’s available, the number of applications purchased increases dramatically.
Figure 11: The Ovi Store Nokia is also rolling out an in-apps purchasing mechanism that will enable, for
client on a Nokia X3-01
Touch and Type example, consumers to buy an application from within a demo version or purchase
additional game levels — without having to visit Ovi Store first. In addition, for
developers who wish to create advertising funded applications, an in-app advertising option is being rolled out
by Nokia too.
There is no need to sign or obtain Java Verified for your app, as this is done by Nokia as part of the QA process.
You do, however, need to ensure your app will pass the Java Verified tests or it will be returned from the Ovi
Store QA process and will have to be resubmitted.
After you submit an app it passes through the QA process. This process checks that the information supplied is
complete and that the application passes basic suitability criteria, for example, if your application offers some
form of gambling feature it may not be legal in some countries. It’s important to note that Nokia doesn’t reject
applications because they may compete with something developed by Nokia. The only exception is where the
app contains an embedded payment option that would bypass Ovi Store.
It may seem that credit card billing offers the best opportunity for revenue generation, as a higher percentage of
the application price is returned. This may, however, not be the case. There are two factors that usually make
operator billing the most lucrative source of revenue:
Credit card ownership — every phone owner has an operator, not every phone owner has a credit card:
Credit cards are far from a universal method of payment. It might be expected that there will be low levels
of credit card ownership in emerging markets, but it’s true of some developed markets too. For example,
in Germany only 30% of the population has a credit card[1]. Also, younger consumers may not have access
to a credit card, which could affect those applications and services directed at this demographic.
Operator billing — is simple and trusted. The user doesn’t have to provide any additional information to
use operator billing, making a purchase much easier, and in general users trust their operator to bill
them correctly.
As a result, revenues from operator billing can exceed those from credit cards by a factor of ten; for every dollar
earned on credit card sales, ten could come from operator billing.
This may still present challenges if an application or service involves fixed costs, such as royalties for music. In
this case the best advice is to price the application based on operator billing sales.
To assist with marketing on your own web properties Ovi Store provides the Promotional Banner Creator tool
(promotions.ovi.com/omt/). This tool enables the quick and easy creation of a web banner that can be used to
advertise an application’s availability in the Ovi Store. The banner provides a link to the application’s page on Ovi
Store too.
4.1 Shazam
Music is engrained into the human psyche. People love to listen to their favourite
music anytime and anywhere. Series 40 devices offer users this ability and Java
technology enables developers to put music at the heart of their applications.
One of the pleasures of music is the ability to discover new songs and artists. There
is, however, nothing more frustrating that hearing something you like and being
unable to find out the song title and artist. This is where Shazam comes in.
When a new song is heard, the user captures a fragment of the song using Shazam.
The app then uploads the music fragment and compares it to a database of over
eight million tracks. Once this is done, the application then provides the user with
details of the music, such as artist and album. Shazam enables users to share Figure 13: Shazam
enables its users to
music, get recommendations for similar music, and view charts among discover music
other features.
Snaptu provides a good example of how a third party developer has leveraged this
feature of Series 40. The Snaptu app, see Figure 14, enables users to quickly and
efficiently connect with their many social networks such as Twitter, Facebook,
Flickr, and Picasa as well as information sources such as news and weather. In
addition, Simon Davies, European MD for Snaptu, sees the Java technology version
as an ideal way to address emerging economies, saying they are ‘going to be a
very lucrative market. A lot of investors in the West don't understand the content Figure 14: Snaptu enables
users to quickly connect
opportunity in emerging markets.’
to media and their social
networks
Since its launch on Ovi Store the Java language version of Snaptu has been
downloaded over two million times.
Farm Frenzy has helped HeroCraft — of Kaliningrad, Russia — achieve over five million downloads through
Ovi Store.
Developed by Idevio AB — of Göteborg, Sweden — Locago has found considerable success in Ovi Store, with
over two million downloads in more than 200 countries.
5.1.1 Design
The Design section of Forum Nokia (forum.nokia.com/Design) is a repository of information built on the years of
experience Nokia has in mobile application design. For those new to development the Introduction to User
Experience (forum.nokia.com/ux) provides a helpful primer to good UI design. Once you get started, the User
Experience Checklist for Keypad (nokia.ly/gjfEWk) and User Experience Checklist for Touch (nokia.ly/e5iHqN) are
concise guides to creating applications with the Nokia look and feel.
Forum Nokia offers a couple of really useful user experience services (nokia.ly/fZXfJz) also. Developers with
serious mobile development ambitions should consider the User Experience Evaluation. This is a charged service
that provides an independent assessment of an application’s user experience, undertaken by a user experience
expert. The review delivers a report that can be used in guiding future development. No other manufacturer
offers a similar service.
An alternative or complementary approach is end user feedback, where Forum Nokia has partnered with
Mob4Hire (mob4hire.com). This company connects developers with users, from up to 150 countries. These users
are interested in testing and providing feedback on new or existing apps. Such testing needs to be well planned
to gain the most benefit, a starting point for such planning is provided in the Forum Nokia User Experience Test
Plan for End User Feedback (nokia.ly/eLZhWT) document.
5.1.2 Develop
The Develop section of Forum Nokia (www.forum.nokia.com/Develop) is where you will find detailed
information on the three primary development technologies offered by Nokia: Qt, Web, and Java technology.
The Java section (www.forum.nokia.com/Develop/Java) provides pages containing:
A getting started guide that provides a quick and convenient introduction to Java ME development with
NetBeans and the Java tools from Nokia.
A listing of the tools available from Forum Nokia for Java development.
Access to Java related documents. These documents cover a wide range of topics related to
Java development.
A collection of code examples that provide definitive information of how to use many of the more
advanced APIs.
A snapshot of the community activity — in discussion boards, the wiki, and blogs — related to
Java technology.
The Develop section provides access to technical support also. Technical Support provides case-by-case solutions
to specific problems or answers to focused technical questions. Each request for technical support costs 170 EUR,
however members of the Forum Nokia developer programs are offered technical support cases at a discount
rate of 100 EUR per case (prices include VAT at 0%).
Through support, there is a facility to report bugs you believe you have found in the platform, which is free
of charge.
5.1.3 Distribute
The Distribute section of Forum Nokia (www.forum.nokia.com/Distribute) provides detailed information on how
to prepare, submit, and market applications through Ovi Store. The section provides:
An overview to the Ovi Store distribution offering, with spotlighted apps and developers, recent
distribution services highlights, and feeds of the latest resources and news for app and
content distribution.
Access to the guidelines you will need to follow to sign up as an Ovi Store publisher and in submitting
apps for publication.
A wide range of statistics on Ovi Store, such as download rates, popular devices, and supported countries.
Detailed information on the packaging and signing requirements for apps submitted to Ovi Store.
Information on and access to the Ovi tools that can assist with marketing your application.
Advice on how to manage your apps marketing public relations, with advice on options such as social
media and tips on how to make the most of the opportunities they offer.
5.1.5 Library
The Library section of Forum Nokia (www.forum.nokia.com/Library) brings together all the document and
media resources for Nokia platforms and supported technologies. The section includes:
Forum Nokia developer libraries, these libraries offer definitive reference information on the technologies
supported by Nokia and used in devices, of particular interest to Java developers will be:
Learning materials that provides hands-on and class room style training presentations and workshops
that you can follow at your own pace.
Multimedia, which provides access to podcasts and webinars, which cover Java technology and
development regularly.
The library provides an alternative route to discovering tools, documents and code examples too.
When accessing the discussion boards it’s always worth searching them before asking a question, many
common and not so common development and technology questions already have answers posted.
5.2.2 Wiki
With over 8000 articles, the wiki (wiki.forum.nokia.com) provides in-depth coverage on technology and mobile
apps development. The Java ME section alone has close to 1000 articles. The wiki is an excellent source of Java
code examples and snippets too.
The wiki includes the Forum Nokia Knowledge Base, a library of known issues, technical solutions, and
code snippets.
5.2.3 Blogs
With regular articles from Nokia and Forum Nokia staff as well as Forum Nokia Champions, the Forum Nokia
blogs (blogs.forum.nokia.com) provide an engaging way to keep up with the latest trends and development in
mobile apps and content.
5.2.4 Projects
Forum Nokia Projects (projects.forum.nokia.com) is a tool that enables developers to host and share projects,
either publicly or privately. Any registered Forum Nokia developer can create a project and then make details
such as source code, project wiki, timeline, and roadmap details available. Given the depth of experience
available in the Forum Nokia community, Projects is an ideal way to find developers and accelerate the
development of your project.
5.3.1 Public
Anyone can take advantage of public access to Forum Nokia. Unrestricted public access is provided to most of
the Forum Nokia website, documents, code examples, and some tools. The Discussion Boards and wiki can also
be viewed and searched.
5.3.2 Registered
Registration provides additional features, including full access to tool downloads, the ability to post messages in
the Discussion Boards and articles in the wiki, as well as host and join projects.
5.3.3 Launchpad
Part of the Developer Programs offered by Forum Nokia, Launchpad (nokia.ly/hzFnVF) provides developers with
a number of additional benefits that can help with app projects. Launchpad members gain:
Early and exclusive access to technical information, such as alpha and beta APIs and SDKs as well as
materials about forthcoming technology releases.
Access to the Discounted Devices Program to purchase Nokia devices for development and testing
purposes, for companies only.
Nokia and Forum Nokia are trademarks or registered trademarks of Nokia Corporation. Java and all Java-based
marks are trademarks or registered trademarks of Sun Microsystems, Inc. Other product and company names
mentioned herein may be trademarks or trade names of their respective owners.
Disclaimer
The information in this document is provided ‘as is’, with no warranties whatsoever, including any warranty of
merchantability, fitness for any particular purpose, or any warranty otherwise arising out of any proposal,
specification, or sample. This document is provided for informational purposes only.
Nokia Corporation disclaims all liability, including liability for infringement of any proprietary rights, relating to
implementation of information presented in this document. Nokia Corporation does not warrant or represent
that such use will not infringe such rights.
Nokia Corporation retains the right to make changes to this document at any time, without notice.
Licence
A licence is hereby granted to download and print a copy of this document for personal use only. No other
licence to any other intellectual property rights is granted herein.