A lot of people like the Auto-type feature on the roadmap, but it doesn’t seem like it will be implemented anytime soon. However, on mobile devices, displaying password as QR codes appears to be a bit easier. Since some computers have QR scanning platforms installed, these users could experience Auto-type faster—even if the computer itself is air-gapped.
Thank you for your prompt reply! I apologize for my limited English; I noticed that the auto-type option in the roadmap was incomplete, and the forum posts didn’t provide any clear information. I didn’t intend to disrupt the strategy that’s already running smoothly or distract from the overall picture. If it’s expected to be implemented quickly, please delete this thread; I would appreciate it!
… I would tend to let your feature request stay open – at least until auto-type is implemented.
But, honestly, I don’t understand your feature request really well, so could you explain it a little more in detail?
I understand from that…
you want the passwords in BW login items – on the BW mobile app – be shown as a QR code
and that QR code should then be scannable by a desktop/laptop computer
And this would need a camera on that computer with which you can scan the QR code from the phone?
And you need only the mobile app to be able to “show” a password as a QR code, as those “QR scanning platforms” also are able to “auto-type” the password where you need it?
Or would BW – in the scope of your feature request – also have to develop a feature to auto-type those scanned QR codes into e.g. fields of desktop apps?
Yes, barcode readers are installed on the vast majority of computers in Chinese hospitals. They are used to read electronic health cards, specifically QR codes (once scanned and recognized, they input the 64-digit card number via simulated keyboard). Of course, in this post, I’m only aiming to implement the most basic functionality: displaying passwords as QR codes (for quick implementation). This allows users to enable automatic password input for every local application, web application, and even operating system logins—even on isolated networks and devices where passwordless environments cannot be set up.
But clearly you saw through my intentions—I also prefer customizable key sequences like Keepass (even if it’s just username-TAB-password). However, even just the password alone would suffice for me, as I worry that moving from 1 to N might require more effort than starting from 0 to 1, potentially stalling this feature request (which is crucial for practical implementation).
(When users are forced to navigate numerous poorly integrated information systems, each demanding regular changes to different complex passwords, it becomes a torment for both users and administrators. You surely understand what I mean, as this is precisely what Bitwarden has consistently addressed—thank you, Bitwarden, for making the world a better place.)