Peloton and Qlik: The Apple Watch Conundrum

By David Freriks, Emerging Technology Evangelist / Partner Engineering at Qlik

Part of being a data professional is pretty simple... you notice when things don't add up. In my case, my Apple Watch and my Peloton aren't on the same data page when it comes to calorie tracking. In this blog, I'm going to deduce why I think it's happening and use Qlik and the Peloton/Apple metrics as the data to support my conclusions.

Let's start with a leisurely walk with my dogs, tracking the exercise with my Apple Watch. To be clear, the Apple Watch was tracking me, not my dogs.

Basic Stats:

  • 1.71 miles
  • 28 minutes, 92 bpm HR

Did I break a sweat – no.

Did I get my heart rate up – no, not really.

Did I have a rocking playlist going – heck yes, I did!

According to Apple Watch, I burned almost 400 calories and 320 active calories.

This is Gandalf... he very much enjoys the walks.

Later, that day I finished a Peloton ride with Emma Lovewell. It was a brutal, high-power, beast-mode workout. Ninety resistance at max, legs burning, heart racing and sweat pouring out for the entire 30 minutes. Again to be clear that was me, not Emma.... Let's compare the results:

  • 388 Active Calories, 468 Total Calories, ~130 Avg HR
  • 371.1 kJ of Output
  • 30 Minutes, 10.6 miles
  • 84 Cadence, 52 Resistance

So, according to Apple, had I spent another five leisurely minutes walking the dog, I would have outperformed the crushing Peloton ride. What does this mean? How does this happen? Who's right or wrong here?

Using my powers of intuition, I have formulated some theories that I will attempt to prove with data. My supposition:

  1. Apple Watch doesn't care how hard your ride is; it's purely counting Cadence, and some factor of Heart Rate, without consideration for Resistance or Output
  2. Peloton drives its Calorie counting by Output and Heart Rate

So what? What that means is that, if you get on the Peloton and bike superfast at low Resistance and generate a low overall Output, Apple Watch will reward you with a large number of Calories burned, even though it was an easy ride.

How can I confirm or invalidate this conclusion... Why, by using data and the power of Qlik Sense, of course! Oh, and I have to exercise.

To test my theory, I took a ride based on my assumptions of a higher cadence and lower resistance to see what results will yield:

Same calories from Peloton (480). But now, Apple Watch gives me 330 active calories and 413 total calories – a variance of 45% between Peloton calories and Apple Watch active calories.

OK – that's pretty surprising. Let's look at the comparable metrics between the two rides:

Ride 1: Peloton Calories – 480, Apple Calories – 468, Output – 371 kJ, Resistance 52

Ride 2: Peloton Calories – 480, Apple Calories – 413, Output – 309 kJ, Resistance 47

Hmmm, with this sample set, for the same 30 minute ride, it appears my suspicion is WRONG! Apple seems to better estimate calories based on my actual output from the Peloton bike.

But, I still can't reconcile the Apple Watch variance between a casual dog walk and a hard Peloton ride. However, I do think the Apple Watch is performing a more accurate estimation of the calories burned while biking on the Peloton.

So, what does this all mean? I'm not sure! I feel much better about the Apple Watch for Peloton tracking, but have no confidence in the numbers it produces for walking. Love to hear some theories on what might be going on.

At the end of the day, I'm more active than I used to be, and that's a good thing. Gandalf also agrees; he thinks it might be fun if they had an Apple Collar, too.

Part 4 of the Blog with Dalton Ruer is coming next, and it's going to be very cool. He's got a wicked cool mashup to show off, and he'll explain how the Qlik engine provides the ability to create an analytics website.

In @dlfreriks third blog post, learn how he used #QlikSense to compare his exercise performance as reported on the #Peleton & #AppleWatch

Get ready to transform your entire business with data.

Follow Qlik