What about Dev Alpha B devices?

We’ve got an update for that too! With this release you’ll be able to check out how your Z10 apps will run on the 10.1 OS, and make all the necessary changes, if needed.

Have you already submitted your awesome app and received your LE BlackBerry 10 device? Or have you already picked up your own BlackBerry Z10?

We certainly want to see more of your great app ideas come to life, so you’ll also be seeing a 10.1 SDK OS update for these devices as well.

Will the simulators be getting an update too?

Yes! There will be a 10.1 SDK OS build for the BlackBerry 10 simulator, so whether you test on a device or a simulator, know that you’ll be able to test on the most recent build available. You won’t see two different simulators available but you will get one simulator with the option to boot to a Z10 or Q10 resolution.

Let’s recap the updates that you’ll be seeing:

• Dev Alpha C device
• Dev Alpha B device
• BlackBerry Z10 devices
• Simulator for Z10 and Q10

So how can you get these updates for your device?

The 10.1 SDK OS will be available for each device through its own autoloader – you’ll see one each for the Dev Alpha C and the Dev Alpha B.

For developers who want to test it on their BlackBerry Z10, you’ll need to find out your device model number and grab the corresponding autoloader. The device model can be found under Settings> About. See the example screenshot below.

Note: This SDK OS update is only for testing purposes and does not replace your full BlackBerry 10 OS. To revert your BlackBerry Z10 to a public OS release, please follow the steps outlined in this KB Article. Using BlackBerry Link, you will be able to reload your device software to a full OS and, if needed, download any OS updates from your carrier.

Device targets for the Momentics IDE will also be updated. If you need a refresher on how to download the target OS and configure it, we’ve got a detailed description right here.

Now that you’re ready for the Q10 (and subsequent 10.1 release!), we can’t wait to see and use your apps! Go on and grab the updates and the simulator at developer.blackberry.com!

Hi fellow BlackBerry® devs! It’s Michelle here from the BlackBerry Developer Relations team with a new addition to our supported JavaScript frameworks. To follow up with the Dojo 1.8 release, it gives me great pleasure to announce BlackBerry’s Guide to Working with the Dojo Toolkit. If you haven’t heard of Dojo before, now’s your chance to get familiar with this amazing web framework.

Dojo is a very powerful tool for creating and controlling web pages. It is one of a few frameworks to offer complex JavaScript classes, it has an enriched components and UI library ready for use right out of the box, internationalization (i18n) capabilities, cross-platform graphics API and also provides many, many, more utilities to help build your web app. Dojo’s new 1.8 release contains an astounding 175 sub-packages and over 1,400 modules to choose from. Within its extensive plugin offering, to cater to our mobile needs, Dojo also comes with its own Mobile utilities – in the 1.8 release alone there have been 26 new widgets added! These Mobile UI components are tailored for better performance on mobile devices while taking advantage of the full power that the Dojo Toolkit has to offer.

With official support for BlackBerry OS 6 and 7, and already performing well on BlackBerry10 devices, Dojo’s many code modules provide the tools you need to create an amazing app experience. Using Dojo’s enhanced mobile components and utilities also means your app will work on the BlackBerry® PlayBook™ tablet and upcoming BlackBerry 10 devices. Included in the mobile module is automatic app theming, meaning your BlackBerry® WebWorks™ and Dojo application can take advantage of the built in themes so your app can have that native BlackBerry UI look and feel to it, giving you more time to experiment  and work on that code.

Upon your first glance at Dojo code, the syntax may be unfamiliar for some developers as Dojo uses the AMD (Asynchronous Module Definition) format. Using AMD allows you to keep your app size at a minimum. This module loading style allows you to choose and load exactly the plugins you want without having to include other code which you may not use and will only weigh down your app. With AMD, the modules are loaded in an asynchronous fashion which will help reduce app loading time.

There is so much more to Dojo than can be included in this post, so check out their latest release and if you need any more convincing, check out the 10 reasons to use Dojo in your projects.

To see what you can do with Dojo, check out their assortment of demos, and to get started with BlackBerry development using Dojo, check out BlackBerry’s Guide to Working with the Dojo Toolkit.

You can also join us at BlackBerry Jam Americas where you can learn all about the different web frameworks to use with your WebWorks app as well as attend a Dojo session to learn more about this powerful JavaScript toolkit.