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

6. Hardware Dimentions  Height 5.1” / 130mm  Width 7.6” / 194mm  Depth 0.4” / 10mm  Weight 0.9 lbs /400g Performance  7” LCD display 1024 x 600  Multi-touch capacitive screen  1 GHz dual-core processor  1 GB RAM  Symmetric multi-processing Media  3 MP forward facing camera  5 MP rear-facing camera  1080p HD video; H.264, MPEG4, WMV  HDMI video output (full OS output, not limited to image/video)  Stereo sound speakers Connections  Micro USB and Micro HDMI ports  Wi-Fi® 802.11 a/b/g/n  Bluetooth ® 2.1 +EDR

7. BlackBerry Tablet OS Based on QNX® Neutrino® RTOS Reliable, high-performance kernel engineered for multi-core hardware Multi-threaded POSIX OS (Portable Operating System for Unix) for true multitasking Developer Options Tablet OS SDK for Adobe AIR Browser based Flash Player 10.1 HTML 5 WebWorks for Tablet OS Native C/C++ Open GL SDK (tbd) Java SDK (tbd) Android dealio (tbd)

8. AIR SDK Used in default Applications

9. Adobe AIR

10. What is AIR?

11. AIR is Flash outside the browser

12. Has hooks to interact with the system

13. 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

14. AIR for Desktop app.a ir

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

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

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

18. Except on the PlayBook

19. On PlayBook AIR = Native Applications not “Native Applications”

20. Why Flash on Devices

21. AIR is MultiScreen

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

23. No

24. Write once, tweak and configure everywhere

25. Developing

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

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

28. Demo Getting Started with QNX

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

30. Demo Going a little further with Flex

31. The Spectrum of Frameworks Performance - Simplicity Features - Complexity Advantages  Same components native apps are using  Performance  Basic skinning, container, layout and invalidation Advantages  CSS  Skinning Model (Complex but more robust, with tooling)  Application Framework  Binding/MXML  Extensive layout and container classes  Invalidation and component life cycle  More components

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

33. AIR APIs  Accelerometer  CameraRoll  CacheAsBitMapMatrix  GeoLocation  Touch, MultiTouch, and Gesture  StageOrientation  SystemIdleMode  NavigateToURL

34. PlayBook APIs  qnx.media.QNXStageWebView  StageWebView with more integration into the webkit on the PlayBook  qnx.system.QNXApplication  Bevel swipe down event  qnx.system.Device  Battery level, state, and monitor  Device info (bsn, hardwareID, vendorID, etc…)  qnx.media.MediaPlayer  Hardware accelerated play black of media and other non-Flash supported codecs  Notifications*  Extending AIR app with Native C/C++ app*

35. Conclusions

36. Powerful Hardware

37. Opportunity for profitability

38. Low barriers to entry

39. MultiScreen is real

40. Next Steps

41. 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 MayMid June

42. Get started http://bit.ly/AdobePlaybook –Flash Builder 4.5 Beta –PlayBook AIR SDK –PlayBook Simulator –Adobe Developer Center

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