[Request] Make Custom Fields a Developmental Priority
In 1Password 4 for iOS, you introduced the custom text, password, email or url fields. These, however, can only be accessed when creating a field; they cannot be changed once the field has been created, unlike with 1Password 4 for Mac. Despite being able to customize the field after it has been created with 1Password 4 for Mac, though, the user can only choose between password or plain text. Currently, I have multiple logins with special URLs put in as custom fields, but because they were entered as plain text fields, to convert them (on 1Password for iOS) to website fields would be very onerous. In order to rectify this issue easily and efficiently, my request is that, from a developmental standpoint, you prioritize allowing 1Password for Mac to add website fields freely (as it does with password and plain text), and also allowing 1Password for iOS to have 1Password for Mac's ability to change the field's identity after it has been created.
Comments
-
+1
0 -
Hi @tatchley and @loscamos,
Thanks for pointing this out and letting us know that this is something you would like to see!
0
