Hi - I have a few questions about some inconsistencies between the mobile and desktop version.
- empty fields
Why are empty fields displayed in the mobile version whilst they are not displayed in the desktop version (unless you go into edit mode)?
Given that the mobile version is limited by the much smaller display size on the device (I'm using an iPod touch) it doesn't make sense to show these empty fields. And when a password field is empty it still shows ******** (I noticed this in a login record).
- All Fields section
Why is this section showing almost at the top in the mobile version when in the desktop version it is the last section?
For some logins, this section can contain a great many fields but all you're really interested is the username and password, i.e. the data from the "Login Information" section.
- view masked fields
I find it quite cumbersome to view masked field values in the mobile version.
Why do I have to go into edit to view the unmasked value? And even then I still have to tab the value before if shows the unmasked value.
BTW, the desktop version also requires you to click on the value before it shows the unmasked value if you have the option "Conceal Passwords" enabled. Not sure why we need to protect these fields in edit mode on any device.
Whilst I don't see this too much of an issue for login records as here you usually just visit the webpage and let 1Password fill in the details or you copy/paste the values, if needed, it is far more important for wallet items to show, for example, the pin of a credit card without having to go into edit mode and then tab the pin field.
Consider this scenario:
Standing at the till, you realise you just entered a wrong PIN and you better look it up to avoid locking your card.
You have to
- switch on your iPod
- enter your passcode
- tap 1Password
- enter your unlock code
- tap the wallet icon
- scroll to record
- tap record
- scroll down to see the PIN before you realise it's masked
- tap the Edit button
- finally, after tapping the PIN field you see the value
Anything to make this list shorter, even by a couple of steps (see also next point) will be appreciated.
- PIN field
Why is the PIN field so far down?
It would be better to show the PIN fields together with the card number, CVV, etc. as this is all the info you need when you make a payment. Would be less of an issue if point 1 (empty fields) would be corrected, but still I would group it with the other card details even in the desktop app.