Suggestion: 1P's own iOS keyboard

Paco II

I have a number of apps that require a username and password to log in, with the added complication that when filling in one of the fields and then backgrounding the app, all fields are immediately cleared out. A challenge when I need to go back and forth to the 1P app to grab username and password (I have password-type usernames, so copying/pasting is required even for them). Have you guys considered adding your own iOS keyboard, where I could copy these entries to this keyboard, which would allow me to then easily enter them into the fields in the app? My thinking is that the keyboard would obey the same 'clear clipboard' rules. Seems no less secure than when copying into the clipboard, and would be unbelievably useful for these kinds of apps.

Hope you'll consider it.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Rad

Hi @Paco II,

Thanks for taking the time to write in ;-)

Yes, we have indeed considered adding a 1Password iOS keyboard ever since 3rd party keyboards came out last year with iOS 8. However, since iOS keyboards are disabled in secure fields (password fields), this complicates matters a bit...

We do have, however, the 1Password App Extension for iOS which works with Safari and 3rd party apps that integrated with our App Extension API.

Here's how to Enable the iOS extension.

And here's the list of apps that integrated with the 1Password App Extension.

Hope that this helps :wink:

Cheers!

Paco II

Please at least consider it, if even just for copying a username. Apps like Clips and Copyfeed won't import from a 1P copy, for obvious and good security reasons. So currently there is no good and easy way. The iOS extension is great for Safari, but none of the financial apps I use that have this 'issue' support 1P natively, which returns us to my original request.

Ben

Thanks for the feedback, @Paco II. When this feature first became available on iOS we evaluated it and decided that because it would not allow us to offer a "full" solution (one that could fill usernames and passwords) that the time required to build such a thing would not be worthwhile, and would indeed lead to a lot of questions from customers as to why we'd implement a keyboard in a password manager that could not fill your passwords.

This is something that we can reconsider now that some time has passed, but I'll be honest I imagine our developers are still going to look at a keyboard that can only fill usernames as "half baked."

We do certainly appreciate the feedback, and will take it into consideration when evaluating whether this feature is worthwhile in the future.

Thanks!

Ben