games communities. SNAP Mobile 7 includes a lightweight, client-side
Java library (the SNAP Mobile Client API) that communicates over HTTP
or TCP with a remote backend system called the 'SNAP gateway'.
The SNAP Mobile Client API enables creation of connected
games with features such as account creation and login, presence,
instant messaging, score tables and rankings, and multiplayer game
The SNAP gateway includes a Session Manager and a Virtual Client
system that handle requests from SNAP Mobile clients and responses from
SNAP community services, such as web services, the Instant Messaging
and Presence Service (IMPS), and SNAP Game services.
Once your game successfully completes the SNAP Mobile Compliance
Test, you can take it to market via a number of Nokia and third-party
channels. For more information, please refer to Appendix B.
3.2.6 Retrieving Telephony Information
From S60 3rd edition FP2 onwards, there are additional system properties
that provide access to telephony information. The information provided
is minimal but it is meant to serve telephony services to applications that
are not themselves telephony-oriented.
For example, consider an application that requires locking onto a
specific device. Developers have to make their applications aware of
the unique IMEI of the phone and provide a mechanism to lock their
applications to it. The scenario in such a case could be:
1. The user sends the phone IMEI when they purchase the application.
2. The IMEI is used to bind the application to the device.
3. The application verifies the phone IMEI at first launch.
There is no Java API that provides access to telephony information.
The information is available only via the following system properties:
com.nokia.mid.imei : International Mobile Equipment
International Mobile Subscriber Identity
com.nokia.mid.networkid : network identification parameters
com.nokia.mid.networksignal : current (GSM/CDMA) network
com.nokia.mid.networkavailability : network availability