Submitting your app for Built For BlackBerry

Adobe AIR Development

You have your application or game approved in BlackBerry World. It’s a killer application. It follows all the BlackBerry UI/UX guidelines, integrates with the BlackBerry® 10 operating system and it runs lean. In short, you have a good feeling it qualifies for the Built For BlackBerry and 10k Developer Commitment programs. But how exactly do you get your application or game considered for the programs?

Well, it’s easy. Prior to January 21st, 2013 (the cut-off date for the 10k Developer Commitment), log in to your vendor account in BlackBerry World. Then, click the Manage Products link. Your screen should look something like this:


The first thing to take notice is the Status of your application. Before you can apply for Built For BlackBerry, the status must be Approved or Up For Sale. If your application has not been approved for BlackBerry World, you cannot submit it to Built For BlackBerry testing. If the status is approved, you will see the word Apply underneath the heading “Built For BlackBerry”. Go ahead, click that link.

Here is where you agree to the terms and conditions of the two programs. If you are only interested in the Built For BlackBerry Program, you only need read and agree to those terms. This means your application or game will go through Built For BlackBerry testing but will not be eligible for the 10k Developer Commitment. If you want to be part of the 10k Developer Commitment, then you must read and agree to both terms and conditions. Once you have read and agreed to the terms, check the boxes next to the appropriate terms and conditions and click Save.

Your Manage Product screen will be updated to show you have applied for the program and your application is Pending approval.

Once your application or game has passed the Built For BlackBerry testing, the term Pending will change to Approved. But what if something is amiss? What if your application or game is Rejected?

Don’t panic – you’ll see that there is a message icon next to the term Rejected. Clicking this message icon will show you the reason(s) why your application failed the Built For BlackBerry testing. You can fix those issues in your application and resubmit the application for Built For BlackBerry testing.

That’s really all there is to it! Built For BlackBerry will identify your application as a great BlackBerry 10 application. I am really excited to start seeing, using, and playing all the Built For BlackBerry applications and games. Remember, launch is January 30th 2013, so make sure you get your apps into Built For BlackBerry testing before January 21st, 2013.

About Tom Anderson

Tom Anderson – Senior BlackBerry Developer Evangelist – Tom started his career in 1986 with Microsoft Corporation where he was a Program Manager on such products as Windows 3.11, Windows for Workgroups, Windows 95, and Internet Explorer. He was also the creator of the Windows Resource Kit which began that product line. In addition, Tom presented at many trade shows and gave technical presentations with the Microsoft Executive Staff. He left Microsoft in 1995 to form Three Points Consulting with Marianne Reid Anderson and Bob Taniguchi. Three Points focused on bringing the power of the emerging internet technology to everyday life. Tom’s innovative technology solutions played a key role in the successful acquisition of Three Points by TechRx. At TechRx, he acted in the role of CTO until it was acquired by NDC Health of Atlanta, Georgia. In 2004, Tom decided to become a High School Teacher as his primary method of giving back to the community. In 2005 he joined the Pennsylvania Cyber Charter School (PA CYBER) where he was awarded the Keystone Award for Innovative Use of Technology in the Class Room. During this time, he also earned a Master’s degree in Software Design through Capella University. In 2009, in addition to teaching, Tom returned to software development creating various web and mobile applications.

Join the conversation

Show comments Hide comments
+ -
blog comments powered by Disqus