The performance monitor plugin is most useful when it reflects the full set of performance information that react-native-performance can produce. Today, users can inspect measures, marks, and metrics, but they cannot rely on the panel as a complete view of their app's performance activity. That creates blind spots during investigation, especially for startup and network-related analysis.
Current State
The plugin currently exposes only part of the react-native-performance data model.
- Measures, marks, and metrics are shown in the panel.
resource entries are not surfaced.react-native-mark entries are not surfaced.mark.detail payloads are not preserved and displayed consistently.
As a result, users do not get a complete picture of the entries emitted by the library, and some useful context attached to emitted entries is lost before it reaches DevTools.
Expected Outcome
The plugin should present a complete and trustworthy view of the react-native-performance data that matters to users.
- All supported entry types that are useful in DevTools should be surfaced in the panel.
- Entry payloads that the library exposes should be preserved and visible in the UI and export flows.
- Native startup-related entries should be visible as first-class data, not hidden behind missing coverage.
- Users should be able to treat the panel as the primary place to inspect performance data emitted by the library.
Resolution Summary
The performance monitor plugin should close its data coverage gaps so users can inspect the full relevant output of react-native-performance, including missing entry types and missing payload details.
The performance monitor plugin is most useful when it reflects the full set of performance information that
react-native-performancecan produce. Today, users can inspect measures, marks, and metrics, but they cannot rely on the panel as a complete view of their app's performance activity. That creates blind spots during investigation, especially for startup and network-related analysis.Current State
The plugin currently exposes only part of the
react-native-performancedata model.resourceentries are not surfaced.react-native-markentries are not surfaced.mark.detailpayloads are not preserved and displayed consistently.As a result, users do not get a complete picture of the entries emitted by the library, and some useful context attached to emitted entries is lost before it reaches DevTools.
Expected Outcome
The plugin should present a complete and trustworthy view of the
react-native-performancedata that matters to users.Resolution Summary
The performance monitor plugin should close its data coverage gaps so users can inspect the full relevant output of
react-native-performance, including missing entry types and missing payload details.