Device Specific Library Part One

We 've seen J2ME does a great job of abstracting the features of an MID. The MDIP API gives you the comfort of working with a (relative) standart to develop the platform your game. MIDP 1.0 represents the features that are common to all MIDs that support that version. There are some expeptions where support is optional, such as repeating keys and pointer device input. Generally, though, what you see in the specifications is what you can experct to get.

As you can imagine, many mobile device have features beyond those supported by MIDP 1.0 -especially features that are unique to particular devices (such as vibration support). This will naturally continue as the hardware improves. The MIDP specifications will continue to update. You 'll notice that many of the features made available as manufacturer-specific extensions under MIDP 2. However, it is the nature of a standardizes common platform to leave room for manufacturer extensions.

Manufacturers make additional featurer available to developers through J2ME software development kits (SDKs). For example, Nokia provides an SDK for many of their device, which provide features such as transparent image blitting, playing sounds, and turing the device into a vibrator (settle down).

You also need to regularly test, if not directly develop, using the various emulators supported for different phones. Trust me, switch phones regurally during development to keep some perpective on the idiosyncrasies of different device. It'll save you from some monster surprises later.

In the next few sections, you 'll take a book at the features made available by some of the more popular MID manufatcuters : NOKIA, Siemens, and Motorolla.