Mobile Vitals for UI events transactions

[romtsn]

Report slow and frozen frames for recently added UI events transactions on iOS and Android.

[marandaneto]

As I understood, this is already done on iOS for every transaction, since they don't need the instance of the view such as activity.

[bruno-garcia]

Moving to the sentry-java repo since iOS already has this.

[philipphofmann]

As I understood, this is already done on iOS for every transaction, since they don't need the instance of the view such as activity.

Yes, indeed.

[adinauer]

Would probably need to replace ActivityFramesTracker with something based on choreographer.postFrameCallback(frameCallback) similar to what is done here https://github.com/getsentry/sentry-java/blob/730095684bb732a0a7d0cc88d3c3b913a08d7cfe/sentry-android-integration-tests/sentry-uitest-android-benchmark/src/androidTest/java/io/sentry/uitest/android/benchmark/util/BenchmarkOperation.kt#L142-L166

This would then also be helpful for FPS Mobile Vitals.

[markushi]

This is already done for Profiling, as frame metrics are already collected on a frame by frame level. It probably makes sense to refactor the existing ActivityFramesTracker and make it's collected data available to both Profiling and Transactions.

[markushi]

It could make sense to re-use the frame-by-frame profiling collector in case there isn't too much of an overhead. (SentryFramesMetricCollector)

[romtsn]

this is superseded by mobile starfish and will be tackled by the mobile interfactions module