Ah right, thanks. So am I right in thinking that every Android app dev using Construct has downloaded this plugin pack, otherwise the back button on an Android device wouldn’t work while their app was running - not to mention it wouldn’t pass Android’s basic app quality standards?
I wouldn't say that it wouldn't pass Android's basic app quality standards. Because, those are all optional features. For example, the Back Button from the Cordova InAppBrowser is a native app feature but still is an optional event trigger.
Because, that plugin only lets you control the InAppBrowser, but the InAppBrowser is technically is the browser you are running your game. So, it's there, but you just can't control it. Unless you use the native Cordova plugin to control it, which is called Cordova InAppBrowser here.
Basically, you can still make an App without a Back Button event trigger. That is just dependent on your app, if it needs it.
That's why Construct doesn't necessarily have to implement this. Hence, 3rd party plugins are made, for game developers who might need them.
Although, Construct Team kind of have to responsibly implement this in the future, for mobile games to be easier to work with on mobile. Especially since this is a subscription software.