The first step is to register at http://www.madewithmarmalade.com/blackberry. Then create your BlackBerry 10 application using the Marmalade SDK and submit it within 30 days in “Draft” to BlackBerry World. Don’t worry, it doesn’t have to be 100% ready for this first step!

The first 300 qualifying vendors will receive a free BlackBerry Dev Alpha testing device on loan. Once apps are completed, submitted for final review, and approved, you’ll receive your free Marmalade Indie License (value of $499 USD) and you’ll get to keep your testing device to create more apps!

Our Marmalade License offer last year was extremely popular with over 1,000 apps created! Be sure to register quickly to secure your free Marmalade Indie License and be one of the first 300 to get a free BlackBerry Dev Alpha device.

If you already received a BlackBerry Dev Alpha device, you won’t qualify for an additional one. However, you are still eligible for the free license. Previous recipients of a free Marmalade License through a BlackBerry offer are not eligible to enter this promotion

For those that don’t know about Marmalade, it’s a powerful cross-platform SDK for the creation of richer apps and games on BlackBerry, iOS, Android and other platforms.

Marmalade makes it easier than ever to create BlackBerry 10 apps. Why not try developing your app with the new Marmalade RAD tool, which you’ll get for free when you sign up? Marmalade Quick is a fast, flexible and open RAD programming environment for the creation of 2D games and apps. It’s based upon best-in-class open source components including Cocos2d-x/Box2D, and the entire engine is made available in source code.

www.madewithmarmalade.com/BlackBerry

Coding and deploying for the devices with 10.1 OS

Even if your older 10.0 Z10 version of the app runs “fine” on the newer 10.1 devices (Q10 and upcoming Z10 update) running the 10.1 OS version, you should try to use the latest 10.1 SDK. Why? Starting with the 10.1 SDK, you get access to some new features which will enhance your app’s experience on the Q10 devices significantly. This particular blog post here is a great source of information when you are converting your Z10 app for the upcoming Q10 devices. In terms of the UI elements that you can leverage as a developer, among others, you now have access to certain components like the auto hiding ActionBar, customizable/freeform and sticky TitleBar – these elements will allow you to maximize your screen real estate (for the smaller screen Q10 devices) and provide more room for actual content for the users.

Key shortcuts and listeners are some of the other slick new features; they make common tasks much easier for your users. The Q10 devices are definitely designed for the power users who love the physical keyboard and who value productivity greatly. You want to show them as much useful content as possible (even in the smaller screen) and require as few user input as possible to get to the primary features and content.

What about my current applications for the Z10 devices?

If there are any updates or bug fixes necessary for your currently public Z10 versions of the app (made using 10.0 SDK), you definitely don’t want to keep your users waiting. Until the in-market Z10 devices receive the 10.1 updates, you should continue posting updates and bug fixes as necessary. Going forward, the new 10.1 features that you will be using for Q10 devices (which you definitely should be) and upcoming Z10 updates; if they are mainly on the QML asset files, you can just continue to maintain just one BAR file. All the 10.1 specific QML code; those asset files can be placed in the folder called 720×720. For devices running lower 10.1 OS, that folder will just be ignored and only the QML files in the root folder would be considered. You can check out the github sample apps here to look at the code for projects like these. If you are using any new 10.1 C/C++ API then your application would need the latest 10.1.X.X SDK to compile against to bypass all the compile errors (the corresponding BAR file would also be a different one, since it would need the minimum 10.1 platform to run against).

Project Explorer View

The QML code under the 720×720 folder. It is using some new 10.1 specific features (e.g. customizable TitleBar).
If the same BAR file is run on the 10.0 devices, this code won’t be executed (the folder will be ignored).
Note: This is a modified sample code shown here just for demonstration

The QML file under the root assets folder; this will run by default. Note that there is no 10.1 specific code here

Note that you can install all the different SDK versions through the IDE update options and install the different OS versions. Re-iterating what is mentioned on the release notes:

• If you are developing using a BlackBerry 10 Dev Alpha device, you need to download the 10.0.10.263 target from the update site.
• If you are developing using the BlackBerry Z10 smartphone, you need to download a target from the update site that matches the device version that’s provided by your wireless service provider. You can verify the device version by opening the Settings app, tapping About, selecting OS in the Category drop-down list, and checking the version that’s listed in the OS Version field.
• For more information about developing apps that work on different versions of the BlackBerry 10 Native SDK, see Appropriate version of the BlackBerry Native SDK in the BlackBerry Support Community Forums.

How do I specify restrictions to BlackBerry World and BAR files?

When you are submitting the signed BAR files through your vendor portal account, you can choose the minimum OS version and the devices accordingly. These settings control whether or not your app will show up on the users’ BlackBerry World app (depending on the devices and the OS version they are currently running on).

