Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Right, but only for setup. The previous implementation would work if you went on a walk without your phone.




I don't see why that's a problem. They can still record the data on the watch and then when it reconnects to the phone it can send over the data for the analysis. Same as how they store metrics on the watch until it reconnects to a phone to send to the Health app.

It's a problem because it requires your phone. Consider places where phones are not permitted: your Apple watch gets a pass. So O2 sat is available in real time wherever you are if you have previous versions of the watch, which is not the case for the current version.

I think you misunderstood what I said. I am saying I don't see how that's not a fixable problem. How often do you need constant O2 readings? What places are phones not permitted but Apple Watches are? Seems like a highly niche problem to me. Obviously not as good as the original, but you should still get a constant histogram once reconnected.

I completely understand what you said. It is NOT a fixable problem.

>How often do you need constant O2 readings?

You're missing the point: the fact you have the freedom to get as many readings as you like is fundamental. Who are you to decide how often I want/need them?

>What places are phones not permitted but Apple Watches are?

1. Among others: courtrooms (phones must be turned off, but no restriction on Apple Watches). Source: my appearances as an expert witness in courtrooms around the country. 2. Classrooms (phones off/Watches fine) 3. Theaters 4. In a dental chair and many, many more places.

>Obviously not as good as the original, but you should still get a constant histogram once reconnected.

But what if I can't reconnect or don't want to?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: