This document discusses digital entertainment options for the home, including smart TVs, tablets, and smartphones. It describes how these devices can work together seamlessly through a home network to share digital content. Examples are provided of applications that have been developed to allow interactive experiences across multiple devices using technologies like RTMFP for discovery. Input methods like multitouch, gestures, and accelerometers are discussed. Challenges of developing for different device screen sizes and resolutions are also covered.

1. Digital Fun for the Digital Home: TV, Tablets, & Smartphones Renaun Erickson – Last updated 2011.05.06

3. Mobile application developer

4. Device Junkie

5. Based in Henderson, NV, USA

6. Like Games, Jeeps, and Archaeology

9. Telecommunication

10. Gaming Consoles

11. SmartphonesWhat are the digital home and digital living? The digital home is an evolution of the idea that PCs, consumer electronics and mobile devices should work together seamlessly through a wired or wireless network to share digital content within a home environment. Digital living extends that idea to include sharing content on the go as well. Digital Living Network Alliance (DLNA) dlna.org

12. The Center of Digital Fun 5

14. Wireless Router

15. Tablets

17. Tons of OS & Chipsets

18. No single control of runtime releases

19. Abstracting as much of device fragmentation as possible

20. Remember early stages of device OS and runtimes, constant change7

22. Router

23. Motorola Atrix / with WebTop

24. iPad2

25. iPod 5th gen

26. iPhone 3GS

27. Galaxy Tab

28. Nexus One2011 AIR 2.5 Available FP 10.1 Available FP 10.1 Available FP 10.2/AIR 2.6 Available FP 10.1/AIR 2.5 Available AIR 2.6 Available FP 10.2/AIR 2.6 Available FP 10.1 8

29. Concepts of Digital Fun Create multi device and user experiences. Device discovery should be automatic or simple. Make use of a wide range of inputs: Multitouch, Gestures, Mic, Camera, Geolocation, Accelerometer, etc… Pixels – different device screen resolution and their relationships matter. Panels – the physical size of devices do not equal screen resolution. Creating one controller application for multiple content. A brain in each application, but only one active at a time. Interaction time: to real time or not to real time the application. Applications that change based upon connected device topology. 9

30. Demos 10 PickQuick CanvasExpo MADH Video Eiden CoinFlip Photoshop Touch SDK - DeviceCompViewer

31. PickQuick Discovery using NetGroup and GroupSpecifier (RTMFP). One application for all platforms. TV remote control input. Designed for tablet, scaled down for specific size & ppi. Every app is full game. 11

32. CanvasExpo Discovery using NetGroup and GroupSpecifier (RTMFP). TV is canvas application. Smartphones and Tablets are the input mechanism. Uses multitouch and gestures. Supports multiplayer at the same time. 12

33. CoinFlip Discovery using NetGroup and GroupSpecifier (RTMFP). Accelerometer used on mobile browser where present, but not on desktop. Browser based application, no download. Supports multiplayer at the same time. Every app is full application and runs the same code. 13

34. Mini Dodgem AIR Hockey (MDAH) Discovery using NetGroup and GroupSpecifier (RTMFP). Multiple game board devices, TV & Tablets Smartphone controllers Supports two players at the same time. Accelerometer & multitouch inputs. 14

35. Eiden – Wiimote/WebTop Wii Controller Android application for Wiimote IME. Atrix WebTop for HDMI mirroring. Input is keyboard keyCodes. Supports two Wiimotes, for 2 player game. 15

36. DeviceCompViewer Photoshop Touch SDK ActionScript 3 Library TCP based IP configured & password required setup Sends ExtendScript JS & special Touch SDK commands Hard to check comps on a device 16

39. AS3 only

41. IP in the multicast range - 224.0.0.0 to 239.255.255.255 with 224.0.0.0/225 for special use (http://www.iana.org/assignments/multicast-addresses/multicast-addresses.xml)

42. Port – any valid port

44. Accelerometer

45. Physical Size / Pixels Per Inch Screen Resolutions are Independent of Physical Screen Size

47. Use PPI and screen physical size to scale only certain devices.

48. Create different view/layoutbased on screen resolution and physical size (tablet vs smartphone).

49. Different view/layout for each device.

51. AIR Application Compile & Package 24 Compiling Packaging ActionScript AIR Application SWF

52. AIR Current Packagers 25 Compiling Packagers adt – Desktop, Android, TV, & iOS Creates: .air, .exe, .dmg, .apk, .ipa pfi - iDevice uses Packager for iPhone Creates: .ipa Now part of adt (AIR 2.6) blackberry-airpackager– PlayBook Creates: .bar

53. How Packaging AIR apps for iOS Works ADT .ipa SWF Assets Runtime is cross compiled down to ARM instructions and is part of each application. ActionScript Captive runtime – The term used for this process. This is a highly requested feature for Android. Flex support for AIR for iOS is coming in AIR 2.7 in 2011. http://www.surveymonkey.com/s/flexprerelease

54. Discussion Time 27 Q/A Thank you for attending renaun@adobe.com http://github.com/renaun @renaun http://renaun.com/blog