Today, RIM is launching the beta of the Native SDK for BlackBerry Tablet OS, which will allow game developers to code in C/C++ environment and

RIM launches beta Native SDK for BlackBerry Tablet OS

Posted by

Today, RIM is launching the beta of the Native SDK for BlackBerry Tablet OS, which will allow game developers to code in C/C++ environment and take advantage of a deeper API set.

To gain access to these new tools and start creating and porting applications for the BlackBerry Tablet OS developers can sign up to participate in the closed beta program at http://03268fe.netsolhost.com/bbbeta/ Interested developers should apply to the beta quickly as space is limited and will be granted on a first come first served basis.

What can developers do?
Using the OpenGL ES 2.0 API, developers can create rich and visually stunning 2D and 3D games for the BlackBerry PlayBook. The Native SDK allows developers to take direct advantage of the power that is inherent in the BlackBerry PlayBook. Developers will be able to build high performance, multi-threaded games. A great example of the interface and graphics that can be built is Need For Speed ( http://blogs.blackberry.com/2011/02/blackberry-playbook-need-for-speed-demo-video/ ).

The Native SDK supports accelerometer, device orientation and other device features, as well as a number of POSIX compliant libraries, which will help developers that are porting existing games.

The Native SDK includes the QNX® Momentics Tool Suite, which is an Eclipse-based integrated development environment. QNX Momentics provides memory profiling, application debugging, and memory usage statistics. This will help developers as they debug sophisticated programs, including hardware accelerated OpenGL applications.

More information on the fast and efficient APIs provided by the Native SDK and associated developer benefits can be found at http://devblog.blackberry.com/2011/08/nativesdk-for-blackberry-tablet-os-closed-beta.

  1. Sounds really impressive.

    The tools are all there, quite all right.

    The critical question is how to convince developers to toe that app_development_path. A real ‘Chicken N egg’ problem –

    Lots of existing apps encourages the development of even more apps for that platform.

    ‘Traveler, there is no paths; paths are made by travelers.’

    Hmm..

  2. Isn’t this a little too late? Other platform release their SDK before the launch of the device. RIM appears to be doing just the opposite. It appears RIM rushed to release an incomplete Playbook!

Leave a Reply

Your email address will not be published. Required fields are marked *