IssueTracker

Component used: Macrobenchmark Version used: 1.2.0-alpha14

The current FrameTiming metrics are statistically good.

frameDurationCpuMs P50 11.4, P90 16.2, P95 17.6, P99 31.5 frameOverrunMs P50 -0.6, P90 2.1, P95 5.3, P99 356.5

But apps often measure simpler % of jank frames.

Would it be worth having a similar Jank metric, that might match Firebase and Play Store Vitals.

https://support.google.com/googleplay/android-developer/answer/9844486

Understand your app's data

On the Excessive slow frames page, you'll see details about the percentage of daily sessions where users experienced more than 50% of frames missing the device’s drawing deadline. User interactions with your app should run at 60 frames per second without any dropped or delayed frames.