You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently upgraded our SDK version to 5.12.0 in order to take advantage of profiling. During our initial test run we were able to add component tracking on a higher level component using the withProfiler hook and analyze the results with a small subset of users.
We are now interested in collecting device level metrics such as battery, CPU, and memory usage. We saw this feature is available for Mobile App Profiling, but not yet for react-native. We also had a chance to speak to one of your solutions engineers, and they showed us how we could potentially use custom instrumentation and custom metrics to achieve the desired result. However, for our organization they are likely to push-back on this custom instrumentation and want to leverage something more "out-of-the-box".
Ultimately, this feature would enable us to complete AB testing of our app and see how changes are impacting different devices and operating systems.
In addition, it would be great to track the number of re-renders that occur on different pages (thought I would throw it in there as a nice to have!).
The text was updated successfully, but these errors were encountered:
Hi @KatePetersonFD, thanks for writing in and for your interest in Profiling and this feature. We're currently working on mixed Profiles (JS + iOS/Android native Profiles) and want to explore adding Profiling CPU/Mem metrics at a later time.
We recently upgraded our SDK version to
5.12.0
in order to take advantage of profiling. During our initial test run we were able to add component tracking on a higher level component using thewithProfiler
hook and analyze the results with a small subset of users.We are now interested in collecting device level metrics such as battery, CPU, and memory usage. We saw this feature is available for Mobile App Profiling, but not yet for
react-native
. We also had a chance to speak to one of your solutions engineers, and they showed us how we could potentially use custom instrumentation and custom metrics to achieve the desired result. However, for our organization they are likely to push-back on this custom instrumentation and want to leverage something more "out-of-the-box".Ultimately, this feature would enable us to complete AB testing of our app and see how changes are impacting different devices and operating systems.
In addition, it would be great to track the number of re-renders that occur on different pages (thought I would throw it in there as a nice to have!).
The text was updated successfully, but these errors were encountered: