Design language

I read you have considered accessibility. I think you have not. Can you have the option to increase fonts in the field view? Some of the secondary information is in really light grey and tiny fonts.

One other screen that acts as a modal that did not act as a modal in 1Password 7 is the sign in on another device. I keep my work 1Password details in my personal 1Password. In order to sign into my work 1Password account with 1Password 8, I had to copy the entire entry as JSON so that I could do this, which meant that the “sign in on another device” was completely useless.

Tying 1Password behaviour into modals is an absolute usability regression and should be reconsidered; if the desire is to keep 1Password as a single window application, then embrace tabs (hitting ⌘, in VS Code brings up preferences in a new tab, not a modal).

Thanks for this, @octothorpe88! I have passed this suggestion on to our developers. We appreciate you taking the time to share it with such clarity.

ref: dev/projects/customer-feature-requests/#851

I like that suggestion, @octothorpe88

I'm finding the beta version functions quite smoothly and well. What I don't like is how far everything is spaced out. I used to be able to see all of my favorites (9 of them) on one screen. Now I only can, barely, if I use the entire height of my MacBook Air. The problem is made worse by the unnecessarily tall height of the dividers. I'm not sure why they're so large, but it compounds the issue.

I think there's some underlying assumption here that it becomes easier for the user to identify and select the login they're looking for if they're very separated by white space. I think the site icons do a lot of this work already, allowing the user to quickly identify a particular login. I know, too little space and things start to look cluttered, but I think it's skewed too far in the other direction.

And of course this also might be a personal preference. I, for one, would welcome variable spacing, like the Gmail interface offers:

The question is, will you be doing all the work to make the Electron app behave like a native Mac app? Scrolling behavior, keyboard focus and all of the little and big things that make a Mac app feel like it belongs on the system? If so it will require a bunch of custom code and a lot of extra time which negates the use of Electron for a more unified codebase anyways.

I'd much rather keep using 1Password 7 but once you publish 1Password 8 to the App Store I assume 1Password 7 won't be maintained anymore. Why not just tweak the 1Password 7 interface a bit and leave it at that? It works wonderfully and is a native application.

The Mac application has to feel like a Mac application. It can't be a unified experience with all the other platforms. This new approach may elevate the experience on Windows and Linux compared to the current applications, but it will sure degrade it on macOS.

It's bad enough that so many other applications are web based. I have switched from many apps to other solutions because of it. I want the Mac experience. It's why I am a Mac user.

Windows users may already be lost. They know no other way than to be constantly confronted with a lack of consistency. They eat whatever you put in front of them. I am sometimes stunned at WHAT Windows users sometimes put up with without reacting.

I switched to Windows after more than 10 years with RISC OS and couldn't stand it for 2 years. I was spoiled by consistency with RISC OS. It wasn't until I switched to OSX that it brought it back to me (almost) exactly the same. It was for exactly THAT reason that I chose OSX. Consistency. I think that's exactly why most Mac users are on that platform.

I wonder: what is wrong with the v7? From my point of view, v7 is close to perfect. It works simply and unobtrusively. Exactly what I expect from an auxiliary tool like this.

Why do you kill an application like v7 so completely without need. I never called for a v8. A very simple product maintenance would have been perfectly sufficient.

And as far as uniformity on different platforms is concerned: I WANT an application to fit into the respective system. I absolutely can't stand Windows and I avoid it where I can. It puts me in a bad mood when I have to use it. And as much as I dislike the way Windows interacts with you, I hate it when developers of applications think they have to build their own design and operating "philosophy".

This is all about distraction. It costs cognitive energy to have to pay attention to whether and where the little differences are, depending on the application. Among other things, THAT is why Electron is such a disaster: EVERY Electron application feels like an alien. But each in its own way. That is incredibly annoying. And when the devs come from the Windows corner, it gets even worse.

Please please please, at least leave the v7 of the Mac version in the program. I don't miss anything about it, it's perfect the way it is.

Oh, I'm not an old man stuck in the past, by the way. In fact, I use everything as beta, or even test versions (*), that works. MailMate, for example, I have used exclusively as a test release since the beginning. I want the future... NOW. Electron is a step into the past. And a huge one at that.

(*) Never really had any problems with it in over 30 years. I know what I'm doing. :)

@danvpeterson that's a lot for you thoughtful response. As a product designer myself all I can feel here is empathy.

I may be on the minority, but I actually love the new visual language (it reminds me a lot of the Things app from Cultured Code — an app I've been using for many, many years). I like white space and I truly believe high-density designs are stressful to use. The new design feels lightweight and fun.

That said, my main concern here is Electron's limitations and the philosophy behind building the same app experience for all platforms. I really hope the final 8.0 version feels more native and polished than what we have at the moment.

As I mentioned in another forum post, I think a huge missing piece of the discussion (which @danvpeterson touches on briefly, thank you) has been clear information from 1Password on what is the plan from a design and Mac fit perspective. What is gained with Electron, what is lost, where 1Password is headed to close those gaps (if possible). Effectively, how do you plan making the "Electron" look/feel effectively disappear and make 1P8 a first class Mac citizen? Or does 1Password plan not to bother going that far?

We all know that there has never been a first class Mac Electron app out there (VSCode probably comes the closest, but that is so dev centric it's in a separate category to be honest). Thus, we all freaked out for legit reason that 1Password's famous Mac experience will never be the same with Electron in the picture.

The key to 1Password turning around this discussion, at least on the Electron piece (we'll leave out the deprecated features discussion on this one), is really explaining the design philosophy and plan going forward for the Mac.