How to Use the BlackBerry 10 SDK for Adobe AIR: A Complete Beginner’s Guide

How to Use the BlackBerry 10 SDK for Adobe AIR: A Complete Beginner’s Guide

Overview

This guide shows the essential steps to build, test, and package an Adobe AIR app for BlackBerry 10 devices using the BlackBerry 10 SDK for Adobe AIR. Assumes you have a working AIR app (Flash/ActionScript) and want to target BB10.

Prerequisites

  • Adobe AIR SDK installed and configured.
  • BlackBerry 10 SDK for Adobe AIR (native extensions and packaging tools) installed.
  • BlackBerry Native Packager / Momentics (for signing and device deployment).
  • BlackBerry ID (for code signing keys).
  • A development machine (Windows/macOS/Linux) and a BB10 device or simulator.

Step-by-step setup

  1. Install AIR SDK and BlackBerry extensions
    • Place the BlackBerry 10 AIR extension files into your AIR SDK’s extensions folder following vendor instructions.
  2. Obtain code-signing keys
    • Register at BlackBerry Developer, request signing keys, and install them on your dev machine.
  3. Configure your app descriptor
    • Edit application XML (app-descriptor) to include BlackBerry-specific namespaces, required permissions, and invocation targets for BB10.
  4. Integrate BlackBerry Native Extensions (ANE)
    • Add .ane files to your project build path and declare them in the app descriptor as needed.
  5. Build an AIR release package
    • Use adt (AIR Developer Tool) to compile and package your app into a BAR file:

      Code

      adt -package -target bundle -storetype pkcs12 -keystore yourCert.p12 -storepass yourPassword output.bar your-app-descriptor.xml -C bin .
  6. Sign the package
    • Ensure signing keys are applied during packaging; verify with BlackBerry signing utilities if needed.
  7. Deploy to device or simulator
    • Use BlackBerry tools (e.g., Momentics or blackberry-deploy) to sideload the BAR to a device or simulator for testing.
  8. Test device-specific features
    • Verify invocation, headless behavior, hardware access, and any ANE functionality on real hardware.
  9. Optimize for BB10
    • Adjust UI scaling, touch targets, and performance: reduce display list complexity, use GPU-accelerated rendering, and minimize memory use.
  10. Prepare for publication
    • Create app icons, splash screens, metadata, and a signed BAR. Upload to BlackBerry World or distribute via your chosen channel.

Common issues & fixes

  • Signing errors: Reinstall keys; confirm keystore password; ensure system clock is correct.
  • ANE not found at runtime: Confirm .ane included in packaging command and declared in descriptor.
  • Performance lag: Profile with Flash/AIR profiler; use bitmap caching and stage3D where possible.
  • Deployment failure: Check device OS compatibility and that developer mode is enabled on the device.

Resources

  • BlackBerry developer site for signing keys and SDK downloads.
  • Adobe AIR documentation for adt packaging options.
  • ANE vendor docs for native extension specifics.

If you want, I can generate a ready-to-run adt packaging command tailored to your project files (provide filenames and keystore info), or create a sample app-descriptor.xml with BB10 settings.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *