Publishing apps in BlackBerry World: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Henri Vikki (talk | contribs) No edit summary |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:BlackBerry]] | [[Category:BlackBerry]] | ||
= Publishing | = Publishing applications in 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 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. | ||
| Line 7: | Line 9: | ||
This article is a supplementary summary provided in addition to the following articles: | This article is a supplementary summary provided in addition to the following articles: | ||
* | * [https://developer.blackberry.com/devzone/blackberryworld/getting_started_preparing_your_app_for_blackberry_world.html Getting Started] | ||
* | * [https://developer.blackberry.com/devzone/blackberryworld/faq.html FAQ for developers about BlackBerry World] | ||
* | * [https://developer.blackberry.com/design/bb10/ UI guidelines for BlackBerry 10] | ||
== Key meta information entries in the BAR application descriptor file == | == Key meta information entries in the BAR application descriptor file == | ||
The template of the | The template of the <code>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 | A good overview of the of all important fields is available in [https://developer.blackberry.com/native/documentation/core/com.qnx.doc.ide.userguide/topic/capabilities_editor_options_base.html this article]. The below sections cover essentials only | ||
=== Author name === | === Author name === | ||
Make sure that these fields match the ones you set in the Developer Certificate and in the debug token : | Make sure that these fields match the ones you set in the Developer Certificate and in the debug token : | ||
<code> | |||
<author>Name Surname</author> | |||
<authorId>Your ID from debug token</authorId> | |||
</code> | |||
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. | 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. | ||
| Line 25: | Line 31: | ||
=== Versions === | === Versions === | ||
* Make sure the | * Make sure the [https://developer.blackberry.com/native/documentation/core/com.qnx.doc.native_sdk.devguide/topic/r_barfile_dtd_ref_versionnumber.html version number] of your application is correct. Be aware that this number should match the information you supply to BlackBerry World | ||
* Supported platforms, see | * Supported platforms, see [https://developer.blackberry.com/native/documentation/core/com.qnx.doc.native_sdk.devguide/topic/r_barfile_dtd_ref_platformversion.html this] article. | ||
=== Application icon === | === Application icon === | ||
The | The [https://developer.blackberry.com/native/documentation/core/com.qnx.doc.native_sdk.devguide/topic/r_barfile_dtd_ref_icon.html application icon for BlackBerry 10] should be 114x114 pixels in PNG format. | ||
=== Splash screens === | === 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 | 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 [https://developer.blackberry.com/native/documentation/core/com.qnx.doc.native_sdk.devguide/topic/r_barfile_dtd_ref_splashscreens.html this article] for more details. | ||
== Signing the application package == | == Signing the application package == | ||
You can use the blackberry-signer tool from the command line: | You can use the blackberry-signer tool from the command line: | ||
<code> | |||
blackberry-signer -storepass <certificate_password> -cskpass <BB_ID_token_password> <output_bar_file.bar> | |||
</code> | |||
where | where <code><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 == | == Publishing to BlackBerry World == | ||
This process is not different for Qt applications than for any other applications. See the following articles: | This process is not different for Qt applications than for any other applications. See the following articles: | ||
* [https://developer.blackberry.com/devzone/blackberryworld/preparing_your_app_for_blackberry_world.html Setting up your app in BlackBerry World ] and all articles in this section | |||
* [https://developer.blackberry.com/devzone/blackberryworld/preparing_an_app_release.html Uploading your release and adding digital goods] and all articles in this section | |||
Latest revision as of 14:47, 19 March 2015
Publishing applications in 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:
Key meta information entries in the BAR application descriptor file
The template of the
bar-descriptor.xml
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. 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 :
<author>Name Surname</author>
<authorId>Your ID from debug token</authorId>
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 of your application is correct. Be aware that this number should match the information you supply to BlackBerry World
- Supported platforms, see this article.
Application icon
The application icon for BlackBerry 10 should be 114x114 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 for more details.
Signing the application package
You can use the blackberry-signer tool from the command line:
blackberry-signer -storepass <certificate_password> -cskpass <BB_ID_token_password> <output_bar_file.bar>
where
<certificate_password>
is the password you set while creating your developer certificate (stored in the
author.p12 file
in the keys folder), and
<BB_ID_token_password>
is the password you set when you generated the BlackBerry ID token (stored in the
bbidtoken.csk
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 and all articles in this section
- Uploading your release and adding digital goods and all articles in this section