Yes there is
in Release Notes for Adobe AIR 22
System level Flash Player support for AIR desktop applications
Starting in AIR 22, applications that play swf content via the HTML control (WebKit) will now load the system level NPAPI Flash Player provided by Adobe (https://get.adobe.com/flashplayer). If this plugin is not available on the system, the end user will be prompted to download and install the plugin from Adobe.
Which means off course that if you build with AIR 21 then there you still have an embedded Flash Player 21 without the need to install it on the system
yes definitively possible to use either NW.js or Electron
and then would it be better?
it depends ...
even if I would push for using AIR first there are many cases where Electron could be better
- case of need to use
nw-flash-trust because you load a local SWF from
- case where it would be easier to support Linux (latest plugin, 64-bit )
- case where you need a recent HTML engine for HTML stuff next to the SWF stuff
- case where you want to reuse electron-builder because you do not want the headache of building your own installer
and others where it would not be better
- case of wanting to be "small", Electron apps can go over 100MB in file size
- case of memory usage, Electron app is running a full-featured chrome browser and chrome is a memory gluton
- case of wanting to use "drag n drop", I do think it is more usable/advanced in AIR
- out of spite not wanting to use anything related to chrome
Now all that said, the simpler is just to make a couple of prototype and see which "way of doing" fits your need better.
In my case with the idea of an open source AIR Browser some of the goals are to make the solution easily reusable to others wether in packaging options, branding, etc. but also be honest about the pros and cons.
Electron and other NW.js are perfectly good solutions too, but I just want really bad to do it with AIR just for the beauty of it: saving SWF with Flash tech, and yeah out of spite too.