Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Adobe AIR Development

Reply
Trusted Contributor
Vibes
Posts: 215
Registered: ‎03-14-2012
My Device: PlayBook 2.0
My Carrier: AT&T
Accepted Solution

What devices are supported for an Adobe Air app?

What devices are supported for an Adobe Air app?

Does a BlackBerry app created with Adobe Air (Air 2.5) run on a BlackBerry 9900 for example?

 

Thanks.

Please use plain text.
Developer
jtegen
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10
My Carrier: Verizon

Re: What devices are supported for an Adobe Air app?

Only PlayBook and BB10 phones
Please use plain text.
Trusted Contributor
Vibes
Posts: 215
Registered: ‎03-14-2012
My Device: PlayBook 2.0
My Carrier: AT&T

Re: What devices are supported for an Adobe Air app?

What is the min. OS to choose for Adobe Air apps? Is 1.0.0 working for them all? (There are plenty to choose from 1 to 2.1)

Please use plain text.
Developer
jtegen
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10
My Carrier: Verizon

Re: What devices are supported for an Adobe Air app?

2.1 = PlayBook
10.0 = QNX/BB10
Please use plain text.
Developer
UberschallSamsara
Posts: 1,026
Registered: ‎12-29-2010
My Device: PlayBook, Z10 LE, Dev Alpha C

Re: What devices are supported for an Adobe Air app?

There are PlayBook apps out there that specify 1.x as minimum OS but you should be aware that:

 

1) Most PlayBook owners upgrade their OS, so the percentage of devices running 1.x is low,

2) There are lots of deprecated UI components (e.g. qnx.ui.*) from the 1.x days that should not be used,

3) When PlayBook gets upgraded to BB10, it's likely the deprecated UI components will go away.

4) It's my understanding that there are security issues with 1.x that make pirating easy, and some piracy-inclined PlayBook owners have held off on OS upgrades for this reason.  You may want to think about whether it's counterproductive to your business to support these folks.

 

For new PlayBook projects, it seems advisable to:

1) Factor your business logic into its own packages (a general best practice, obviously)

2) Design using qnx.fuse.ui components (and flexible layouts, to support multiple screen sizes, if you plan to have smartphone versions of your PlayBook apps)

3) Get yourself setup with good revision control and bug tracking (also a general best practice), if you intend to fork your codebase to support legacy PlayBook OS alongside BB10 on PlayBook.  In the event that BB10 for PlayBook has any major issues that cause folks to delay or completely avoid upgrading, this could be a scenario you want to have at least contingency plans for.

Please use plain text.