Usability issues (UX) in redesigned UI (2024.12.0)

Reading some of the earlier posts, it seems all of my main points have already been said. So instead, I will provide some additional insight into how I see things in the hopes that it will be beneficial in some way.

Optimizing the UI is an admirable goal, one that I firmly believe in. However, first and foremost, UI’s should be optimized for your users workflows. Then other aspects of the UI can be optimized within the framework of the workflows. Doing things the other way around simply trades one issue for another. This results in “the cure being worse than the disease”, as you end up with something that is very easy to use, but aggravating for many with the extra work involved to complete each task.

I understand that some users need the UI to be easy to operate without having to learn by reading or watching anything. As such, there is no one-size-fits-all solution. So you will either need to pick one type of user and code the UI for that specific use case, while alienating the rest, or you need to provide UI options to allow each individual to decide what works best for them.

Whenever my development team implements changes to existing features, including the user interface, we always implement a setting that defaults to continue working the way it always has. Anyone wishing a different experience, now has the option to tweak things. This prevents a lot of confusion and upset from the existing user base, and has served us well over the years. We only break this rule in extreme circumstances.

If you want to simplify the UI setup, while providing various options, then how about implementing a setting to specify what type of user they are. Do they want a simplified UI, the most optimal workflows, middle of the road or Jedi master who can customize their own UI configuration?

I have seen some browser extensions bring up a webpage after installation. Perhaps you should utilize this in future when making big changes. It would be very useful for informing or training the users on big changes. Another idea would be to use it to implement a setup wizard. This wizard could ask a few targeted questions to setup the browser extension to the individuals needs. Such as asking them what their use case is (basic password management, use of security keys, etc.), show UI pictures and have them pick which they like the most, etc.

On a side note, I am struggling with arthritis from heavy keyboard and mouse usage. So while a few extra clicks to access a feature may not seem a lot to you, they can have a huge impact to my quality of life. Especially for password and form filling as I use that throughout my day, 365 days a year. Even a few clicks per task, can really add up. Currently, a good day for me is when I’m done and don’t have more pain than when I started. Your awesome password manager is one of my most used tools, so any workflow optimizations are a huge help to me.

Thanks for adding a setting back in to allow us to more easily access the copy username and copy password feature. That is a huge help to me and my fingers. The biggest thing I am still missing is more keyboard shortcuts, especially for form filling. Keyboard shortcuts make it really easy for people such as me, to access features via voice commands. Attempting to control the mouse be a voice can be very frustrating and time-consuming, especially for smaller buttons such as your new form fill button.

I just double checked, and it seems the keyboard shortcut, that I was so desperately needing, has been completed. Thank you so much! I think we need the better feedback mechanism, unless I missed something. It have been nice to receive a notification when a feature request I voted on/reply to was completed. :wink:

2 Likes