The connectNative API would be used to connect to the app. Since we'll stop supporting NPAPI I can imagine that there will be a fairly high demand for this feature. (Chrome requires the executable to be shipped separately)

There isn't any real enthusiasm for this feature from what I've seen. There's quite a few reasons for this: * the management of the extension on AMO is way harder and full of footguns * the installation and set up of that native executable has to be done * it ties together the update of the add-on to the native executable * the native executables aren't reviewable by AMO * ... and basically I don't believe we should be installing executables on peoples computers from a browser We did a lot of work to get away from doing this in the past and its got to be a pretty good reason to go back to it.