Analysis of Apple Watch running data
31–40 of 171 posts
Re: Analysis of Apple Watch running data
#32Earlier quoted context omitted.
> I would guess that it’s software, with the author, if for no other reason than I’d be surprised if Garmin were all that much better at putting GPS in a tiny housing than Apple. After "you're holding it wrong", anything seems possible. But yeah that does seem more likely to be software, it's a surprisingly difficult and fuzzily-defined problem.
Weird hill to die on with Apple. That's a 10 year old issue with an iPhone 4, said by a CEO that is long dead. They gave everyone free bumpers, because sweaty fingers would close the antenna gaps. The statement was true, the gaps were placed where they were expected to least affect the grip. What exactly would you expect in this case? The messaging worked. If your iPhone 4 was having signal issue, consider readjustin…
> This is not the nightmare scenario that non-iPhone users made it out to be. Apple haters, like any group of haters are a silly bunch.
What nightmare scenario did I imply? I think you're being a little overenthusiastic here. It was just a funny example to show that Apple isn't above screwing up hardware stuff/radios from time to time.
Re: Analysis of Apple Watch running data
#33Re: Analysis of Apple Watch running data
#34I wonder if at some point Apple reduced the sampling frequency of the gps position to save power? Since this sounds pretty important to the guy, I would buy a Garmin watch or similar to compare to and run with both. I also suspect one of the challenges here is that taking a lot of corners like in an urban environment might result in rounded paths — like if you ran around a rectangular city block it ends up being logg…
Re: Analysis of Apple Watch running data
#35Assuming it is an aerboic work out, what's the difference if the watch tells you that it's 9.6k, 9.7k, or 9.8k? The only thing that I need to know the accurate distance is to train a specific event, e.g. mile run, 5k, or 10k. If I train to run a mile within four minutes, all I need to know is to run 60s for each 400m on track.
Re: Analysis of Apple Watch running data
#36Earlier quoted context omitted.
> I would guess that it’s software, with the author, if for no other reason than I’d be surprised if Garmin were all that much better at putting GPS in a tiny housing than Apple. After "you're holding it wrong", anything seems possible. But yeah that does seem more likely to be software, it's a surprisingly difficult and fuzzily-defined problem.
Weird hill to die on with Apple. That's a 10 year old issue with an iPhone 4, said by a CEO that is long dead. They gave everyone free bumpers, because sweaty fingers would close the antenna gaps. The statement was true, the gaps were placed where they were expected to least affect the grip. What exactly would you expect in this case? The messaging worked. If your iPhone 4 was having signal issue, consider readjustin…
You're welcome to patronize whoever you want as a customer, but from a business perspective this is the sort of behavior that will be heavily scrutinized during antitrust hearings.
Re: Analysis of Apple Watch running data
#37Re: Analysis of Apple Watch running data
#38A friend has both a whoop and an Apple Watch. One or both of them are wrong. He almost never get consistent results between the two, Apple is almost always higher than whoop (avg. heart rate for a given period) it’s a bit depressing.
Re: Analysis of Apple Watch running data
#39Did OP mention if the scripts are published somewhere?
Re: Analysis of Apple Watch running data
#40A friend has both a whoop and an Apple Watch. One or both of them are wrong. He almost never get consistent results between the two, Apple is almost always higher than whoop (avg. heart rate for a given period) it’s a bit depressing.
This also lowered the avg HR for the workout on the whoop, as you noted. Happy to share an example comparison graph if you’re interested, just reach out.
For what it’s worth, I ended up cancelling the Whoop this month after trying twice to engage with their data team.