When clicking “Sync vault now” (Settings → Vault options), there is no visual feedback indicating that syncing has started. It makes the user doubt whether the interaction (clicking the button) has actually happened, and causes friction.
The only current indicator that the request to sync has been received happens after sync completes, in the form of a toast (popup). This is good, but it is not enough.
A simple spinner animation (such as the one shown upon opening the extension) would help a lot.
Jumping in here, for me, the sync usually completes in just a second or two, but I still find the lack of immediate visual feedback a bit confusing. Even with a fast sync, it’s not always clear if the click registered, especially if there’s no spinner or loading indicator. Some sort of quick visual cue would definitely improve the experience.
The timestamp is updated 2 seconds after clicking the button. That is an entirely inappropriate amount of time to wait for feedback on a button click. A widely-accepted rule of thumb in UX design is that feedback must be given within 1 second in order to not break a user’s flow.
I just tested it, at least for me it takes about one second.
I am no expert in UI design, but in my opinion the current implementation is sufficient, especially with the big green banner “Synchronization finished”.
It seems clear to me that the time depends on network conditions. I’m located in Europe and using the US server, so the additional latency is probably to blame.
The problem is that you don’t know if your button click was even successfully received until the whole job is done. I would challenge you to work on a device where all UI interactions take 1 second before they show you any visual feedback. I promise you, you will tear your hair out within the first five minutes.
All we’re asking for is some kind of UI acknowledgement that the button has been clicked. Like the little spinner animation that shows for a moment when you click to open the Bitwarden browser extension.
Yes, I get that, but we are not talking about “every click all day long” but a feature that is used not even daily. So in my opinion this would be a nice change but not with a high enough priority to fix it very soon.
If implemented, it could also be used for other actions that may have a perceptible time delay before completion (e.g., uploading files, importing vault data, etc.).
Always the fastest way to get a new feature implemented!
Have you read the guidelines for how to contribute? I don’t see your proposal in the Discussion section. I suppose this PR is simple enough that they may not need a formal proposal before reviewing it, though.