We are planning an update on the mobile app's gait panel to improve the operation efficiency.
The existing design:
It requires two operations to change to a specific gait and switch eyesight between the mobile app and the robot. The app combines the gait and direction and sends the command, which delays the robot's control of the target destination.
The update we are proposing:
This design will make it easier for the robot to use different gaits and control the direction without requiring one to look at the phone app.
Please let me know if you have any suggestions or comments before we make it final.
Here's a poll on YouTube:
https://www.youtube.com/post/Ugkx5yx8FoslO2u-JV8_3WSIfjnN96Oa5ZCR
I would rather select a gait with a button (not a slider), select a speed with a slider and use directional buttons to control direction of the locomotion.
So, no, I would not like this change. Instead, I would like to have the UI be changed as I just described. Right now the speed and gait are on the same control - those should be separate controls.
I was thinking something similar last month, but just with arrows and no text. Higher arrows indicate higher speed. The "step" gait is only useful for turning left and right, so I suggest triggering the "step right" and "step left" gaits after the user has switched to "stand" / "pause". And the buttons do not need text to be understandable, I quite like the D-pad control layout. Here is a rough sketch of what I would consider most intuitive:
Or, essentially the same as your setup, just with really big left and right buttons:
Or you could do your setup but make them function as horizontal sliders instead of buttons that one needs to tap. Perhaps that is already what you had in mind?