It doesn't matter which sensor is involved.
Design team decided that this UX is not desired, not for the default Clock app. 3rd party developers are allowed to implement this in their app if desired (even though I think the platform doesn't offer a way to do that, yet, right?)
It doesn't matter which sensor is involved.
Design team decided that this UX is not desired, not for the default Clock app. 3rd party developers are allowed to implement this in their app if desired (even though I think the platform doesn't offer a way to do that, yet, right?)