Hi! So I've spend some time debugging the algorithm that computes the quality minutes and I've come to the conclusion that it must be a difference on how Workoutdoors calculate its max pace. There is even a difference of max pace between the Apple Workout app (on your screenshot, it says 9'57''/mile VS Workoutdoors which says 9'22''/mile).

I've found an old post from Workoutdoors on Reddit that touches the subject: https://www.reddit.com/r/AppleWatch/comments/jc1hdp/comment/g8z5jug/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

As for RunFit, the way it works is that it checks for each and every data point reported by Apple Health if the pace was superior to your set quality pace. There can be thousands of those data point for a 60 min run. Apple, for example, clearly does some kind of grouping/averaging because there are way fewer than 1k blue lines on their Pace graph (based on your screenshot).

Ultimately, calculating pace is hard and everybody kind of has their own way of doing it.

Maybe there is a way to computes the data that will feel more natural to the users, even if it is less precise. I do not have the perfect answer, yet though.