Sticky Post of Remaining Features?

zendnez

Hi, 1Password folks. Would you be open to a stickied post in which you list features that are not yet supported in the beta and provided some notion of ordering or status? Seems that this would save you effort in answering many similar questions while giving us users a sense of your priorities. We'd also all have a common notion of what "finished" or "shippable" looks like.

I've taken a shot at how this list might initially look. If you're up for this, please feel free to either sticky this post (edit it if you want) or create a new one. Thanks for considering this request.

Save and restore window position
Search all fields (vs. just tags & titles)
Create custom sections and fields
1Password Mini fills identities and credit cards
Rich icons for logins
Custom icons for all items
Attachments to local items
Editing of local vaults (including DropBox & OneDrive synced vaults)
Local sync of local vaults
Support unlocking using Windows Hello (fingerprints, face recognition, PIN)
Watchtower
Security Audit

---

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

MikeT

Hi @zendnez,

Thanks for writing in with this awesome idea.

We've tried something like this before and it didn't really work out the way we wanted it to be, new threads are still created despite having an updated clear list of known issues. We do have a small roadmap in the pinned welcome guide in this beta forum that we probably will update soon as we're working on our first stable update soon.

One of the things is that we do want people to tell us their top concerns, so we can prioritize based on incoming reports. In addition, we can help with different tricks based on what we have now.

zendnez

It's unfortunate it didn't work out before. Personally wish you'd try again. I think what I really want is for you guys to open the door to having the community help you project manage this effort to completion. I just wish you'd pick either path A ) make it work for local vaults or B) make it work for cloud vaults, write down a public list of the things you need to do to land a complete product for that path, and then start checking things off. Let us see what you're doing in what order.

I could give you the subset list of what you need to do in order for v6 to be a credible replacement for users of local vaults. I think we all know, though, that your priority is to support cloud vaults first and I'm fully in support of that.

With that in mind, this is my minimum list of what I need in order to switch to 1Password 6 and cloud vaults:

• Save and restore window position
• Search all fields (vs. just tags & titles)
• Create custom sections and fields
• 1Password Mini fills identities and credit cards

If you did nothing but these 4 things, I would re-activate my family subscription, import my vault, delete 1Password 4, and not look back.

Rich icons for logins would be nice to have but I don't consider them required. Custom icons, too, and I suspect those probably have to be on the list in order to support full-fidelity import for people who use them. All the rest - watchtower/security audit, windows hello, all of the features supporting local vaults - can come later.

If I were project managing this thing, those 4 items would be on my whiteboard and we would run hard at them - and nothing else - until we hit v1.

I hope this helps. I hope it doesn't just bounce off.

Thanks.

pbryanw

@zendnez - Hi, thanks for the great list of features you'd like to see in 1Password 6. As another user of the 6 beta, I'd like to see all the features in your first post incorporated into the new Windows version at some point :+1:

Just to add my own personal feature request. I'd like to see manual saving of logins coming to the 1Password 6 beta. I'm not a huge fan of auto-saving as I've had problems with it in the past (admittedly this was a long time ago). I also like having complete control of when & how I want to save items, so manual saving is a must for me.

I'd also to the list:- remembering which vault you were last in on startup, or setting a user-defined vault to load on startup (I've seen this requested a few times in threads on here). And I was thinking it would be great if there was a mechanism like you get in the Windows start menu, whereby if you have your logins sorted by title, you can click on a letter which then brings up a list of letters which let you jump to the alphabet letter of your choice (hope I've explained this clearly enough, and this would apply to the desktop app).

Saying this, it's become apparent with the last few 1Password 6 betas, how close it's coming to being fully usable & stable for my use. It's come a long, long way - with its regular updates - since the very first beta.

MikeT

Hi @zendnez and @pbryanw,

Thanks, we really do love hearing how passionate you guys and the community are to help us improve 1Password 6 to the point you can use it for good. Everything on both of your lists is already on our list to implement in the near future.

As much as we really want to be more open with our development plans with the community here, it's just not something that our internal workflows will allow for. As I mentioned before, we did try to be more open and sharing more details but often than enough, when you have a diverse community that have different needs and so on, it becomes difficult for us to work with. We even got a lawsuit threat once because we said we were going to work on one feature but decided to postpone it because it needed more development time.

Right now, our priority and the only priority is to get the foundation of 1Password 6 done and stabilized, so that we can start adding new features on top of it. 1Password 6 is a new codebase and in order for certain features to work, the foundation of which the feature is based on has to be coded first, which means initially everything is going to take some time to finish. We cannot add all sorts of new features while building the foundation, it'll just break apart, just like you don't start building a bedroom while pouring concrete or putting up the framing for it. pbryanw pretty much bought up why we're doing this, it is becoming more stable and usable daily because of how we're handling this from the beginning.

We have an internal tracker with a huge list of things we need to do and we do team reviews (both engineering and CS teams from the forums, twitter, emails and so on) twice weekly to review our to-do list. Our development is based on variables that has to be considered; for an example, if 1Password.com is adding a new feature, we need to test and make changes to make sure the app can gracefully handle it. There are a lot of things happening every day and we're trying to do a much faster pace of release cycle where we ship weekly or biweekly updates instead of doing one major update every few months that we used to do in the past.