Porting your app from the BlackBerry PlayBook OS
There are some things to consider when porting your application from the BlackBerry PlayBook OS to the BlackBerry 10 OS. To begin the porting process, you must first download the BlackBerry 10 SDK for Adobe AIR. After it's installed, you can import your existing code and begin tweaking it to run on the BlackBerry 10 OS.
You can refer to the following sections to learn more about the differences between the BlackBerry PlayBook OS SDK for Adobe AIR and the BlackBerry 10 SDK for Adobe AIR and the modifications you must make to get your Adobe AIR application running on the BlackBerry 10 OS.
Application icon size
When creating new application icons, make sure that your application icon is the appropriate size for the application platform.
|Platform||Icon Size (pixels)|
|BlackBerry PlayBook OS||86x86|
|BlackBerry 10 OS||114x114|
For information, see: <icon>
Support for multiple screen sizes
Your BlackBerry 10 application should support different screen sizes so that your app looks consistent across devices. You specify the splash screen sizes in the BAR application descriptor file and you can add them for each supported screen resolution. The BlackBerry 10 OS chooses the correct icon and splash screen to use based on the device that the application is running on.
The BlackBerry 10 OS supports the following screen sizes:
|BlackBerry 10 Dev Alpha||1280x768||-|
|BlackBerry 10 Z10 device||1280x768||-|
|Future full-touch BlackBerry 10 devices||1280x720||16:9|
|BlackBerry 10 Q10 physical keyboard devices||720x720||1:1|
To support multiple screens in your BlackBerry 10 application, modify the bar-descriptor file.
<splashScreens> <image>splash-1024x600.jpg</image> <image>splash-600x1024.jpg</image> <image>splash-1280x768.jpg</image> <image>splash-768x1280.jpg</image> </splashScreens>
For more information, see <splashScreens>.
In the BlackBerry PlayBook OS SDK for Adobe AIR 2.0, the qnx.fuse.ui API replaced the qnx.ui API used in version 1.0. Even though the qnx.ui was deprecated, it remained available to applications for the BlackBerry PlayBook OS.
In the BlackBerry 10 SDK for Adobe AIR, the qnx.ui API has been removed, and you must update up your application to use the qnx.fuse.ui API.
To use the qnx.fuse.ui API in your application, you must add the QNXSkins AIR native extension to your application. For more information see AIR native extensions.
The following table displays the BlackBerry PlayBook OS SDK for Adobe AIR 2.0 and the corresponding fuse.ui API:
|BlackBerry PlayBook OS SDK 1.0||BlackBerry PlayBook OS SDK 2.X and BlackBerry 10 SDK|
- qnx.ui.events.dataProviderEvent remains unchanged
- qnx.ui.data remains unchanged
- For qnx.ui.text.textInputIMF use qnx.fuse.ui.text.TextInput
- For qnx.ui.listClasses.scrollPane use qnx.fuse.ui.core.Container
In the BlackBerry 10 SDK for Adobe AIR, the old container methodology (found in qnx.ui.core) was deprecated in favor of using a new layout and container method to organize your UI components.
In the BlackBerry 10 SDK for Adobe AIR, the container concept has changed to improve flexibility and provide layout behaviors that make it easier to develop applications across devices.
For more information on building your UI using the layouts, see Organizing your UI with containers and layouts.
AIR native extensions
AIR native extensions (ANE) provide access to features and functionality of the BlackBerry Native SDK within the AIR environment. To use features such as sensors, network, or to apply UI and skinning features, the ANE must be added to your application.
For more information on adding ANE, see AIR native extensions.
The user experience for BlackBerry 10 has changed significantly from the experience on the BlackBerry PlayBook tablet. Creating a cinematic experience, having fluid workflows, and emphasizing high performance are just some of the key principles that BlackBerry 10 applications should follow. The BlackBerry 10 UI Guidelines cover these principles and specify design, interaction, and style guidelines for your app.