UX and 1Password 7 click fatigue

jdowson
jdowson
Community Member
in Mac

I continue to feel like Agilebits doesn't test 1Password 'at scale' - i.e. what if someone has lots of records of a certain type: then what does the user experience feel like?

  1. [New] The new hhtps check - nice, but if someone has 300 items in that state, they have to deal with each one. You need a 'change all' to https, and then allow exception handling - but fix most of them when you can. Right now, it's an unnecessary PITA.
  2. [Old] The need for default field values for software licenses. What if a user has 350+ software license? How many times does one need to type email and licensee user full name especially when Textexpander is unavailable? Do some anonymous statistical analysis of your user population and determine if there are frequently repeated strings (whatever they are) - that might suggest an opportunity to reduce user effort.

This is basic stuff - and it's hard to understand why Agilebits doesn't get it.

Yeah, I know - not your priority. You've told me. :'(

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

Comments

  • jdowson
    jdowson
    Community Member

    And another one:
    3. If you go to a site that is noted as compromised, how do you generate a new password in Mini? It looks like you can't - you have to switch back to 1Password. There used to be a 'generate new password' menu bar item - looks like it's gone.

  • danco
    danco
    Volunteer Moderator

    As to 3. In my set up Mini has a sidebar, and Password Generator is visible near the top. Do you have something different?

    Your suggestion 2 seems a good one.

    I'm not sure whether suggestion1 is actually practical - would be nice if it were.

  • jdowson
    jdowson
    Community Member

    @danco You have to have the popup appear for the generator - it used to be directly in the menubar as a pulldown.

    1. is practical - if you can discover programmatically that 1 site does not respond to an https GET, why can you not scan a list and just handle the ones that are OK?
  • ag_kevin
    ag_kevin

    Hi @jdowson ,

    Thanks for the suggestions. I'll attempt to address them here:

    1. Yes, we can certainly automate the updating of http to https. When doing things in bulk behind the scenes, a new set of issues arises. Issues such as how to notify the user of errors in a way that won't disrupt their workflow, what do to a site does respond to https, but doesn't present the same page, breaking the login? This might not be discovered for a long time, and then many customers might have broken login items. These are a few of the challenges that must be solved before doing this. It's not to say it's impossible, but sometimes, thinking about accounting for errors and failures takes a fair bit of time before we could implement it. We didn't want to hold back the warnings for that. Right now, the best option is just to deal with them as you use each affected site.

    2. The suggestion of auto-filling things like that into templates is a good suggestion and yes, we know that many customers have suggested it already. It is also something I'd personally like to see. We continue to look at this one, but I can't promise when or if it will be done, but we're certainly not saying no.

    3. danco has addressed this, but it should be just as easy. Click to show, click "Password Generator", click Fill. Before it was click, mouse down, wait for generator to show, click Fill. We can look into making this a bit more streamlined though.

    Thanks again for taking the time to send in feedback. We do appreciate it and will be taking it all into account.

    Cheers,
    Kevin

This discussion has been closed.