This presentation by Steve Easley, lead developer for RedMinnow Interactive, LLC, explains how to become an iOS developer and take a Flash application and convert it to an iOS app to be sold on the Apple App Store.

2. About Me Lead Developer Red Minnow Interactive Co-own the company with Duane Andrews Flash developer for 13 years Flex developer for 3 years Have created marketing games for:

3. About Presentation 2 Parts Becoming iOS developer, retrieving files needed and publish a Flash app to iOS

4. About Presentation 2 Parts Becoming iOS developer, retrieving files needed and publish a Flash app to iOS Device Agnostic Optimizing apps for mobile Design/develop for multiple screen sizes and processor capabilities What you can and can’t do on devices

5. About Galaxy Grab Initially created for ActiveDen last summer Flash component

6. About Galaxy Grab Initially created for ActiveDen last summer Flash component Created for designers to modify and make own game

7. About Galaxy Grab Initially created for ActiveDen last summer Flash component Created for designers to modify and make own game Can be resized to designer’s needs This would be start for multiple screen sizes

8. About Galaxy Grab Initially created for ActiveDen last summer Flash component Created for designers to modify and make own game Can be resized to designer’s needs This would be start for multiple screen sizes Can change properties in Component Inspector

9. About Galaxy Grab Initially created for ActiveDen last summer Flash component Created for designers to modify and make own game Can be resized to designer’s needs This would be start for multiple screen sizes Can change properties in Component Inspector tiny.cc/activeDen

10. Galaxy Grab to iOS Goal Learn the process Take current game straight to iOS to see how it performs Have an app on Apple App store

11. iOS Development Quick Start Guide Join iOS Developer Program (min. $99/yr) developer.apple.com iProvisioning Portal developer.apple.com/ios/manage/overview/ Tutorials: tiny.cc/iOStutorial (pictures) tiny.cc/adobeIOShelp tiny.cc/adobePackagerForum

13. Text Entry worked well

14. SharedObjects worked (surprisingly)

15. Background music with on/off button worked

17. Text Entry worked well

18. SharedObjects worked (surprisingly)

19. Background music with on/off button worked

21. Text Entry worked well

22. SharedObjects worked (surprisingly)

23. Background music with on/off button worked

25. Text Entry worked well

26. SharedObjects worked (surprisingly)

27. Background music with on/off button worked

29. Text Entry worked well

30. SharedObjects worked (surprisingly)

31. Background music with on/off button worked

33. Tested several projects and all were S-L-O-W

34. Online search revealed similar results from others

35. Shelved idea but came back to it a few weeks later

37. Tested several projects and all were S-L-O-W

38. Online search revealed similar results from others

39. Shelved idea but came back to it a few weeks later

41. Tested several projects and all were S-L-O-W

42. Online search revealed similar results from others

43. Shelved idea but came back to it a few weeks later

45. Tested several projects and all were S-L-O-W

46. Online search revealed similar results from others

47. Shelved idea but came back to it a few weeks later

49. Tested several projects and all were S-L-O-W

50. Online search revealed similar results from others

51. Shelved idea but came back to it a few weeks later

53. Optimizing Apps for Mobile What works for web may not work for mobile Vector vs. Bitmap Processor intensive vs. file size Animation – Blitting over Tweening Animation only when needed and when little else is going on OOP vs. fast code Big MVC architectures slow down mobile apps Balance between reusable code and performance

54. Optimizing Apps for Mobile What works for web may not work for mobile Vector vs. Bitmap Processor intensive vs. file size Animation – Blitting over Tweening Animation only when needed and when little else is going on OOP vs. fast code Big MVC architectures slow down mobile apps Balance between reusable code and performance Gaming and Optimization Techniques 8bitrocket.com moock.org gskinner.com/blog tiny.cc/adobeMobileOptimization

55. Optimizing Apps for Mobile Some ideas will help any app - mobile or online Declaring variables before loops

