Menu Button goes to last widget in list instead of first

It may seem counterintuitive, but UP takes you to the previous item (i.e. moves you up one spot in the list), and DOWN takes you to the next item (i.e. moves you down one spot in the list), not unlike the up arrow and down arrow on a computer keyboard. (Note that this is the opposite of how it would work if you were swiping a touchscreen. Usually, swiping a touchscreen has the metaphor of moving the content in certain direction, while pressing a directional button has the metaphor of moving a selection/cursor *through the content*)

But whether you're pressing a button or swiping, the idea is that the watchface and widgets are part of a circular carousel. And pressing UP or DOWN changes the item that's currently selected in the carousel.

4871257 said:

It would make sense for the menu/up button to take you to the top of the menu, and the down button to take you directly to the bottom.

It can't work this way because you have to define what happens with a list with multiple items (not just a top and bottom item) in a consistent way.

The part that may be initially confusing is that the watchface is part of the carousel or "widget loop". But as mentioned in the comments above, if it was implemented any other way, it would be self-contradictory or unintuitive,

For example, say you have a watchface and three widgets:

- Watchface

- Widget 1

- Widget 2

- Widget 3

If you start at the watchface and press UP, the watch could take you to Widget 1 like you said. But then what should the watch do when you press UP again?

A) Take you to Widget 2? In that case, UP is really moving you down the list (or the list is in the opposite order that you'd expect).

B) Take you to Widget 3? In that case, how do you get back to the watchface? The only way this works is if watchface is not part of the carousel.

C) Take you to the watchface? But then what happened to Widgets 2 and 3? With the carousel metaphor, it doesn't make sense to return to original page after pressing the same direction button fewer times than the number of items (in this case, 4)

I really do think the unintuitive part here is that users may assume the watchface is not part of the widget loop. But that would make navigation more difficult.

But if the watchface was not part of the widget loop, then the only way to get back to the watchface would be to press BACK. This is more complicated than the existing metaphor or the "carousel", where pressing UP or DOWN enough times eventually brings you back to your original page.

In other words, you can think of the carousel / widget loop as looking like this:

...
- Watchface
- Widget 1
- Widget 2
- Widget 3
- Watchface <======== start here
- Widget 1
- Widget 2
- Widget 3
- Watchface
...

A) If I start from the watchface and press UP 8 times I see these pages: (3, 2,1, Watchface, 3, 2, 1, Watchface)

B) If I start from the watchface and press DOWN 8 times I see these pages: (1, 2, 3, Watchface, 1, 2, 3, Watchface)

If that isn't intuitive, that's fine, but the challenge is to define a different way that's more intuitive and consistent. (i.e. what would you expect to happen in the above two cases?)

As far as I can tell, the only two ways to do that are:

1) Make UP and DOWN move through the list in the opposite directions from what you'd expect. (The current direction of movement for each button for the widget loop is the same as the directions of movement for menus and data pages, so it's all consistent, and nobody ever complains about the menus or data pages afaik)

2) Remove the watchface from the carousel. (But this actually makes things more complicated and less intuitive, in my opinion.)

I have to admit it took some for me to get used to this, too. I think the concept of the watchface and the widgets being part of the same loop threw me off.