Note that there is also a specific value that can be set through the bar-descriptor.xml file, which dictates the minimum required platform OS version required to install and run the app. This in turn gets reflected on the final signed BAR produced (MANIFEST.MF file). Do not modify this default value set unless you are absolutely certain which device OS versions you want to prevent the app from being installed (even if they are discovered through the BlackBerry World app). This value is checked by the OS itself when the app is installed and run using the BlackBerry World app. However, this is not something that the BlackBerry World looks at (currently) to filter what apps the user can see to download. This means, if you are playing around with this value, there could be instances where the user can see or buy the app through the BlackBerry World app but not be able to install it! The vendor portal filtering only gives you granularity between 10.0.0, 10.0.10 and 10.1.0 for now but if you are modifying the bar-descriptor.xml value for this, you can end up being really specific (10.0.9.X, 10.0.10.X, 10.1.X.X) which could prevent your users from installing the app (even if they are being able to see it or buy it).

The bar-descriptor.xml editor from the QNX Momentics IDE

Viewing the resulting signed BAR file through the IDE (MANIFST.MF file)

Viewing the resulting signed BAR file through the IDE (MANIFST.MF file)

Managing code base

Since there are newer API/libraries with 10.1 SDK, you might already be thinking about how to manage your code base better. Well, there are a few different options to choose from:

1. If you are already using a version control system like Github, just use the branching and merging technique for your code base
   • Create a new branch from your latest 10.0.X.X code version. Add all the new 10.1 features here and continue to use this one for devices running 10.1 (Q10 devices for now and soon to be Z10 as well)
2. If your 10.1 changes (e.g. using some of the newer UI elements and features) are mainly on the QML assets, you can make use of the static asset selector which is new with 10.1. Basically, your IDE will be pointing to the same project (code base) but based on which device you are targetting your app, it will select the respective .qml files
   • As mentioned before, the Z10 devices running lower than 10.1 OS, will just ignore the folders such as the 720×720
3. If you are using 10.1 specific API in your C++ code (only), you can use the NDK versioning macros to detect the OS versions. This forum post here talks about this in details

To Sum Up

• For devices running 10.1 OS, definitely use 10.1 SDK to compile and deploy your app; make use of all the useful features which will make the Q10 experience of your app significantly better
  • As soon as 10.1 OS is picked up by the Z10 devices, these app releases will be shown through BlackBerry World as well (provided you set the vendor portal filtering accordingly)
  • There is more than one way to manage your code base; you have to decide which one is best for you
• For posting updates and bug fixes to the 10.0 Z10 versions of your app, continue to use the respective 10.0 SDK to compile and deploy the app
• Sanity check: Don’t forget to test and try out the application on the OS versions that your users are expected to run the app

We hope at least some of this was helpful to you. If we have missed any particular cases, do bring them to our attention and we will try to advise accordingly. Hope to see all of your apps for the Q10 devices soon!

In order to be eligible for a Limited Edition BlackBerry 10 smartphone, you must have received a BlackBerry 10 Dev Alpha testing device, submit a qualifying app, and you must also qualify under the program terms and conditions. Once you’ve submitted your app and it qualifies, you will receive an email indicating you qualify and instructions on how to trade in your BlackBerry 10 Dev Alpha testing device.

Here are the answers to some of the most common questions we’ve been receiving.

• When do I have send in my Dev Alpha?
  • The Dev Alpha device can be returned anytime. Please keep in mind that the Limited Edition devices will not begin shipping until six to eight weeks after the BlackBerry 10 launch on January 30, 2013.
  • You will not receive a Limited Edition device until you return the BlackBerry 10 Dev Alpha testing device.
• When will I receive my Limited Edition device?
  • The Limited Edition devices will begin shipping out six to eight weeks after the BlackBerry 10 launch on January 30, 2013
• Can I still register for a Limited Edition after January 21, 2013?
  • Yes, the January 21, 2013 deadline is for submitting your application in to BlackBerry World. The registration for Limited Edition can be completed anytime, using the App ID of an app submitted by January 21, 2013.
• Why have I not received an email yet?
  • This is likely because your submission is still in the queue to be validated against the terms and conditions. Once tested, you will receive an email with your qualification status.

If you have more questions, please view the Limited Edition FAQ.

[ YouTube link for mobile viewing ]

Click on the important links we discussed in this week’s #re-hashed video:

Built for BlackBerry deadlines are fast approaching! Click here for the latest.

Don’t sell your Dev Alphas! 1. That’s illegal and 2. Dev Alphas will be disabled after launch. To learn more about the trade in for BlackBerry 10, click here.

Have questions about what you’re seen here? Leave us comments below!

As a thank-you to the BlackBerry® 10 Dev Alpha community, we are offering you the opportunity to trade in your BlackBerry 10 Dev Alpha testing device for a new Limited Edition BlackBerry 10 smartphone!

In order to be eligible for a Limited Edition device, you must qualify under the terms and conditions, and you must also have received a BlackBerry 10 Dev Alpha testing device.

1. Submit a qualifying BlackBerry 10 app
2. We will send you a note indicating you qualify and instructions on how trade in your BlackBerry 10 Dev Alpha
3. Complete step 2; a follow-up email will be sent after the BlackBerry 10 launch event on January 30th, 2013

Your BlackBerry 10 application(s) need to be created and submitted to BlackBerry World by January 21, 2013. The application will go through testing and will be deemed either qualified or not qualified based on the terms and conditions.

Want to know more? Check out developer.blackberry.com/limitededition

I have always found hardware specs pretty fascinating, so if you are like me, you will be very interested in this blog post. Based on some questions that developers have asked regarding differences between the BlackBerry® 10 Dev Alpha A and Dev Alpha B hardware and other questions about getting SIM cards, we wanted to put a post together to help clarify some of the hardware details.

As we mentioned before, these are prototype devices and not final BlackBerry 10 phones. They are exclusively for our BlackBerry developers so they can get their applications ready for launch. In fact, as of October 10th, the BlackBerry App World™ storefront is open for submissions for the launch device. Now, let’s see the hardware specs on these devices:

A fair bit of the details are the same, but there are obviously some differences that are important for developers. Moving from the OMAP 4460 to the OMAP 4470 has an impact on performance, in particular for graphics with the new SGX544 graphics chip. The next most important differences are in radio connectivity. Both devices have Quad Band HSPA/UMTS, but the 4 bands supported are slightly different. If you plan on getting a microSIM card for your Dev Alpha, check which bands are required for your carrier. For example, the Dev Alpha B is limited to EDGE on T-Mobile USA, while the Dev Alph A can get HSPA. Also, the Dev Alpha B has expanded Wi-Fi capabilities, with 5GHz frequency support for 802.11a\n.

BlackBerry Infrastructure

There are some APIs that use connections to BlackBerry Infrastructure, such as BBM™ and Push. These APIs should work over Wi-Fi® without setting up any special ports, and you will be able to see the BlackBerry symbol in the homescreen titlebar, which indicates connectivity to the BlackBerry Infrastructure.

Should you decide to get a microSIM for your Dev Alpha, you do not need to have “BlackBerry Data” turned on for the account. Connectivity will work with regular Internet access alone. There may be some carriers where data connectivity doesn’t work, but Wi-Fi will work for you in that case. Please note that this is the case just for the Dev Alpha device and not BlackBerry 10 launch devices, which will need to have BlackBerry data on the wireless plan.

I hope that answers many of your questions and gets you even more interested in doing some development for BlackBerry 10. If you have further questions, post a comment below or in the forums, or tweet to us @BlackBerryDev. Remember, these Dev Alpha devices are not final BlackBerry 10 hardware; they are your opportunity to build BlackBerry 10 applications before the devices launch. Developers who get their applications in before the deadline will earn an upgrade to a special BlackBerry 10 device.

image from Indian Creek Web Design

I’ve spent many hours talking to members of our developer community both online and in person at our conferences and meet-ups, and I know you’re excited by these tools. Last week, I attended my first BlackBerry® 10 Jam in Toronto and I was blown away by the energy of the developers in attendance.

What to expect in this first Beta

The BlackBerry 10 SDKs don’t jump to awesomeness in their first iteration; it’s an evolution to greatness. In this first Beta we’ve provided the foundational building blocks and a great start for developers to see where we’re heading. The SDKs allow you to create the BlackBerry 10 user experience with core controls and a great application framework to build the necessities of your application around networking, storage and other foundational pieces. It’s not like we’re starting from scratch; all the functionality provided in the SDKs for the BlackBerry® PlayBook™ tablet is also available.

We’ve also made sure that the core UI controls in the Adobe® AIR® runtime have been re-skinned to provide the BlackBerry 10 look and feel along with updating bbUI.js for WebWorks developers to provide the same BlackBerry 10 experience as you find in Cascades™.

Did you just say “first Beta” – and what does it mean to evolve?

We’ll be providing a series of Beta releases on the road to the gold BlackBerry 10 SDK. I want to make sure I set expectations with the community on how we’re approaching the beta cycle. As we evolve each of the SDKs, it means that on top of adding functionality we may need to make changes to functionality released in a previous beta. We are making sure that we examine all the possible angles before we make changes that could affect your application’s code during the Beta and are trying to minimize these changes as much as possible. However, there are times when we’ll have to make changes to ensure that we have solid footings for moving forward with follow up releases. As we move closer to gold, our goal is to make sure that changes in the SDK do not affect compatibility with your code.

What about PIM, BBM, Share and Invocation Framework APIs?

RIM has a strong heritage in delivering fantastic deep integration into the core BlackBerry experience and providing a differentiating factor for your application on the platform, and this will continue with BlackBerry 10. As we evolve the BlackBerry 10 SDKs, these deep integration APIs will be made available, but they aren’t quite ready for 3rd party consumption yet.

These APIs are still seeing refactoring as we move through all the use cases of our core applications. We want to ensure that both our core apps are using the same APIs as 3rd party developers and that the APIs see minimal changes after they are made available in a Beta.

I won’t list all of the APIs that are coming, but I’ll list the hot topics where I usually get inquiries:

• BBM™
• PIM (Contacts, Calendar, Tasks, Notes)
• Messages/Email
• NFC
• Share/Invoke Framework
  • Adding your menu item to an existing app
  • Invoking and being invoked by another app
• String pattern registry
• Geocoding & reverse geocoding
• Bluetooth®

All these and more will be coming in follow-up Beta releases, so make sure you grab the SDKs and start building the core of your application to ensure that you’re ready to integrate these features as soon as they’re available!