56. Optimizing Apps for Mobile Some ideas will help any app - mobile or online Declaring variables before loops Data type variables – Double Advantage App runs faster and takes up less memory

57. Optimizing Apps for Mobile Some ideas will help any app - mobile or online Declaring variables before loops Data type variables – Double Advantage App runs faster and takes up less memory Vectors vs. Array

58. Optimizing Apps for Mobile Some ideas will help any app - mobile or online Declaring variables before loops Data type variables – Double Advantage App runs faster and takes up less memory Vectors vs. Array Object Pooling If it has been made. Don’t delete and recreate if needed Creating/Destroying objects is memory intensive and slows system down

59. Optimizing Apps for Mobile Some ideas will help any app - mobile or online Declaring variables before loops Data type variables – Double Advantage App runs faster and takes up less memory Vectors vs. Array Object Pooling If it has been made. Don’t delete and recreate if needed Creating/Destroying objects is memory intensive and slows system down Drawing API is slow – try not to use

60. Optimizing Apps for Mobile Some ideas will help any app - mobile or online Declaring variables before loops Data type variables – Double Advantage App runs faster and takes up less memory Vectors vs. Array Object Pooling If it has been made. Don’t delete and recreate if needed Creating/Destroying objects is memory intensive and slows system down Drawing API is slow – try not to use Avoid filters – create bitmaps for them instead

62. Limit moving items on screen

63. New items “transport” in (used blitting)

64. Created Test to check speed of processor

65. Math problem run 1 million times

66. Returns how long it took to run

67. Based on testing of devices, number indicates how many items to animate on-screen at once

68. Tested on several different devices:

69. iPhone 3G (900ms)

70. iPhone 3GS (600ms)

71. iPhone(300ms)

73. Limit moving items on screen

74. New items “transport” in (used blitting)

75. Created Test to check speed of processor

76. Math problem run 1 million times

77. Returns how long it took to run

78. Based on testing of devices, number indicates how many items to animate on-screen at once

79. Tested on several different devices:

80. iPhone 3G (900ms)

81. iPhone 3GS (600ms)

82. iPhone(300ms)

84. Limit moving items on screen

85. New items “transport” in (used blitting)

86. Created Test to check speed of processor

87. Math problem run 1 million times

88. Returns how long it took to run

89. Based on testing of devices, number indicates how many items to animate on-screen at once

90. Tested on several different devices:

91. iPhone 3G (900ms)

92. iPhone 3GS (600ms)

93. iPhone(300ms)

95. Limit moving items on screen

96. New items “transport” in (used blitting)

97. Created Test to check speed of processor

98. Math problem run 1 million times

99. Returns how long it took to run

100. Based on testing of devices, number indicates how many items to animate on-screen at once

101. Tested on several different devices:

102. iPhone 3G (900ms)

103. iPhone 3GS (600ms)

104. iPhone 4 (300ms)

106. Resize Handler functions load the correct size for screen size

108. 6 days from submission to selling

109. No problems with submission (have heard horror stories)

111. Resize Handler functions load the correct size for screen size

113. 6 days from submission to selling

114. No problems with submission (have heard horror stories)

116. Resize Handler functions load the correct size for screen size

118. 6 days from submission to selling

119. No problems with submission (have heard horror stories)

121. Resize Handler functions load the correct size for screen size

123. 6 days from submission to selling

124. No problems with submission (have heard horror stories)

127. Non Apple UI-based apps

128. Visualization/Aggregator from web data

130. Non Apple UI-based apps

131. Visualization/Aggregator from web data

133. Non Apple UI-based apps

134. Visualization/Aggregator from web data

136. Non Apple UI-based apps

137. Visualization/Aggregator from web data

139. Non Apple UI-based apps

140. Visualization/Aggregator from web data

141. Apps that don’t need to tap into device-specific functionalitytiny.cc/comparisonChart

142. Questions?

143. Thank You! Steve Easley steve@redminnow.com twitter: steveRedMinnow blog: www.redminnow.com/blog