Hi esquared, this feedback is very welcome.
I LOVE 1Password.
We really, really appreciate this! It will not surprise you to know that we care a lot about what we do here, and hearing about positive experiences with the apps is part of what keeps us going. We of course want 1Password to be an experience without peer. Speaking of that...
Please let me be your advocate for the new version by addressing the issues raised here and elsewhere.
We're more than happy to have this kind of engagement. We want to be pushed, and that requires a process of finding out what's working naturally for you, and where the pain points are, and what kind of new features might resolve issues by preventing them from even happening in the first place. We're also continually challenging ourselves to up our game as well, in ways that aren't always visible from the outside but which are happening here every day nonetheless.
While your product is security focused, your users need to feel as if the tool supports them, not the other way around, and as it flows now in 1P8, there is a lot of the the tool imposing a mental model on the users inappropriately.
Speaking only for myself, it does feel like there's a balance to be struck here. We of course agree that the tool should support the person, not the other way around. We talk a lot about "human-centric security", and recognize that one of the traditional reasons people don't adopt security apps is because they're cumbersome or unintuitive! So resolving that dissonance is something that's always on our minds.
That said, I think part of the way we get there is by establishing a solid design (done) and fleshing it out (ongoing) that commits to a particular vision of how the app should work. That by necessity involves an implicit mental model, because without that there would seem to be no rhyme or reason to anything - but it should of course be an intuitive one. Apple products are one prominent example of how this can be done well. We similarly seek to meet that standard of "ah, of course it works this way." And that's an ongoing effort.
OK, to the specifics!
Duplicate item (this issue).
Mike has filed this issue for you, so that's a step forward. With that said, it's the first request we've gotten for it, so I can't speak to the likelihood of its implementation.
Reordering fields
This is going to happen. The relevant team is at work on it and we'll be delighted to announce here when it's done. 👍
Copy / paste field title
I think this is related to a recent regression we had with copy / paste functionality. It should be resolved in the latest Beta, which is out today! Does that resolve the discrepancy for you?
changing field type
This is something we're evaluating. I don't have much to share on it at the moment, but can personally understand why this would be useful. I agree - this would be totally in line with "least friction" philosophy; the question is probably "what does it take to make this happen?", and how to balance that with the (many, many, many) other feature requests and priorities that customers ask us to address? In any case, I'll be happy to share more on this when we're able to.
We appreciate your thoughtful engagement here, and hope that you'll be impressed as we keep pushing forward. While we may not agree every time on the best way to approach a particular feature or need, we very much want the same thing when it comes to meeting the standard of excellence you expect of us. We'll do our best to make that happen.
