I have a suggestion for the UX of the dock.
Currently, the default behavior of the rotational knob (i.e. the encoder) as it pertains to the home screen is when you spin it clockwise, it selects the item below the highlighted entry. The issue is, that feels backwards because you’re mixing UI/UX metaphors. While you have added the ability to reverse the direction, even that is somewhat confusing UI/UX-wise for the same reason.
I’ll explain in more detail.
Specifically, in the settings list (which ironically isn’t affected by that new setting), it works as expected. You are moving the selection up and down accordingly. You roll it up, it goes up. You roll it down, it goes down. This feels natural.
However, on the ‘home’ screen, the reason why the default feels backwards is you’re currently treating the knob as if it’s moving the screen contents up and down, which makes sense, except you’re also showing a ‘selection border’ implying you’re moving the selection up and down, just like in settings. Except unlike there, not only does the selection border not move–which already feels awkward–but when you’re thinking it should move up to select the previous item, instead it appears to move down to the next item, because what you’re actually doing is moving the screen contents up behind the selection border, not the selection border itself.
And that’s the disconnect! You’re mixing metaphors. You’re showing a selection border, but you’re acting on the screen contents behind it. Even with the new setting which does address the ‘wrong direction’ feeling, it will still never feel ‘natural’ since the visual of what you’re seeing is always in dissonance with what you’re actually interacting with.
The good news is it’s easy to address, depending on which you prefer… moving the selection border or moving the screen contents.
Starting with the former, moving the selection border… just make it work like settings! You literally move the selection border up or down. If it reaches the top or bottom and you keep scrolling, then just like in settings, new items come into view shifting out old ones. But if you’re just moving between the three items already on screen, then only the selection border moves between them, not the screen contents itself.
The ‘selection-based design language’ works best for non-animated screens since what’s ‘jumping’ is just the selection moving to the previous or next item. It’s a highlight. It actually feels weird when you try and animate a selection because a ‘selection’ is not a ‘thing’ per se. It’s a decoration of another thing… the selected item. That’s why animating selection indicators feels weird, and isn’t usually done (except maybe fading, but almost never moving.)
The second approach to address the dissonance is to move the screen contents themselves, again, what you’re currently doing, but with more intuitive/consistent visuals.
First, you need to remove the selection border because if you see a selection border, you think you’re acting on it, not the contents behind it. This does mean you would have to indicate which is the current item a different way. Maybe an arrow/triangle off to the side, or maybe making the focused item larger than the non-focused ones showing which one is active.
Better yet, this would be a perfect place to add animations as again, you’re moving the screen contents up and down, which feels natural when animated. That’s what made the iPhone so revolutionary. Push the screen up and it animates up. Pull it down and it animates down. Here, you’re just using the knob instead of touch.
More importantly, jumping (i.e. non-animated) works better for selection-based interaction (which is why it feels normal in settings), but it does not work when moving screen contents. Try it yourself on your computer… disable ‘smooth scrolling’ in your browser and you’ll see just how uncomfortable it feels.
In contrast, animating the screen just ‘makes sense’. Roll the knob up, the screen slides up. Roll it down, the screen slides down. No selection ring needed (as mentioned, if there was one, users will again think that’s what they’re interacting with, not the screen contents.)
Anyway, just some friendly feedback from someone who loves UI/UX and who does this kind of thing for a living. Hope it helps, or at least gives you some food for thought.