Is there a list of "planned" v8 features anywhere?

Hey wraith,

Thanks for the this question. The simple answer here is "yes", with some caveats. I hope I can provide an explanation here that helps, both in the general and specific sense.

I've only briefly tested v8 and I'm switching back to v7 due to a few usability issues I've encountered (I'm sure they're minor to irrelevant for some people, but for my frequent usage they are a significant issue).

First, I'm sorry to hear that's the case! If you let us know what you've encountered, we'll be happy to either assist with a workaround or report the issue to our development team so it can be addressed.

You're correct, though: "Early Access" is just what it sounds like, a kind of early preview of the next edition of 1Password - not yet a business-ready, final product. If you really need that stability and reliability, 1Password 7 is certainly the way to go for now.

We like to provide these early previews because 1) it's cool for customers to get to try new stuff and 2) community reaction provides us a really great means of feedback and course-correction. That's a big part of how we know if we're doing the right things.

Based on comments in some of the other posts, many things are missing from v8 because they're just not ready yet (eg Mini)

True. You can reasonably expect 1Password 8 Stable to have more functionality ready to go than Early Access does. We have announced that Mini will be coming, and we want to make sure it's ready to roll out to all platforms, not just Mac, or Windows, and so on. It's indeed on the way.

others seem to be bugs

Also true! And we're working on it. More on this in a moment.

yet more seem to be design decisions (in-field prompts). Is there anywhere that explains what's intended to be coming in the beta so we don't bug you about stuff like Mini when it's coming anyway (and so we can ensure that we do bug you about the things that might be design changes)?

There's a lot that's appealing about this idea. I think it's also likely that it won't happen. Again, explanation further down 👇

What's in 1Password 8?

The major features you can expect from 1Password 8 (and, to be more specific, the biggest changes you can expect over 1Password 7) can be found here:

https://blog.1password.com/1password-8-for-windows-is-now-in-early-access/

A short list of big feature changes includes:

• A fully redesigned UI
• A new shared "core" of code across platforms, built from the ground up (thus each app resembles its siblings much more than in the current generation)
• Dark Mode! (I am personally very pro-all-dark-mode-everything, so very excited about this)
• Biometrics! including in your browser
• Closer integration between the desktop and browser apps, with shared unlock

You might have also heard about entire new solutions we've rolled out in parallel recently, like Secrets Automation, which makes secure secret-sharing possible for developers and other technical folks in a pretty awesome way. That's not specifically a part of 1Password 7 vs. 8, it's just ... a whole new thing we added on to both.

Development at 1Password

Without going outside my perimeter of competence here (I'm not a developer), I'd like to explain a little about how development works at 1Password, and how that affects publication of planned features.

1. The 1Password apps are always in a process of continual development and revision - even more than you see from your end. That is, we're constantly adding fixes, testing new features, and generally building things out incrementally. In contrast to the Bad Old Days of software design, many software companies have moved to this small-step approach, rather than releasing one "final" software version in a box and calling it a day. Same deal here - and that means revision and refinement are just part of what we always do. The end result is better stability, better security, and the ability to make changes really fast when it's critical to do so.

2. We almost always keep new features private until they're ready to go. There's a simple reason for this: we prefer to under-promise and over-deliver, and sometimes it's also not clear ahead of time what will be an easy thing to do, or if changing a certain aspect of the software is a coding and design nightmare. We don't want to promise something and then not be able to back it up.

3. The diversity of examples you've noticed here - some bugs haven't been worked out, some features aren't built yet, some are design decisions - are outgrowths of this design philosophy (and the fact that EA isn't a finished product). We want to know about bugs so we can fix them quickly. We provide Early Access so folks can try out the basic features of the next release, while being clear that this isn't the final thing yet. And we continually improve the product as we go.

Given that, it would be very hard to release a definitive list of features. Instead, we try to provide the highlights, and pleasantly surprise you with our ratio of promise-to-deliver. I hope that makes sense!

And lastly, if you do have specific requests - for bug fixes, for new features, and so on - this is the place to let us know. 👍

Many thanks!