Going mobile natebeck

@jnbeck

ADL, PFI... WTF?ADL - AIR Debug Launcher - Using ADL, you can run an applicationwithout ﬁrst packaging and installing it.ADT - AIR Developer Tool - ADT is a multi-purpose, command-linetool for developing AIR applications.PFI - Packager For iPhone - Completely replaced by ADT. 2

The Markets... that support Adobe Flash 3

Membership Fee $99 / year $25 $99 / year ¹ $0 $0 Revenue Split 30% 30% 30% 30% 30%Overall Difﬁculty 1-10 5 1 3 9 11 Number of Apps ~435,000 ~230,000 ~13,500 ~400 ~3,000 ¹ At the moment, ﬁrst year is free Source - Apple App Store - http://148apps.biz/app-store-metrics/ Source - Android Market - http://www.appbrain.com/stats/ 4

Build Process APK Executable ADT IPA Assets BAR 5

Application Descriptor Id Version Number Render Mode Auto Orientation Aspect Ratio Full Screen Onscreen Keyboard Behavior Icons Paths Device Proﬁle Permissions iPhone Settings 6

DEVICES SUCK 7

Your ﬁnger is not transparent THIS NOT THIS 8

Devices do not have roll over or roll out 9

TouchEvents are different than MouseEvents ﬂash.ui.Multitouch ﬂash.ui.MultitouchInputMode 10

Let’s not forget about gestures ﬂash.events.TransformGestureEvent 11

Use Enter Framenot Mouse Move 12

Screen Density !=Screen Resolution 13

Screen Density != Screen Resolution 150 x 40 pixel button Desktop monitor Galaxy Tab Droid 2 iPhone 4 @100 dpi @160 dpi @240 dpi @320 dpi = 1.5” x 0.4” = 0.9” x 0.25” = 0.6” x 0.17” = 0.46” x 0.13” 14

Screen Density != Screen Resolution 150 x 40 pixel button Desktop monitor Galaxy Tab Droid 2 iPhone 4 @100 dpi @160 dpi @240 dpi @320 dpi = 1.5” x 0.4” = 0.9” x 0.25” = 0.6” x 0.17” = 0.46” x 0.13” Same pixel count, different physical sizes (Minimum recommended size: 0.25” x 0.25”) 14

Screen Density != Screen Resolution 3.5 inch diagonal screen 15

Screen Density != Screen Resolution 3.5 inch diagonal screen Same physical size, different pixel counts 15

Screen Density != Screen ResolutionClassiﬁcation 160 DPI 240 DPI 320 DPIDevices Most tablets Most Android phones iPhone 4 iPhone 3GS Motorola Droid ProMapped range < 200 DPI >= 200 DPI > 280 DPI <= 280 DPITypical range 132 DPI (iPad) 217 DPI (HTC Evo) 326 DPI (iPhone 4) to to 181 DPI (HTC Hero) 254 DPI (NexusOne) 16

Devices have differing aspect ratios 17

Some devices have additional stuff... 18

Capabilitiesﬂash.system.Capabilities 19

Devices have orientations StageOrientationEvent.ORIENTATION_CHANGING stage.setOrientation( StageOrientation.UPSIDE_DOWN ); 20

Accelerometers Get your tilt on. 21

Emulators 22

Testing on the DeviceWiFi Debug Only WiFi and USB Debug WiFi Debug OnlyLong Build Times Faster Build Times Debug TokensMobile Provisions Signing Certiﬁcates 23

Full Screen 24

Permissions 25

CPU vs GPUCPU - blitting GPU - DisplayObject iOS - 20 FPS iOS - 34 FPSDroid - 24 FPS Droid - 32 FPS 26

Playbook is wicked fast 27

Molehill? 28

ANT is your friend(or maven if you’re a cool kid) 29

Build servers are awesome + 30

Hosting your build servers 31

Your game can beinterrupted, at any time 32

Piracy can be a problem 33

Please use Version Control... please 34

Questions? 35

Thanks! Nate Beck Principal Architect @jnbeck nate@zaalabs.com blog.natebeck.net 36

http://blog.natebeck.net	2139
http://translate.googleusercontent.com	11
http://translate.googleusercontent.com	11
http://webcache.googleusercontent.com	2
http://ej.sectorit.net	1

Going mobile natebeck

by Nate Beck on Jul 31, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

5 Embeds 2,164

Statistics

Going mobile natebeck — Presentation Transcript