• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

Mix of AdobeAIR and HTML5 during migration

New Here ,
May 17, 2016 May 17, 2016

Copy link to clipboard

Copied

Hi,

Does anyone have any best practices when it comes to migrating from AdobeAIR to HTML5 for mobile apps?

We have a quite complex app written in Adobe AIR and that App also runs in web browsers on computers. So a nice reuse of code between web browsers and mobile apps.

On the web we can iteratively move to HTML5 by embedding our old AS3 written features in HTML5 and then little by little migrate each feature to HTML5. Its a complex task but its doable.

However on mobile is there a way to avoid the big all-or-nothing migration of an app so you would somehow have a mix of AdobeAIR and HTML5?

Thanks.

TOPICS
Development

Views

311

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 17, 2016 May 17, 2016

Copy link to clipboard

Copied

I would suggest simply rewriting it if need be. Not knowing the features or requires though - hard to say.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
May 17, 2016 May 17, 2016

Copy link to clipboard

Copied

LATEST

If you mean the app version, there wouldn't be any reason to rewrite it in Javascript. But, if you want the one and only version of the experience to be HTML5, and somehow usable in a mobile app, you could use AIR as the app wrapper, and show the HTML5 content in a StageWebView. You could then still have ActionScript do some of the things that Javascript cannot do.

The main issues you'll hit are memory management (web views don't seem to clear memory very well), and on iOS you will have sound issues, the first sound in a web view has to be triggered by a user action.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines