03-25-2018 09:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-25-2018 09:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I have a watch face where an area can be tapped to go to a second page. Very often, instead of a tap I get a swipe up and the Today data loads, unloading the watch code. This is very annoying and it appears that the swipe distance is way too short, on the order of a few pixels.
On the flip side, swiping down on the Today data requires a very long swipe that does not always take and have to do it multiple times before it works.
Swipes on the watch face display should have to be more deliberate to avoid unnecessary unloads of the program when someone just wants to tap the display to get more data.
03-27-2018 16:38 - edited 03-27-2018 16:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


03-27-2018 16:38 - edited 03-27-2018 16:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I checked with the design team.
20% of the top and bottom of the screen is used for the swipe gesture detection.
The swipe amount is 20 pixels.
For clock faces, you should probably just avoid touch events within those areas if you're triggering the swipe gesture too frequently.

03-27-2018 19:20
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-27-2018 19:20
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Well, 20 pixels out of 300 is an awfully small distance and hence the unintended swipes.
Perhaps instead of having to avoid the swipe zones on clock faces, the design team could increase the swipe amount to something bigger than the head of a pin, say 25% of the vertical screen resolution (60-75 pixels).
Even inadvertently touching the screen sometimes brings up the Today data.
