Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Double password input speed by using both sides #995

Closed
ln2max opened this issue Oct 22, 2022 · 2 comments
Closed

Double password input speed by using both sides #995

ln2max opened this issue Oct 22, 2022 · 2 comments
Labels
wontfix This will not be worked on

Comments

@ln2max
Copy link

ln2max commented Oct 22, 2022

The password input process currently only uses one side of the device. As a result, at each stage of the search tree, the user can choose from only 3 possibilities.

However, the Bitbox02 has touch sensors on both sides of the device. By using the other sensors as well, the user would be presented with 6 choices at each step of the input tree.

This would reduce the time to reach the root of the tree to approximately half, dramatically speeding up the somewhat cumbersome password input process.

This might make randomized input (#744) practical and reduce the need for a more complicated process (#743).

Backspace and character modal selections (ABC, abc, 123) would then happen by simultaneous presses on both sides of the device (as is currently done for the confirmation press).

@jadzeidan
Copy link
Contributor

Hey @ln2max, thanks for the input. The password input process is a balance between increasing complexity to acheive speed and vice versa. As an advanced user what you described might be more efficient, but for other users that aren't as advanced or aren't as dexterous it may make the process harder. However if we find time to improve the password entry one day, this proposal is something we could experiment with.

@benma benma added the wontfix This will not be worked on label May 29, 2023
@benma
Copy link
Collaborator

benma commented May 29, 2023

Closing this as it is unlikely we will go this way. Our newest experiments change the way the keyboard is switched but the top bar is still needed for it.

@benma benma closed this as completed May 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants