mobile experiential track

Help You Manage and ControlHelp You Manage and Control

© 2004, Intercitra. All rights reserved. Proprietary and Confidential - Not to be Copied or Distributed.

be a Part ofbe a Part ofEmotionalEmotional

RevolutionRevolution

Mobile Experiential on Java #1Mobile Experiential on Java #1

Frans ThamuraFrans Thamura

Arief PurnamaArief Purnama

Rahmat AzhariRahmat Azhari




AgendaAgenda

• Java Mobile Technology Overview

• Nokia Devices

• J2ME Development Concept

• Developing with J2ME

• User Interface Programming

• Persistence Storage

• Nokia UI Development

• The Future





Java Mobile Technology OverviewJava Mobile Technology Overview




Java TechnologyJava Technology

• Write Once carefully Run Anywhere optionally (WORA)




J2ME and MIDPJ2ME and MIDP

• For Wireless Devices

- Commonly use CLDC Configuration• Connected Limited Device Configuration

• 128kb ROM for JVM and system classes• 32kb RAM (min) for application classes

- MIDP Profile• Mobile Information Device Profile• Provides:

• Simple LCD based GUI classes• Basic networking facilities• Persistent data




CDLC FeaturesCDLC Features

• Fundamental packages re-specified

• Most package removed

- java.lang• System has no in field

- java.io• No buffered classes

- java.util• Greatly reduced• Just 9 classes

• there are 41 in Java 1.4.0

• No dynamic byte code verification

- J2SE verifier too expensive on memory




Mobile TrendMobile Trend

• Multipurpose Trend




Mobile DevelopmentMobile Development

• From Java to Streaming




Mobile Services Value ChainMobile Services Value Chain

• Content Deliverable Concept

ContentOwner

ContentOwner





Nokia DevicesNokia Devices




Nokia DevicesNokia Devices

• Nokia devices grouped according to capabilities:

- Series 30

- Series 40

- Series 60

- Series 80

- Series 90




Nokia Series 30Nokia Series 30

• Cost driven devices

• Nokia OS

• MIDP 1.0, CLDC 1.0

• Nokia UI API

• XHTML, MMS

• Example: 6310i

• Maximum size of one MIDlet suite: 30 KB

• 96x65 pixels

• Maximum data storage space for MIDlet: 20 KB





• Size driven colour platform

• Nokia OS


• Nokia UI API

• XHTML, MMS

• Example: 7210

• Maximum size of one MIDlet suite: 64 KB

• 128x128 pixels





• One hand operated feature platform

• Symbian OS


• Nokia UI API (not backlight or vibrate)

• XHTML, MMS

• Example: 7210

• Memory available to Midlets : 4MB (max)

• 176x208 pixels




... basic functionality originates from Series 60 platform on

Symbian OS

Nokia 7650 Nokia 3650 Nokia N-Gage TM mobile game deck device

Siemens SX1

Samsung SGH-D700

Nokia Series 60 devicesNokia Series 60 devices




Nokia Series 60 UINokia Series 60 UI

• Nokia UI Screen





• One hand operated feature platform

• QWERY Keyboard

• Symbian OS


• Personal Java, JavaPhone API

• MIDP 2.0 (Nokia 9500 and 9300)

• XHTML, MMS

• Example: 9210

• Memory available to Midlets : ~14MB

• 640x200 pixels




Input method

One-hand operation Pen input

Display size

176 x 208 208-240 x 320

Applications • Multimedia messaging• Imaging• Entertainment, downloading• Personal Information Management• Office connectivity

• Business applications • Entertainment, downloading• Personal Information Management• Web browsing• Multimedia messaging, Imaging

Series 60 PlatformUIQ

Symbian OS support V7.0 and onwardsV6.1 and onwards

Complementary UI designsComplementary UI designs

UIQ





J2ME Development ConceptJ2ME Development Concept




J2ME DevelopmentJ2ME Development

• Can use basic J2ME tools to build apps

- Tool support makes development simpler

• Automated verification and packaging

- Sun J2ME Wireless Toolkit

- Sun Java Studio Mobile Edition

- Borland JBuilder Mobile Toolkit

- Eclipse

- Websphere Devices Developer

• Comes bundled with wireless toolkit

• Simple integration with Nokia SDK




Tool supportTool support

• Nokia Developer’s Suite

• Integrates with JBuilder, or Sun One Studio 4

- Run as standalone

- Includes Nokia emulators

- 6310i

- Symbian

• Download more emulators

- Series 40 and 60

• Others

- Jakarta Ant?




Developing with MIDPDeveloping with MIDP

• MIDP applications are called Midlets

- Conceptually similar to Applets

• Can be downloaded

• Executed in host environment

- Subclass the MIDlet class

• Provide no argument constructor

• Must not implement main method

• Implement lifecycle methods




Developing MidletsDeveloping Midlets

• The Midlet lifecycle

- A device will call the methods shown here as appropriate

• Midlet can control its own lifecycle

- notifyPaused()

- notifyDestroyed()




Developing with MIDPDeveloping with MIDP

• Development process

1. Subclass MIDlet class

2. Override lifecycle methods

3. Compile

4. Pre-verify

5. Package• Create jar file• Create application descriptor (jad file)

6. Install and run, or emulate




MIDP application structureMIDP application structure

• A MIDP application comprises two files

- jad file (application descriptor)

- jar file

- a Midlet suite is a collection of related Midlets




The jad fileThe jad file

• A file describing the Midlet suite

• Must include:

- MIDlet-Name• name of the Midlet suite

- MIDlet-<n>• A name for each Midlet in the suite

- MIDlet-Version

- MIDlet-Vendor

- MIDlet-Jar-URL

