Hey,
Concerning the android app,
I would think that autofill options could be expanded to include android app URI locators. Currently, to add such an URI the user would have to know the scheme “androidapp://com.example” first before they add it to the option field under new autofill option. I think a button or option could be added here to include atleast the “androidapp://” so that user can type the package name. Better would be to provide the whole scheme from the intent request but I don’t know if that is possible.
The Bitwarden mobile app for Android has an Autofill and Save function, which will save the URI in the selected vault item. Would this not work for you?
Maybe another Android user can assist, as I do not use the Android app myself. My understanding was that the workflow would be something like: navigate to app → search for relevant credential in Bitwarden → select Autofill and Save (i.e., similar to the work flow in the browser extension).
Maybe I don’t know the Android app myself enough now… But as I see it (and I just tested it on my phone), it doesn’t have an explicitAutofill/Fill and Save button in the three-dot-menu for a credential. (if one clicked on the credential, “View” opens - and there is also no Autofill/Fill and Save button there)
But, and this might be the difference to the iOS mobile app, Android has an implicitAutofill/Fill and Save button/function, as I would call it now, because: if you want to fill an item on a website… and from that you open the BW app, it either finds a “same” or similar login (and if not, you can search for a corresponding item - like it happened in my screenshot now)…
That is for a website… I think it’s the same for an app…
Besides indeed using Autofill and save - another way to get to the URI (of a website or app) should be to just click on the + in my first screenshot, as then the “New login” dialog opens, with the added URI, which you then either use for the new entry (and save it) or mark and copy the URI.
(PS: I just tested this with an Android app now - it does get the URI including the androidapp://... part, which was the original point of the request, if I understand it correctly)
Just for completeness: And I think another way to get the URIs for Android apps is via the Google Play Store, as described here in the Help Sites. (PS: though this does get the URI of the app, but not the androidapp://... scheme in front of it…)
The process you have described for Android’s “Autofill and Save” is definitely different (and much simpler) than the workflow described by @dsl8b1d8 in their previous comment (starting from having opened an app and seeing no matching credentials):
In contrast, your method (starting from having opened an app and seeing no matching credentials) would be:
Search for item that has the credentials.
Select the desired item.
Select “Autofill and Save”.
As the name of the feature implies, this will not only autofill the desired username/password, but will also save the correct URI scheme (e.g., androidapp://com.example) in the login item, so that URI match detection will work automatically the next time that the app is opened.
IMO, this existing feature meets the requirements of OP’s feature request.
Hm. Seems so. - But I think, the request for a pre-defined androidapp:// URI scheme (and https:// …), that could be easily choosable would still make a valid request.
Yes, I think it’s close enough — but as the current topic has 0 votes, closing the thread or merging it would have the same effect…
Merging would clutter up the destination thread with our “internal” discussion, so if you feel like merging is the best option, then I would suggest only moving the first post.
like my first screenshot showed it:
