We’re redesigning the Password Manager experience from the ground up across our devices. First, we’re giving users a sneak peek at a new web app experience, including navigation and collections architecture.
Share your feedback about the new design in this 10-minute survey.
Take the survey.
Your input won’t just be heard — it’ll directly shape what we ship. This is your chance to influence the product you use every day. Thanks for your time!
@mbit @dwbit Could you please clarify whether this “new web app experience” is going to be a blueprint for the other clients?
Many of us (myself included) do not care too much about what happens in the Web Vault, because we rarely use it (only for account maintenance tasks, like setting up 2FA or KDF). But if the Web Vault design is going to be ported to the Desktop app and to other client apps (browser extension, mobile apps), then we would look at the information about the “new web app” from a whole other perspective — which will influence survey responses.
Hi @grb great question. Agreed, not a ton of users say they use web app often. We designed web app first since it has the most complex navigation structure at the moment, as well as other products and features like Admin Console, Reports, and Secrets Manager, etc. The way I’d think about this is, the navigation or exact design you’re seeing may not look exactly the same in all devices, but it ideally would feel the same or the concepts would be translated to other devices. I know that’s a squishy answer, but hopefully that helps a little! Happy to clarify further or answer any other questions.
@mbit Having completed the survey, I have concerns. You are testing for discoverability of a function (to complete a specified task), which is something that would primarily benefit new users who have no familiarity with the UI. The responses and conclusions of the survey would be very different if you allow experienced users to spend more extended time with each of the two designs — the design that allows for the most efficient work flow is not necessarily going to correspond to the UI with the highest degree of discoverability for uninitiated users. For a a critical productivity tool that will be used on a daily basis, some learning curve is acceptable, if the pay-off is more streamlined work flow for day-to-day tasks.
I have two remarks about the survey:
The first question should be: Do use collections Yes/No? If the answer is no, thank the participant and close the survey.
I wanted to complete it but I postponed it a bit too much, as it already closed 
. Will there be other surveys like this one in the future?
@ot10 We’re sorting through responses to this survey now. But we’re planning to do more surveys and posts around getting feedback on the redesign of the vault / Password Manager! I noted the feedback here that our research posts should better emphasize 1) who we’re targeting 2) which device. Thanks all!!
@mbit @Mary_Blabaum I hope you also considered my feedback about how the survey results are sensitive to the way in which the testing is designed — the A/B test administered here will not tell you which of the two concepts will be more efficient or user-friendly for experienced users, it will only tell you which concept will require less coaching for brand new users.
@grb I did see your post and it’s a good point. Out of curiosity, when you mention testing with experienced users (and given it’s a new design) what testing methods have you found that work well to capture feedback and ensure efficient workflows? I’ve done a diary study only one time, but that could be an interesting way to test a design once it becomes more “real” in a testing environment. Not sure that is possible, but something we could consider.
@mbit I recommend bringing in external help/support for the next steps (e.g. UI redesign).
They can take a more impartial approach to the whole matter and aren’t as deeply involved as the Bitwarden team. This can also help to avoid mistakes (see the last UI update) or enable the use of innovative methods to better track user behaviour and how they interact with test versions.