This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Inconsistent display of fields in mobile version
Hi - I have a few questions about some inconsistencies between the mobile and desktop version.
[list=1]
[*][b]empty fields[/b]
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).
[*][b]All Fields section[/b]
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.
[*][b]view masked fields[/b]
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
[list]
[*]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
[/list]
Anything to make this list shorter, even by a couple of steps (see also next point) will be appreciated.
[*][b]PIN field[/b]
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.
[/list]
[list=1]
[*][b]empty fields[/b]
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).
[*][b]All Fields section[/b]
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.
[*][b]view masked fields[/b]
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
[list]
[*]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
[/list]
Anything to make this list shorter, even by a couple of steps (see also next point) will be appreciated.
[*][b]PIN field[/b]
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.
[/list]
Flag
0
Comments
-
Hi, Michael. You've brought up some good points, and I'll address them one by one.
1) You are correct that displaying empty fields is unnecessary and inconsistent. We've filed an issue on this already. Regarding the password masking, it's shown masked whether or not there's a value so that someone can't just see that you don't have a password saved for whatever you're viewing. This is consistent with the desktop version.
2) All Fields is shown at the top so that you can easily copy and paste any information that you need to access. The Username and Password designations just show you which field is assigned to which function. I'll make a note of this though.
3) To view a masked field, all you have to do is tap and hold, and a box will pop up, asking if you want to reveal the password or copy it. Just tap reveal, and you're good to go.
4) I'm not sure about this one. I'll make a note of it.
Thanks for the great feedback!Flag 0 -
Thanks for your patience with me, Rob <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />
[quote name='RobYoder' timestamp='1294556011' post='18659']
1) Regarding the password masking, it's shown masked whether or not there's a value so that someone can't just see that you don't have a password saved for whatever you're viewing. This is consistent with the desktop version.
[/quote]
Whilst this is indeed consistent with the desktop version I would still question why it is necessary to mask empty fields. If a record does not require any password then the data associated with it cannot be very important or sensitive - otherwise why would you store it in a place that has no password.
But then we could also have the scenario where we have a record that does need a password but for some reason you have not filled in the password yet. In this case, masking the password field may make you think that you have already setup a password. But by showing it as blank you would see that it's still missing.
[quote name='RobYoder' timestamp='1294556011' post='18659']
2) All Fields is shown at the top so that you can easily copy and paste any information that you need to access. The Username and Password designations just show you which field is assigned to which function. I'll make a note of this though.
[/quote]
Sometimes, I copy/paste details from 1Password to a website but this is usually only done when I change personal or security details for a login. And I would do this only on my desktop where I can have browser and 1Password windows side-by-side. I'm not likely to do this on my iPod. On my iPod I would use the autofill from 1Password and therefore the "All Fields" section doesn't need to be up front.
[quote name='RobYoder' timestamp='1294556011' post='18659']
3) To view a masked field, all you have to do is tap and hold, and a box will pop up, asking if you want to reveal the password or copy it. Just tap reveal, and you're good to go.
[/quote]
I tried but this doesn't work for me. When I tap it and hold I can only see a "Copy" button popping up.Flag 0 -
[quote name='m w' timestamp='1294597347' post='18684']
Whilst this is indeed consistent with the desktop version I would still question why it is necessary to mask empty fields. If a record does not require any password then the data associated with it cannot be very important or sensitive - otherwise why would you store it in a place that has no password.
But then we could also have the scenario where we have a record that does need a password but for some reason you have not filled in the password yet. In this case, masking the password field may make you think that you have already setup a password. But by showing it as blank you would see that it's still missing.[/quote]
That's an interesting thought, but I think there was a reason they did it that way. I believe it used to be how you are describing, iirc.
[quote name='m w' timestamp='1294597347' post='18684']
Sometimes, I copy/paste details from 1Password to a website but this is usually only done when I change personal or security details for a login. And I would do this only on my desktop where I can have browser and 1Password windows side-by-side. I'm not likely to do this on my iPod. On my iPod I would use the autofill from 1Password and therefore the "All Fields" section doesn't need to be up front.[/quote]
The most common use cases for copy and paste are 1) for people who need/want to use Mobile Safari and not 1Password's built-in browser and 2) for native apps that require a login (such as Facebook, Twitter apps, Chase Mobile, Bank of America, etc.)
[quote name='m w' timestamp='1294597347' post='18684']
I tried but this doesn't work for me. When I tap it and hold I can only see a "Copy" button popping up.
[/quote]
What version of 1Password are you using on your device? I'm using a beta version of 1Password Pro, and my passwords aren't even concealed. This has already been reported (passwords not concealed), but I thought it was in the last stable release, too.
Anyway, I can't test my statement right now because my passwords aren't being hidden to begin with. On the iPad, however, where my passwords are hidden, if I tap and hold, I get both options, Copy or Reveal.Flag 0 -
[quote name='m w' timestamp='1294754382' post='18777']
I'm using version 3.5.4 which should be the latest, isn't it?
[/quote]
Yes 3.5.4 is the latest version available for download from the iTunes App Store.Unless one Has been submitted for review. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/wink.gif' class='bbc_emoticon' alt=';)' />Flag 0 -
[quote name='m w' timestamp='1294754382' post='18777']
I'm using version 3.5.4 which should be the latest, isn't it?
[/quote]
Yes, that's the latest official release. Try creating a new login with a fake username and password in 1Password on your iPhone or iPod touch (not iPad). Save it and then go back and view it again. Is the password concealed?Flag 0 -
[quote name='RobYoder' timestamp='1294771096' post='18802']
Yes, that's the latest official release. Try creating a new login with a fake username and password in 1Password on your iPhone or iPod touch (not iPad). Save it and then go back and view it again. Is the password concealed?
[/quote]
Ok Rob - I did that and realised when I view the record the password is masked by bullets. When I tap the password in the "All Fields" section I just get the copy button, when I tap the password in the "Login Information" section, it open a new page showing the password in clear text except for the end if it exceeds the width the window. To see that I have to go into edit mode.
Cheers
MichaelFlag 0
