The most important thing is the PURPOSE of a functionality. So, what is the purpose of
- introducing the gestures,
-- switch on the light (and this the reason the gesture settings are in display group)
-- inform about exit from sleep for watch face (user can't see this but he can see only the light on)
-- generally, something connected with situation when USER wants to see something on watch, from the user's point of view: gesture = light on ONLY
- limitation of gestures during activity
-- the light shouldn't be on
-- during activity watch face is all the time in the high power but gesture calls onExitSleep :-) (but not the light on)
-- generally, user shouldn't see anything (black screen) just because activity is in background...
You are right only if we assume that switching on the light by gesture is quite different then making it by pressing the button. For me it's true exactly the same thing so.
Everything depends on the situation:
- for me and my user seeing qr code (even during activity in the background) its good to have gesture because I don't have to press button, screen (e.g. it is very cold outside and I have to take off the gloves)
- for tactic activity or real war activity watch should ask 10 times before it switch the light on
- for most user it doesn't matter :-) and we waste our time for showing our own opinion :-)
Btw. I have the goals alerts ON and I've never seen it during activity although many times I made the goal. And if we're treat alerts as light on they run in the different way.
The most important thing is the PURPOSE of a functionality. So, what is the purpose of
- introducing the gestures,
-- switch on the light (and this the reason the gesture settings are in display group)
-- inform about exit from sleep for watch face (user can't see this but he can see only the light on)
-- generally, something connected with situation when USER wants to see something on watch, from the user's point of view: gesture = light on ONLY
- limitation of gestures during activity
-- the light shouldn't be on
-- during activity watch face is all the time in the high power but gesture calls onExitSleep :-) (but not the light on)
-- generally, user shouldn't see anything (black screen) just because activity is in background...
You are right only if we assume that switching on the light by gesture is quite different then making it by pressing the button. For me it's true exactly the same thing so.
Everything depends on the situation:
- for me and my user seeing qr code (even during activity in the background) its good to have gesture because I don't have to press button, screen (e.g. it is very cold outside and I have to take off the gloves)
- for tactic activity or real war activity watch should ask 10 times before it switch the light on
- for most user it doesn't matter :-) and we waste our time for showing our own opinion :-)
Btw. I have the goals alerts ON and I've never seen it during activity although many times I made the goal. And if we're treat alerts as light on they run in the different way.