Using Adobe AIR to write apps for the BlackBerry PlayBook

1. Building Apps for BlackBerry PlayBook Terry Ryan Adobe Developer Evangelist http://terrenceryan.com @tpryan

2. I work for Adobe Not for RIM

3. Why am I here?

5. The PlayBook

7. Width 7.6” / 194mm

8. Depth 0.4” / 10mm

10. Multi-touch capacitive screen

11. 1 GHz dual-core processor

12. 1 GB RAM

14. 5 MP rear-facing camera

15. 1080p HD video; H.264, MPEG4, WMV

16. HDMI video output (full OS output, not limited to image/video)

18. Wi-Fi® 802.11 a/b/g/n

20. Reliable, high-performance kernel engineered for multi-core hardware

22. Browser based

23. Flash Player 10.1

24. HTML 5

25. WebWorks for Tablet OS

26. Native C/C++ Open GL SDK (tbd)

27. Java SDK (tbd)

29. What is AIR?

30. AIR is Flash outside the browser

31. Has hooks to interact with the system

32. Flash on Mobile Flash Player 10.1 + In-browser content Games, video Deploy as a SWF, put on the web Currently 10.2 Air 2.5 + Mobile applications Native APIs, extra functionality Package to target individual devices

33. AIR for Desktop app.air

34. AIR for Devices app.bar app.apk app.ipa

35. “Native Application” AIR for Device Applications are “Native” That means they can be put on app stores NOT that the UI components are native

36. We can use Flash to build “native applications”

37. Except on the PlayBook

38. On PlayBook AIR = Native Applicationsnot “Native Applications”

39. Why Flash on Devices

40. AIR is MultiScreen

41. Is it “write once, run everywhere”?

42. No

43. Write once, tweak and configure everywhere

44. Developing

45. QNX UI Framework Flex Mobile UI Framework Roll your own ActionScript UI

46. QNX Pros Low Level High Performance Default UI Complete UI Cons Limits app to PlayBook Data components not as rich as UI

47. Demo Getting Started with QNX

48. Flex Pros Higher Level Slight Performance Cost Rich Data model Cons UI options aren’t as Rich

49. Demo Going a little further with Flex

51. Performance

53. Skinning Model (Complex but more robust, with tooling)

54. Application Framework

55. Binding/MXML

56. Extensive layout and container classes

57. Invalidation and component life cycle

58. More componentsFeatures - Complexity

59. Roll your own Pros Extreme Performance Great for traditional Flashers Cons Lot of work Not so hot for traditional coders

61. CameraRoll

62. CacheAsBitMapMatrix

63. GeoLocation

64. Touch, MultiTouch, and Gesture

65. StageOrientation

66. SystemIdleMode

68. StageWebView with more integration into the webkit on the PlayBook

69. qnx.system.QNXApplication

70. Bevel swipe down event

71. qnx.system.Device

72. Battery level, state, and monitor

73. Device info (bsn, hardwareID, vendorID, etc…)

74. qnx.media.MediaPlayer

75. Hardware accelerated play black of media and other non-Flash supported codecs

76. Notifications*

78. Powerful Hardware

79. Opportunity for profitability

80. Low barriers to entry

81. MultiScreen is real

82. Next Steps

83. Availability Flex and Flash Builder 4.5 BlackBerry ActionScript Only QNX Android ActionScript Only Flex IOS ActionScript Only Flex and Flash Builder 4.5.1 BlackBerry ActionScript Only Flex QNX Android ActionScript Only Flex IOS ActionScript Only Flex First Week of May Mid June

84. Get started http://bit.ly/AdobePlaybook Flash Builder 4.5 Beta PlayBookAIR SDK PlayBook Simulator Adobe Developer Center

85. Follow up? Feel free to contact me terry.ryan@adobe.com http://terrenceryan.com Twitter: @tpryan