FR: Add screentrace with custom name and start / stop methods rather than per viewcontroller

[shamilovtim]

Feature proposal

• Firebase Component: Performance

A React Native "screen" can be anything and doesn't have to be a ViewController. In fact, most everything in React Native runs in one ViewController. Thus I am proposing an API:

ScreenTrace.start('FirstScreen'); ScreenTrace.stop('FirstScreen');

ScreenTrace.start('SecondScreen'); ScreenTrace.stop('SecondScreen');

Allowing users to use this approach might override the current approach of going per-ViewController, so maybe there's also a boolean or switch to move to user controlled ScreentTaces.

[kim-f]

Hi Timothy,

Thank you for reaching out to the Firebase Performance team, and for suggesting a way to improve the usefulness of our product! I've filed a detailed feature request in our internal tracking for discussion and potential prioritization. I appreciate the level of detail you've included within this and your similar request for our Android SDK–the context you've provided will be very helpful to us as we consider what we should focus on building next.

Thanks again, Kim