Procrastinator’s Guide to a Free Blackberry Playbook

This past week my fitness calculator app, Repper, was approved for the Blackberry App World.  In return for enduring Research in Motion’s arduous app submission process, I will be awarded with a free Blackberry Playbook once they are officially released to the public.  Because I’m so pleased with this news, I thought I would share what I perceive as the easiest route to getting your hands on a free Playbook yourself.

You only have til March 31st to submit your app, according to the latest version of their offer.  While this date has been pushed back a number of times, I suspect this may be the hard deadline.  You don’t need to be approved by the due date, you just need to have your app submitted.  You may think I’m exaggerating here, but creating the app is the easy part, submitting is the real pain in the ass.

So before I get into too many boring details, let me lay out the list of things you need to do in order to reduce the amount of surprise time sucks you will encounter:

  • Sign up to be a Blackberry vendor
  • Get your code signing keys
  • Follow the getting started guide for setting up your AS3/Flex development environment (or WebWorks if that’s your thing)
  • Convert an existing AS3/Flex project or create a new app (IF YOU ONLY READ ONE SECTION, READ THIS)
  • Sign and submit your app to the Blackberry App World through the vendor portal.
  • Wait for approval

The steps necessary are listed in a very specific order to maximize efficiency, particularly becoming a vendor and getting code signing keys.  Read the section below detailing each step to find out why.  So again, DO THE STEPS IN ORDER, it will save you time in the end.

Sign up to be a Blackberry vendor

This is simple enough. You just need to fill out a form with relevant personal information do that Blackberry has a record of who you are.  In the early stages of this process you actually needed to submit a notarized letter, if you were an individual and not a company, in order to complete the registration.  From what I understand this is no longer required so it should make your life a little easier.

Blackberry is also waiving their usual $200 registration fee for developers during this period.  So whether or not you plan to hit this deadline, it may be worthwhile just to sign up and get in for free.

You will do this first because this process may take a few business days to complete.  They review the vendor registration submissions and Blackberry has not been terribly quick with approvals at any step in this process.  In fact, that is the most common complaint about the app submission process so far is simply how long it takes to complete.  So get this done first and don’t wait for approval to move on to the next step.

Get your code signing keys

This is another step that is as simple as filling out forms, but again requires Blackberry’s intervention to approve.  Also bear in mind that the code signing key you will receive will only work on one workstation once registered and cannot be transfered to another workstation.  You have to request another key is you want it to work on another workstation.  I have requested 2 keys thus far and both have taken at least 2 business days to arrive via email.

Like the last step, get this done now and don’t wait for the key to arrive to move on.  Hopefully by the time you are ready to submit your app to the App World you’ll have received your vendor approval and signing key.

Follow the Getting Started Guide

I’m not going to go into a great deal of detail here because the Blackberry documentation lays it out very well.  Just follow the guide found here and you’ll be fast on your way to your Blackberry Playbook “Hello, World!”.

One thing to keep in mind is that you must be building against the 0.9.4 SDK. I initially made the mistake of hanging on to the old 0.9.3 SDK and Blackberry has requested that I rebuild against the latest version before being able to make my app available on the App World.  Its not a huge deal, but will require you to go through the whole app update process if you don’t do it right the first time.  That said, they still extended me the offer of the free Playbook without yet having made this change.

Create your app

I know, I’m trivializing what sounds like a big step.  But here’s the thing: I’ve not heard of one Playbook app that has been turned down due to perceived usefulness or quality.  The only apps that I have heard being rejected are ones that actually don’t work.  This is common in the case of people trying to implement multitouch or gesture support when the simulator does not properly emulate the behavior.

In other words, put together a simple application that is useful to a niche group.  Or better yet, convert an existing AS3 or Flex Hero project to a Playbook app.  Check out my prior post to see how I did this in literally seconds.

For me, Repper was a no brainer.  It is a simple fitness calculator that determines your 1-15 rep max on exercises.  It was originally built using Flex Hero in Air for Android.  Its currently available on the Android Market if you wanna take a look at it there.  You can see there is no rocket science.  Blackberry has no high expectations for the functionality of an app for which developers have no device.  KISS is the key factor here.  Wait til you have one of these Playbooks in your hand before you try to get really creative with it.

Don’t get me wrong, I’m not encouraging fart app development here.  I’m just saying that at this point in the game Blackberry is happy handing out Playbooks to competent, motivated developers.  The quality of this one app is not what they are banking on.  They are hoping that with their generous gesture that they may woo more than a handful of mobile developers to spend their time on Blackberry Playbook apps rather than iPad or Android tablets.

In short, no excuses.  Create a useful, simple app.  Its not that hard and you know it.

Submit your app to the App World

Before digging into the specifics of the submission and signing process, here’s the things you’ll need:

  • Your signing certificate (CSJ file)
  • A less than 4000 character description of your app
  • A 480×480 product image for the App World
  • At least one screenshot that is no larger than 640×640
  • An 86×86 PNG icon, which includes a 5 pixel transparent buffer around it.  This effectively makes the icon content 76×76 or less.

First you are going to sign your release build of your application using your CSJ signing certificate.  This is an intimidating and somewhat complex process.  I highly suggest picking from the choices at the bottom of their code signing guide and following them to the letter.  I personally had no problems with the workflow for signing apps through Flash Builder 4.5 “Burrito”, but I’ve heard that some people had issues.  The safest route might be to follow the command line instructions for the entire process.  Again I emphasize, follow the instructions to the letter and don’t try to frankenstein multiple guides together, it makes it harder to troubleshoot the issues.

After you have successfully signed your app, you just need to submit it to the App World through the vendor portal. Just go to “Manage Products” and click the “Add Product…” button.  You will be walked through the steps necessary to submit your signed BAR app file.  So long as you have all the items I mentioned above in the list, and a successfully signed app, it should be pretty smooth sailing.  Finding these things out during the submission process was quite frustrating.

Carve out at least an hour for the above process, because it will take some time.  The code signing can be especially time consuming from the command line, but it seems to be the one sure fire way to get the app successfully signed.

If you followed my advice and became a vendor and requested your signing keys first, you won’t find yourself waiting for days once you’ve reached this part of the process… like I did.

Wait for approval

Now that you finally have your app submitted, you just have to sit back and relax… and relax…. and relax… and do your taxes… and ge your car inspected… and renew your driver’s license… you get the idea.  It takes a LONG time to get approved.  I’ve not heard of anyone getting their first app approved in under 2.5 weeks, with many waiting as long as 7.  But once again, as long as you get the app submitted before the deadline, you are still eligible for the free Playbook.

Once you finally do get approved you’ll receive an email telling you as much.  It may also include additional steps you must take in order for your app to be made available in the App World, like mine did.  Shortly following this, for me it was a day later, you’ll receive a congratulations notice for your free Playbook.  Included in this email should be a link to a purchase order for your Playbook with a cost of $0.00.  I have not heard of a single case where an app was approved but the developer did not receive a free Playbook offer.  Fill it out, send it in, and join us in the patient wait for the release date.

Hope you follow these steps and find yourself with your very own free Blackberry Playbook too!  Let me know if you happen upon success yourself.

12 Responses to “Procrastinator’s Guide to a Free Blackberry Playbook”

  1. Matthew Fabb says:

    Also RIM has mentioned if you do updates to your app while it’s in the approval process, you don’t miss your line in the queue for approval. So I would suggest to anyone coming down to the line & close to the deadline, to go ahead and submit your app even if it’s buggy. Then you can fix the bugs in the next week or two while and resubmit a new file later.

  2. Didn’t realize that Matthew, great point! So as I stated above, the real trick is getting your vendor registration and signing certificate in time to submit before the deadlines.

  3. Thanks a lot for this post Tony. I’m really glad I started following you on Twitter.

    Hoping to have my app submitted this weekend.

  4. Ditto that Andy! Twitter is a very karma driven experience. You get what you give.

  5. says:

    Thanks for the encouragement. But, after following instructions for FB4.5 and it does not recognize BB tablet platform using TabletSDK-0.9.4 any ideas?

  6. Christian Ruiz says:

    Hi Tony,

    I submitted my app a few weeks ago, and today I’ve got an answer saying that it’s approved but that I got to upload a signed copy. I thought that I’ve already signed my app, I’ve read again all the docs about submitting, and the only thing that I guess I could be missing is the publisher element in the blackberry-tablet.xml (I don’t have that file in my project and I’ve looked at your app source I didn’t see it either). Have you any ideas about what could be wrong?

    Thanks for all that really useful post!

  7. @Bill: Hmmm, I didn’t have any issues with the installation of the SDK. Are you using the publicly available FB 4.5 on the labs site or are you using one from the prerelease program? The prerelease program version are not supported by Blackberry yet as far as I know. Include some detail with the problem you’re having and I’ll try to help if I can.

    @Christian: Did you sign it using the requested CSJ files? If not, that could be the problem. I had to resign and resubmit mine as well. Did you originally use a version of the SDK earlier than 0.9.4? I think Blackberry made some changes to the vendor portal recently so maybe all apps before a certain date need to be resigned.

    In any case, I actually received my purchase order for a free playbook BEFORE resigning my application for the App World. So if you haven’y gotten your’s yet, you should get it soon.

  8. Man what a pain in the ass that whole process was, but my app is submitted for approval! Thanks for all your help Tony. It would have been much harder without your and Joseph’s blog posts.

  9. Desmarkie says:

    I’m almost there. Have everything I need, but just can’t log into the developer portal to submit my app. Really frustrating :)

    Anyone else have trouble signing in once approved? I’m just hoping I can submit before tomorrow’s deadline >.<

  10. Chris says:

    Hey I got this message saying I was approved:

    Currently your application is in an ‘Approved’ state within the vendor portal, please correct the following in order for us to have it ready for launch (TBA):

    Items that need attention:

    - Please send signed copy

    - Default BlackBerry icon after installing application, please make sure the icon size is 86×86 and included with your bar file submission

    I just uploaded my icon to the App World but is there a special way to attach an icon to my program specifically in Adobe Flash Builder? Also I too thought I signed my program properly, should I apply for a new set of keys and resign it that way?

  11. @Chris: Check out my other post on mobile icons for markets: https://savagelook.com/blog/android/mobile-developers-icon-image-checklist

    In there it shows you that for blackberry playbook you need a blackberry-tablet.xml file with your 86×86 icon specified. The post shows you how to make your own simple xml. When you resign your BAR file and resubmit to the vendor portla, make sure that icon with the blackberry-tablet.xml is included and you should be all set.

  12. @Desmarkie & @Chris: I had to re-sign my application as well. I had to do it because I originally submitted my app with the 0.9.3 SDK and they require the 0.9.4 now. I did request a new developer key, but thats because my workstation changed and the signing certificate only works for one workstation. You may or may not have to get a new key, but I don’t think its a requirement.