For all of us developing on Flash Pro 5.5 - watch out for the deployment type - performance varies

Forum|Forum|14 years ago
October 22, 2011
3 replies
1746 views

hey

for everyone who uses Flash Pro for mobile development please take notice that there is a big difference in the way you deploy your app

on iOS, "Deployment - Apple App Store" gives a much better performance than the quick publishing

on Android, publishing to an APK file and installing that file with some method (like dropbox) gives better performance than testing or debugging the FLA straight through USB

so don't end up fighting performance issues that are actually not there, like i did

cheers

Saar

Development

This topic has been closed for replies.

Correct answer Joe ... Ward

You are definitely correct for iOS. The "fast" mode is only there to reduce packaging time (since the iOS packager is painfully slow). The tradeoff is that your application runs on the device as interpreted code and without the benefit of a JIT (just-in-time compilation). This is pretty much worst-case for code execution speed.

On Android, there should not be any difference in performance because of the way you install the app. Perhaps you are also changing to a "release" build instead of a "debugging" build. Release builds always out perform debug builds.

E

EducaSoft_Bart

Known Participant

So if we do an APPStore build we can also install it on our device the same way like we do with a quick publish ?

Colin Holgate

Inspiring

If you have done an Ad Hoc build (one that uses the distribution certificate and provisioning files) on a given device, the app will continue to work when you install the App Store submission version.

S

saarikoAuthor

Inspiring

thanx Joe Ward

u r completely right

(i wanted to edit my original post regarding the Android but couldn't see how )

J

Joe ... WardCorrect answer

Participating Frequently

You are definitely correct for iOS. The "fast" mode is only there to reduce packaging time (since the iOS packager is painfully slow). The tradeoff is that your application runs on the device as interpreted code and without the benefit of a JIT (just-in-time compilation). This is pretty much worst-case for code execution speed.

On Android, there should not be any difference in performance because of the way you install the app. Perhaps you are also changing to a "release" build instead of a "debugging" build. Release builds always out perform debug builds.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded