Add generator and copy buttons to password field in New Send screen on Android

The Send feature is great, but I’m always at a loss what to about the password. I understand the actual send is encrypted. Though, I always prefer to add a password in case the link gets intercepted.

Currently, I have to remember to generate a password first, copy it, save it somewhere else. Intuitively, I expect to see the generate password icon next to the password entry field. Once I save the Send, I better have saved the password somewhere else or the password is gone.

The menu on the saved Send item has Delete password. The menu should also have Copy password. Without the Copy password menu item, I have to manually save the Send item’s password and correlate it to the name of the Send item for future use.

I currently use a Note with the Send item name and it’s password next to it. Very tedious and inconvenient, especially since I am already in the BitWarden secure client.

@MalibuDave42 Welcome to the forum!

Yes, and when you first create a Send, there is such an icon there, along with a copy icon and a visibility toggle:

 

So is your request to implement these three buttons (password generator, and password copy, and visibility toggle) also in the “Edit Send” view?

Hum, I don’t see that on the android version.

Yes, the generate password icon next to the password entry field. And, be able to copy the password saved with the Send for password use later.

Thanks for clarifying. I updated your topic title to be more descriptive (old title was: “Send - access to the item password”; new title: “Add generator and copy buttons to password field in New Send screen on Android”). I have also changed the topic’s operating system tag from “os:windows” to “os:android”.

Hm. The desktop app also seems to lack the generator and copy button. (but the desktop app also seems to have the old UI there, still…)

For Android – BTW, can someone check iOS as well? – as it uses the new UI already for Sends, this maybe could be reported as a UI/UX bug as well. (for everyone who might report it on GitHub: please, don’t let it look like a feature request there :wink:)

There now is a GitHub issue (i.e. bug report) about that: