AIR for iOS -Quick Publish vs Ad Hoc -optimization difference? -


i use 'quick publish' option single kiosk based air ios apps.

is there additional optimization occurs during compilation if using 'ad hoc' option?

yes. there 4 different build options (at least in flash builder):

  1. ad hoc release build
  2. distribution release build
  3. standard debug build
  4. fast debug build

release builds, standard debug, , fast debug substantially different in terms of performance.

  • the release builds meant final releases , take 5-30 minutes build, depending on cpu , ram. ad hoc allows install on specific devices specified in mobileprovision file. distribution creates build can submit ios app store
  • standard debug allows debug mode in close-to-release-mode environment , takes same time release builds, though bit quicker build. not fast release, won't notice difference in normal activities. in activities, however. on last app, had decode wav files playable on device. in standard mode, 10-15 second task on iphone 4s. using ad-hoc, less second. however, parts of app should perform relatively close release build would. time might notice difference in simple application in flex view instantiation
  • fast debug incredibly slow. build in seconds, comparable standard swf or air android app. notice drop in performance using , should used rapid testing building, changing single value, building again, changing value, etc.

for being used outside of development, should always use release builds. far more optimized , meant for. i'm unsure quick publish (i assume flash pro option?), guess matchesup 1 of debug modes. determine how builds , should indicate one. either way, kiosk app should using ad hoc release builds.


Comments

Popular posts from this blog

html - How to style widget with post count different than without post count -

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

javascript - storing input from prompt in array and displaying the array -