First of all I wanted to thank Andrew for joining in the discussion here and for keeping everyone in the loop with how things are going on the forum and by email. This year has been especially stressful with no communication from Adobe, so finally hearing some sort of information is a very nice change. I understand that Adobe likely couldn't talk about much while the deal with Harman was in the works, but boy was it frustrating when Adobe went months without even acknowledging that Android even HAD a 64-bit requirement coming up! Glad to hear about the progress towards Android 64-bit, since that's obviously the most pressing, and happy to hear that the team is gearing up for iOS support as well for whatever new requirements iOS 13 and iPadOS throw our way. It's a shame that AIR was never heavily marketed to gain more traction, since it can pull off some truly impressive results, and it will be interesting to see if some promotion and marketing can lead to more developers checking it out. For us personally, we started out as a Flash game development studio, and AIR has been instrumental for us getting our games quickly to mobile. The fantastic part is that with AIR we can start by using most of the same source code from the original games, and then build on top of that with gameplay adjustments for multitouch and platform-specific needs. Our original Flash games made heavy use of vector graphics for tens of thousands of unique assets, and with GPU Mode on mobile we've been able to use those same graphics with fantastic performance with just a handful of optimizations (GPU Mode performance is great on Android, but truly amazing on iOS with whatever development or fine-tuning was done there). As far as feature requests or roadmap suggestions, the main thing we're looking for is keeping up with the app stores' changing requirements so we can keep using AIR for our releases and maintaining our existing apps. Off the top of my head though, a few things that would be nice to have are streamlined support for packaging with Android Adaptive Icons (right now we're fudging it with sticking assets into the AIR SDK app_entry/res folders), supporting display cutouts/notches on Android (some way to retrieve DisplayCutout object info with bounding boxes and insets, since there are so many different types of cutouts on Android devices), and maybe autogenerating Assets.car for iOS if developers don't want to use XCode for that. On the Starling forums I also saw users trying to get iOS Launch Storyboards to work instead of using the huge list of Launch Images we need to use now, though there were some issues with black screens flickering before startup, so getting that process streamlined or adjusted would be nice to have at some point. In one of the older Adobe roadmaps there was also talk of adding GPU render mode for AIR Desktop, which in our case would be helpful as well for eventually making desktop releases for Steam/etc.
... View more