Publishing AppWorld
Publishing Applications in the BlackBerry world
This pages provides a quick run through the key topics which an application developer should pay attention to when switching from development mode into the released mode and preparing the application for publishing in BlackBerry World.
This article is a supplementary summary provided in addition to the following articles:
- Getting Started [developer.blackberry.com]
- FAQ for developers about BlackBerry World [developer.blackberry.com]
- UI guidelines for BlackBerry 10 [developer.blackberry.com]
Key meta information entries in the BAR application descriptor file
The template of the
bar-descriptor.xml<code> file has dummy entries for many fields not relevant on the first steps in application development. You have to provide correct information before distributing the app for testing and submitting it for selling.
A good overview of the of all important fields is available in this article [developer.blackberry.com]. The below sections cover essentials only
Author name
Make sure that these fields match the ones you set in the Developer Certificate and in the debug token :
You can use either Qt Creator or the Momentics IDE to read this data from a debug token. You can also look it up in the MANIFEST.MF in debug token BAR file. If those fields do not match you will not be able to deploy a signed application to a device.
Versions
- Make sure the version number [developer.blackberry.com] of your application is correct. Be aware that this number should match the information you supply to BlackBerry World
- Supported platforms, see this [developer.blackberry.com] article.
Application icon
The application icon for BlackBerry 10 [developer.blackberry.com] should be 114×114 pixels in PNG format.
Splash screens
A splash screen is shown just after the user taps on the application icon and kept on the screen all time before the application starts rendering on the screen. It is a good idea to define an image which should be shown as splash screen to improve the user experience. See this article [developer.blackberry.com] for more details.
Signing the application package
You can use the blackberry-signer tool from the command line:
where
<certificate_password><code> is the password you set while creating your developer certificate (stored in the <code>author.p12 file<code> in the keys folder), and <code><BB_ID_token_password><code> is the password you set when you generated the BlackBerry ID token (stored in the <code>bbidtoken.csk<code> file in the keys folder)
Publishing to BlackBerry World
This process is not different for Qt applications than for any other applications. See the following articles:
- Setting up your app in BlackBerry World [developer.blackberry.com] and all articles in this section
- Uploading your release and adding digital goods [developer.blackberry.com] and all articles in this section