The iPhone 5s’ M7 Processor As A Predictor of FitBit Steps

I’ve had an iPhone 5s since late September 2013, and wanted to examine the relationship between the daily step data it records and the daily step data my FitBit Flex records. Of course, the data from the M7 should consistently underestimate my step count, since I’m always wearing my Flex but don’t always carry my phone with me (especially when I’m working out). This post is thus fundamentally different from previous posts, because the underlying variable is really about my personal phone-carrying habits (I’ve already done a brief experiment which incorporates a step-for-step comparison of the M7 and the Flex). Nevertheless, I wanted to see how accurate the M7 data would be in predicting my daily FitBit step count.

The iPhone 5s will only hold up to 7 days worth of data from the M7, so if you fail to launch a 3rd party app which downloads and stores the M7’s data on a weekly basis, you’ll start to loose steps. I was pretty good about checking-in with the Argus app in Sep, Oct, Nov and Dec, but started to get a bit spotty in Jan and Feb. Since 9/24/13, there were 116 days for which I had daily step counts from the M7 via Argus, and the data are plotted below:

M7 vs FitBit Flex

M7 vs FitBit Flex

As expected, there is a pretty noticeable correlation, but before quantifying it I wanted to remove the outliers. I figured it was easiest to just manually remove data points for which either the M7 or the Flex recorded zero steps. The former could have been caused by my leaving my phone at home (which happened occasionally), and the latter was likely due to the periods when I wasn’t wearing the FitBit due to loosing one in the Bahamas or having my Force short out on me. Here is the plot of this data, along with a linear regression and R^2 coefficient:

M7 vs FitBit Flex Where Data Points with an X or Y Value =0 Have Been Removed

M7 vs FitBit Flex Where Data Points with an X or Y Value =0 Have Been Removed

Having removed the zeros, I also decided to remove other data points which were also clearly outliers (shown in yellow above). Not only did these points not fit the generally trend, but the dates on which they occurred were highly suspect : several of the points occurred when I was changing time zones / crossing international date lines, while others occurred on days before / after I lost a Fitbit. I figured these confounding factors warranted their removal, and their absence generated the the plot below which had a considerably improved r^2 coefficient:

M7 Data vs FitBit Data with All Outliers Removed

M7 Data vs FitBit Data with All Outliers Removed

There are several incredible features on this plot. The first is that the Y intercept of the linear regression (5257.7 Steps) is very close to the number of steps that my typical cardio workout routine (30 min on the elliptical) generates. I haven’t gathered data to support this, but I know qualitatively that I can always expect to gain about 5,000 steps on my FitBit after a 30 min workout. The M7, by contrast, gains no steps during this time as it is just sitting on the display stand streaming terrible Jason Statham movies off NetFlix. While this is seemingly a good explanation for the Y intercept, it is weakened by the fact that 1) I certainly don’t do cardio every day and 2) there must be an inherent baseline of daily of steps that my FitBit sees which my phone does not (for instance, getting dressed in the morning, showering, etc). It would be interesting, particularly for Apple or an app maker utilizing M7 data, to see what the average American’s baseline steps without their phone are, not including working out. This number could then be added back into M7 based step measurements in order to give a more accurate picture of a users real step count.

The second notable feature is that the slope of the line is almost exactly 1, which means that aside from any baseline + elliptical generated steps, the FitBit and M7 are almost spot on in their step counts. If the slope were considerably greater than or less than 1, it would be evidence that there is a systematic bias between the two measurements.

Finally, the R^2 value is decently high, which means that M7 data could probably be used to give me a rough idea of my FitBit step count on average. While it’s unlikely to be good enough to make determinations on a daily basis, if I can keep my phone on me for most of the day, I could probably bucket my weeks into high, med or low movement without having to keep track of going to the gym.


One thought on “The iPhone 5s’ M7 Processor As A Predictor of FitBit Steps

  1. […] The iPhone 5S’ M7 Predictor as a Predictor of Fitbit Steps by Zach Jones. A great post here by Zach as he explores the data taken from his iPhone 5S vs. his Fitbit. […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: