#Adobe air 24 android
#Adobe air 24 code
#Adobe air 24 free

#Adobe air 24 android

Some of the recent updates from Adobe have been to try to push a/v further onto the platform, rather than handling it internally, so we can see how that goes.ĥ) Improving context3d so that context is not lost so easily on android devices. Playback delays are a right pain, and have been from the start! We can look into this, but I know that different devices and chipsets have different characteristics so some of this may be tricky. I’ll talk to Adobe to see why this was put in place – we have a customer using Workers on an embedded platform and didn’t have any such restriction afaik.Ĥ) Improvements in audio api and fixing bugs like sound play delay on Android. Removing FPS limit on workers in mobile devices which is now hard coded to 4 FPS. Current limit is 512mb which is way low nowdays.Ģ) Improvements in multi threading. I think for the most part we are looking at keeping our first SDK release very simple, and then once we’re properly up and running we can start looking at things like these!ġ) Allowing more memory for textures in GPU.

I’ve got a few initial comments so have put these here. For everyone else, I'ved opted to share this information here. If you emailed HARMAN concerning AIR33, you most likely got this email as well.

I hope this is useful: thank you for your interest in this, we’re hoping it will be a fairly seamless transition and are looking forward to what we can then do with the runtime to help support you and your applications! Apologies for the delay (and for the information drought recently) – this deal has been a long time being prepared and ensuring that all the lawyers are happy! no using this for uploading to the Play Store and distributing to millions of end users, as we are still going through the QA processes! The goal for the formal release of AIR v33 is then at the start of July, hopefully giving sufficient time for application packaging/testing/deployment prior to the 1st August deadline. Timescales: we are aiming to release an initial beta version in around two weeks’ time this would only be for internal development/testing, i.e.We can look at ways to help where an IDE may use a graphical dialog to allow you to select ARM vs x86, prior to them hopefully updating the UI I’m also wondering whether we can make the packaging a little simpler (if anyone else uses the command line directly. The goal is to make this work just the same with all the existing IDEs.Ultimately though, the fees that we can raise through distribution of AIR will be paying for the development team, so we’re really going to strive to make it a success. Feedback is welcome obviously we’ve been looking at Unity and other such products/frameworks to ensure that we’re being competitive and not putting too big a burden on anyone.

We’re looking at an alternative subscription method but this may need to follow later.

#Adobe air 24 free

Pricing is still going through final approvals here, we have some initial thoughts from which our initial business model was created which would involve a free tier and then a kind of ‘pay-as-you-go’ mechanism which is based on a low royalty fee depending on distribution levels.

We’ve been focussing on the engineering side of it and not necessarily the infrastructure quite so much, but we do plan to have a web portal and will upload the SDKs to that in the short term we may use an alternative mechanism for distribution though, the focus is still more on the runtime and SDK than on a web portal….

We want it to be in reasonable shape before we release the beta! We also need to integrate some updates from Adobe that they’re making in AIR 32 around the multimedia area, taking advantage of the underlying platform/OS for some of the a/v playback.

We’ve got AIR building and running in 64-bit mode on Android, but not yet extensively tested, so that’s our focus currently.

#Adobe air 24 code

We’ve had a relationship with Adobe for a dozen years to provide the Flash Player and AIR technologies to customers who don’t fall into the “normal” category of desktop/mobile application development, so we know the AIR runtime code very well some of the wider SDK is new to us so for example we’ve only recently got access to the source of the AIR Developer Tool, but we are being well supported by Adobe and have already built on their initial work by adding support for an Android-ARM64 platform for ANE creation.