RIM releases BlackBerry NFC APIs

Support for both tag reading/writing and card emulation applications are included in the BlackBerry Java SDK v7.0, ready for the forthcoming launch of the NFC-enabled BlackBerry Bold 9900 and 9930 smartphones.

BOLD MOVES: Developers can begin writing NFC apps now

RIM has launched the BlackBerry Java SDK v7.0 in beta. The SDK can be used to “leverage the NFC capabilities of the BlackBerry smartphone to read and write NFC tags,” RIM explains. “With the API functionality available, you can access a secure element (JSR 177) for mobile commerce and loyalty apps, and include tag/card emulation, and tag reading and writing in your app. Your app can also include support for NFC IT policies.”

“This new version of the SDK also comes with simulators for the new BlackBerry Bold 9900 series of smartphones, allowing you to test your applications against the latest and greatest,” the official Inside BlackBerry Developers Blog explains.

“With the new BlackBerry Bold 9900 smartphone and BlackBerry Bold 9930 smartphone on their way, you will have the tools you need to make sure your apps are running on these smartphones at launch. What’s more, the BlackBerry App World storefront is also accepting app submissions for these new devices! You now have the chance to be among the first to have your application submitted and ready for these exciting new products.”

The release notes explain that the net.rim.device.api.io.nfc package enables developers to read and write data on smart tags, emulate a smart tag and access a secure element embedded on a BlackBerry device or SIM card.

The NFC API can also be used to enable a device to emulate a smart tag using the net.rim.device.api.io.nfc.emulation package. The net.rim.device.blackberry.api.accessory.AccessoryManager class can also be used to connect smart accessories to the device while the net.rim.device.api.io.nfc.se package is used to access a secure element.

The BlackBerry Java SDK v7.0 is available to download from the BlackBerry website now.

Next: Visit the NFCW Expo to find new suppliers and solutions

4 comments on this article

  1. Looks like RIM has come up with their own proprietary NFC API. Why they did not try to implement JSR 257 instead?

    1. Hi Lalit

      JSR 177 and JSR 257 are both standard approaches to different things. JSR 257 is for non-secure applications such as tag reading and writing. JSR 177 is used for encrypted communications with the secure element, so RIM is indicating here that they have implemented the standard way of creating a secure communications channel to the secure element.

      I hope that helps…


      1. Thank you Sarah, yes I understood accessing the secure element part using JSR-177 (which is indeed a standard API). But what about the API for reading/writign an NFC tag ? Do they support JSR-257 for this purpose or they have their own proprietary API ?

Comments are closed.