(that quote was from your first post) I think it’s not that simple, as normal URLs look like this:
https://www.netflix.com
… but the Android variant looks like this:
androidapp://com.netflix.mediaclient
→ it’s not only reversing two parts of it…
And other Android apps use different patterns – e.g. for PayPal for me it is https://www.paypal.com but androidapp://com.paypal.android.p2pmobile (and I don’t think Paypal would work with .mediaclient … as Netflix wouldn’t work with .android.p2mobile…)
@user47 I now merged your Feature Request (FR) with this one.
And I tried to find a shorter title which hopefully also reflects the request.
(the former title of this FR was When using PC signup with https://example.com if bitwarden could helpfully auto-add the androidapp://com.example complement for Android Apps autofill to match" – and the former title of @user47’s FR was Bitwarden needs to convert computer URLs to Android URIs)
I think the easiest way for Bitwarden to address this issue would be if they at least added the corresponding Android and iOS app URIs to each set of pre-defined Equivalent Domains (and perhaps also expanded the list to include additional common websites).
Hey, nothing against this feature request in particular – but you really do have about 500 credentials in Bitwarden and for everyone an Android app (!) where you want to login to? – If you just want to login to some of them with on a mobile browser (!) you don’t need a changed URI for that (just as a reminder).
And also as a reminder: when you try to login on an Android app (!), you then can search manually for your matching credential in the Bitwarden app (sidenote: unfortunately, I suffer from the bug on the mobile app, that I chose “English” but in some cases it shows my German system language):
As I wrote it before - and I think @grb wrote back in December in the other discussion - by using that, you add the `androidapp://…" URI to your credential, and next time can use autofill directly.
A struggle I have with the autofull is that sometimes I want to use autofill for an app, and Bitwarden fails to recognize that the app as that same website I have saved for that password, so I have to manually go and add these weird “com.appname.whatever” URLs to my passwords too. Not sure if it’s an Android problem or a Bitwarden problem, but I thought it’s best to mention it.
I recently migrated from LastPass to Bitwarden. The vault transfer was tedious, and LastPass is partially to blame for its limited CSV export. However, once I set up the vault, I was surprised by how difficult it is to get app autofill working on Android - I did not expect Bitwarden not to find the login credentials for an app when the vault contained the app’s associated URL. Bitwarden clearly recognizes app package names during autofill attempts, yet it requires users to enter them (e.g.,androidapp://com.package.name) manually as URIs to link credentials, which is unnecessarily complex and creates friction for users who are already navigating a sensitive migration (my phone has 221 apps and the vault has 452 logins; it will take a considerable effort to complete the linking!).
From a technical standpoint, Bitwarden has all the information needed to securely infer the correct URI format. A simple toggle—“Auto-link apps using known package names”—would let users opt into a smarter experience without compromising security, dramatically reducing onboarding pain, and improving retention.
Microsoft succeeded in migrating Lotus 1-2-3 users to Excel by supporting familiar functions and command keys. Bitwarden could follow a similar path: respect user expectations, reduce friction, and build trust through usability—not just encryption.
I’m a college professor and systems designer, and I see this as a strategic blind spot. Bitwarden’s growth is limited not by its security model, but by its UX rigidity. Please consider implementing smarter app-linking logic or at least surfacing package name suggestions during autofill failures. It’s a small change with a significant impact.
I moved your post into this existing feature request on the same topic. (you can vote for feature requests when you reach the next “trust level” – just spend some time on the forum for that)
Read through the history on this FR. You will likely find that Autofill and Save is your friend here. You will also find examples without a clearcut relationship between website and android app, like this:
And, the last thing I want when it comes to auto filling my credentials is for anything to guess at the answer due the prevalence of look-alike websites that exist solely to harvest credentials.
That said, if you have a curated mapping of andriod apps to web sites, I suspect Bitwarden would appreciate you submitting it as candidates to be added to the Equivalent Domains list. (GitHub · Where software is built, click “New Issue”).
