Leave it to Apple to write off what many see as a bug or a decrease in functionality as a “feature.” Maybe it’s part of the reality distortion field (RDF) that we briefly mentioned yesterday, but Apple is definitely stretching things quite a bit this time around.
When the Apple Watch first started arriving at customer doorsteps, users were able to obtain accurate and consistent heart rate readings. In fact, the Apple Watch was shockingly consistent, delivering readings every 10 minutes. However, following the release of the Apple Watch 1.0.1 update, customers began to notice that the readings were no longer recorded every 10 minutes, and in fact, there was actually no rhyme of reason as to when and how the readings were recorded.
Apple Watch heart rate readings before (L) and after (R) the 1.0.1 software update (Source: twisted-pixel)
Needless to say, users flocked to Apple’s Support Community to voice their frustrations. As of now, the original thread discussing the matter has grown to 197 replies and has been viewed nearly 15,000 times.
Rather than admit that this was a bug introduced with the 1.0.1 update or give the standard response that it is “looking into the matter” (as was the case with the recent iPhone texting bug), Apple is doubling down and denying that this is an actual bug. In fact, it’s being called a “feature” of the Apple Watch.
Apple’s support page that describes the functionality of the Apple Watch’s heart rate sensor was recently updated this morning to state, “In addition, Apple Watch attempts to measure your heart rate every 10 minutes, but won't record it when you're in motion or your arm is moving.”
Prior to this morning, the latter half of the statement was absent from Apple’s description of the heart rate sensor. Given that this is Apple we’re talking about, we’re likely never to receive a full-fledged response from Apple on why this feature has been neutered with the 1.0.1 update.