Integration is as easy as clicking "install app" on your Github Repo :) though you'd still have to spend some time configuring rules on our settings page if you want to fine-tune advanced settings.
Re other companies: internal devX challenges that crop up while scaling eng teams seems to be a class of problems that isn't strictly CI or source control or deployment infra, though adjacent to a lot of such tools... Maybe that's why?
It's similar in theory to Cordova but quite a bit different in practice, so that's hard to say. Its about two years old but has been growing quickly (https://npmcharts.com/compare/@capacitor/core)
Yes it hooks early on in the process startup to start measuring the time that the OS take to launch the app, as well as the app launch itself. And it stops at the end of first run loop when the first screen starts accepting touch events.
It's slightly different between iOS and Android though
So you're trying to train people to accept microphone access for apps that don't need it on the off-chance a user submits a bug report with a voice memo? I strongly recommend for the entire security ecosystem of mobile users that you don't do this, that's pretty awful. If you get your way for this "feature" then malicious apps will be able to use the exact same excuse.
I'm also concerned with such permissions and getting users accustomed to granting them for any and every app that asks for them (users don't need to be made more complacent than they are).