- MIDlet-Jar-Size

• Information regarding the Midlet suite

- May include:• MIDlet-Description

• MIDlet-Icon

• MIDlet-Info-URL

- MIDlet-Data-Size• Minimum persistent storage required by

suite

• Default is Zero




The jar fileThe jar file

• Follows standard jar file format

- Manifest to include all data found in jad file• Except: MIDlet-Jar-Size

- Can include other resources• E.g: Images

- Must also contain:• MicroEdition-Profile• MicroEdition-Configuration




DemoDemo

• Sun Java Wireless Toolkit

• Nokia J2ME Toolkit





Developing with J2MEDeveloping with J2ME




Developing with J2MEDeveloping with J2ME

• Elementary MIDP

- User Interface Programming

- Persisting Data

- Networking

• Extension packages

- Nokia UI API classes





User Interface ProgrammingUser Interface Programming





• Limitation of display devices

- Colour or Black and White

- Display size & device memory

- Forget about AWT or Swing!• Too big• Overly complex• Tables, Dialogs, Multiple windows

• New API for user interfaces with MIDP

- Lightweight

- Designed for use with small screens• Based upon single display areas





• LCD user interface API

- In package:• javax.microedition.lcdui

• Simple structure

- Add Displayable items to a Display!

• Each Midlet has a single Display to use

- Use static method on Display class:• Display.getDisplay();

• User interface class hierarchy

- Screens are high level

- Canvas low level (see later)




User Interface Programming (List)User Interface Programming (List)

• A List example:

- list = new List("Select artist:", List.EXCLUSIVE);

- list.append("B2K",null);

- list.append("Babyface",null);

• List types include:

- EXCLUSIVE

- MULTIPLE

- IMPLICIT




User Interface Programming (TextBox)User Interface Programming (TextBox)

• A TextBox example:

- TextBox textBox = new TextBox("Email address:","Text", 30,TextField.EMAILADDR);

- Text constraints include:• ANY• EMAILADDR• NUMERIC• PHONENUMBER• URL




User Interface Programming (Form)User Interface Programming (Form)

• Forms

- Like other Screen subclasses• occupies whole screen• can have tickers set• etc...

- Allow multiple items to be added• there are many subclasses of Item

• A Forms example:

- form = new Form("Default settings");

- form.append(new Gauge("Earpiece volume:",true,10,5));

- form.append(new Gauge("Ringer volume:",true,10,5));




User Interface Programming (Command)User Interface Programming (Command)

• Notify user generated events

- J2SE applications use an event delegation model• Explicitly attached to event sources• Typically results in many anonymous classes

• More efficient to re-use objects

- J2ME applications use Commands• Many predefined types• Can be extended with custom types




User Interface Programming (Command)User Interface Programming (Command)

• A Commands example:Form f = new Form(...);

f.addCommand(new Command("Exit", Command.EXIT, 0));

f.setCommandListener(new CommandListener() {

public void commandAction(Command c, Displayable d)

{

if (c.getCommandType() == Command.EXIT) {

notifyDestroyed();

}

}

});




MIDP Development HierarchyMIDP Development Hierarchy




DemoDemo

• User Interface Programming





Persistence StoragePersistence Storage




Persistent StoragePersistent Storage

• Midlets will need to persist data

- Users name

- Mail host address

- High score for a game

• MIDP includes a specification for Persistent Storage

- Record Management System (RMS)

- Simple database model

- Holds unique records for each Midlet suite

- Device responsible for storing data





• Each Midlet suite shares records

- Care should be taken with concurrent access• multiple active Midlets• multi threaded Midlets

• writes to records guaranteed to be atomic• program defensively

• Very simple API

- javax.microedition.rms

- Only contains one class!• and four interfaces





• Records are stored in a Record Store

- Use the RecordStore class

- Each record store is named• max 32 Unicode chars

RecordStore rs = null;

try {

rs = RecordStore.openRecordStore("my-data",false);

} catch(RecordStoreNotFoundException e)

{

// doesn't exist

} catch(RecordStoreException e){

// some other error

}





• To create a new record

- specify the bytes you want to store

- each record within a store will have a unique number (id).

RecordStore rs = ...;

byte[] data = ...;

int id = -1; //record ids will always be > 0

try {

id = rs.addRecord(data, 0, data.length);

} ...




DemoDemo

• Persistence Storage Development





Nokia UI DevelopmentNokia UI Development




Nokia UI DevelopmentNokia UI Development

• MIDP 1.0 UI limited

• Nokia address this with custom UI classes

- Included in upcoming MIDP2.0 specification

• New classes

- FullCanvas

- DirectGraphics

- DirectUtils

- DeviceControl

- Sound




Nokia UI OtherNokia UI Other

• Nokia UI supports other features

- Sound

- Device control• Volume of device• Backlight• Vibration

• User preferences may prevent these from being accessible




Application DesignApplication Design

• Screens are organized into a flow:

- Most require simple behavior

- Some more complex




Adapting to DevicesAdapting to Devices

• Different devices have different capabilities

- Must cater for these





The FutureThe Future




J2ME FutureJ2ME Future

• Wireless Messaging (WM API, JSR 120)

• Mobile Media (MM API, JSR 135)

• Bluetooth API (JSR 82)

• SyncML

• MMS API (WM API 2.0)

• SIP API

• Game API

• 3D API





Thank YouThank You

Frans ThamuraFrans Thamura

Arief PurnamaArief Purnama

Rahmat AzhariRahmat Azhari

[email protected]@intercitra.com

mobile experiential track

Technology

nokia series

midlet suite midlet

nokia devices nokia

midlet lifecycle

nokia emulators

nokia sdk

appropriate midlet

url midletjar