BlackBerry PlayBook Native SDK reaches closed beta; developers can apply now

By Jared DiPane on 24 Aug 2011 11:36 am EDT

Ever since the release of the BlackBerry PlayBook we have been looking forward to the Native SDK to be available to the developers to see just how far they can take their development. We have seen the Adobe Air SDK as well as the WebWorks SDK but unfortunately we have been waiting for the official Native SDK to arrive. Well we just moved one step closer to it becoming a reality as today RIM announced on their Developers Blog that the Native SDK has reached a closed beta phase and they are allowing developers to apply now for access to all of the goodness.

The closed beta is limited in space, and will be on a first come first serve basis, so if you are an interested developer be sure to fill out the form now! This news is the start of many good things to come, let's hope the beta goes smooth and they are able to get this into the hands of all the anxious PlayBook developers.

Source: Developers Blog

Jared DiPane Jared DiPane "News Writer for Mobile Nations
Father | Husband | Chipotle Addict"
319 (articles) 6102 (forum posts)

Reader comments

BlackBerry PlayBook Native SDK reaches closed beta; developers can apply now


I really want a Playbook, however, I heard a podcast from another blog that the Playbook doesnt access secured WiFi's Is this true? This is how I want to connect to the internet while at home.

That's not true at all and doesn't even seem logical. What blog said this? Were they pro iPad? ;)

My WIFI is secured and hidden and I can access it just fine. It remembers my hidden network when I leave and always connects right away when I get home -- something that was an issue early on, but was fixed with an update.

And on this, the PlayBook is the only tablet certified to be used by the government, because of its encryption/security. So if wireless weren't secure, I'm thinking they wouldn't have been granted it.

Here's what the PlayBook supports for security;
WPA Personal
WPA2 Personal
WPA Enterprise
WPA2 Enterprise

Applied. Been waiting for this for a long time. Most of what I have in mind could be done in Flash but I'm not as familiar with it as I am with C++ so I've been waiting and hoping for this.

This is great news!!! I think. Can someone tell me what this means, and what is SDK? lol Cut me some slack..I'm learning :)

SDK stands for software development kit. Basically, an SDK is the set of tools for making software for a platform. The native sdk is the set of tools specifcally made for the PlayBook. Apps made in the native SDK can take full advantage of the PlayBook hardware.

So far the only apps made with the native SDK have been from RIM (such as Facebook and Scrapbook) and ones made by EA (such as Need for Speed and Dead Space).

I am not a developer so feel free to correct anything I got wrong!

Facebook and ScrapBook were built with the AIR SDK. It just shows the level of developer(s) competence. :)

Another thing, parts of the PlayBook's own Apps and GUI were built using AIR. I recall the CEO of RIM mentioning it during the ADOBE/RIM preview the other month.

Facebook was developed by Adobe for RIM using AIR SDK. Scrapbook was developed by TAT using Adobe AIR as well. The Playbook's UI was also developed on Adobe Air.

Can one of your developer guys/gals explain to me why this seems like a cart before horse scenario? I am grateful but this seems like it would have turned away so many of you from developing for this product.

A native SDK allows us developers to easily port other POSIX compliant applications to take.full advantage of the PlayBook. For instance any of the open source torrent clients can now be ported to the PlayBook with not much more than a simple recompile. We could even start putting things like Eclipse and C++ compilers on it along with just about any UNIX/LINUX based application you can imagine. Think about it this way... AIR and Webworks provide a subset of the functionality... the native SDK will allow us to get close to the metal. Our applications will have just so much more potential.

RIM opened up AIR and Webworks first because its easier to write games/apps that way but the NDK will really open ip the power of this device.