[jl_agilebits]

> Can you quantify the "needless development churn and hassle for both customers and our support team" in some way?

Sure, happy to elaborate on that! Since we were rebuilding our app from the ground up, it was a significant slow-down on development to create a user interface for both Electron and SwiftUI, requiring two separate teams of platform developers for every feature we needed to implement. There were also concerns by the documentation and support teams that we would need two separate sets of instructions for many common tasks, due to small differences in layout and look between the applications. Eventually, we had to make the tough decision to focus on a single common framework for desktop. This will allow us to ship features across every single platform far quicker than we could before.

> I'd be hopeful that whatever tradeoffs y'all will be making moving to Electron, the "native" feel of the macOS client wouldn't be sacrificed.

We've tried our very best to keep the experience the same so that the transition from 7 to 8 is smooth, and from my point of view 1Password 8 feels right at home on macOS - I especially love our new translucent sidebar. That being said, this is still in an early access stage, so there are bound to be hiccups and UI issues that need to be resolved. Please let us know if you run into any problems or have suggestions on how we can improve. And thank you for being a long-time user!

[drcongo]

This is such nonsense that I can't let it go unremarked. I can count on the fingers of zero hands the number of times 1Password has shipped a "new feature" between major releases. There are no new features needed, it's a password manager. However, I would need to borrow some extra hands to count the number of features you've removed, features that loyal paying customers of many years depend on. 1P7 doesn't even let you keyboard navigate to the Generate Password button for goodness sake - something that I was able to do in every version up to that point.

Absolutely nothing about any decision AgileBits has made in the last 4 years has had anything to do with what customers (that's us, the people that used to give you money) want, and everything to do with nickle and diming the suckers dry.

UI consistency between different operating systems is NOT a user-focussed feature. When I'm on a Mac, I want my apps to behave like a Mac app. When I'm on Linux, I want my apps to behave like a Linux app. If you _actually_ believed that all apps should look and behave the same on any OS, why does the Android version look and behave nothing like the Mac app?

You've removed features with every major release, and this is just smashing the final nail into 1Password's coffin. You've ruined what used to be the best password manager on any platform.

[1123581321]

Take a look at the items marked “new” in the changelog. https://app-updates.agilebits.com/product_history/OPM7

[stock_toaster]

> requiring two separate teams of platform developers for every feature we needed to implement

So your margins are more important than your users’ native experiences. Got it.

[the_lucifer]

I mean looking at this I can see why people came to the conclusion that this was primarily a move that VC funding caused even though AgileBits seem to vehemently deny this.

[psionides]

The funny thing is, they were doing just fine for years with just their own money. Now that they have sooo much more money, they suddenly can't afford separate developers for different platforms... they should be able to hire 10x more people now.

[jl_agilebits]

The primary issue with having two separate teams for the same platform was not money, it was time. To be clear: we wanted to build a native app in parallel with our cross-platform Electron solution, and we had the developers to do it. But unfortunately, having an additional team that needed to implement the UI for every single new feature was a significant slow-down, and we collectively realized that we could not meet our deadlines nor maintain this long term.

I'm sorry for not being more clear earlier as to why we couldn't support two separate teams for the same platform. Hopefully this clears up any confusion.

[jimsimmons]

I don’t understand why two teams means slower. Are you keeping the total number of engineers the same? If you are saying 2x engineers on electron complete tasks faster than 1x on electron and 1x on native, you are basically agreeing with OPs take.

You take money to provide software. But then you become lazy and greedy and want 1 size fits all. End result is your users having clunky, high latency experience.

[1123581321]

I think he’s saying 1x on both Electron and Swift UI was making it too hard to ship either version to an acceptable standard because each was slowing the other down due to inconsistencies, difficulty staying in parity and double communication.

Unfortunately, it’s normal in software development for multiple platforms to increase development complexity when feature and UX parity is prioritized.

[maxharris]

Your deadlines are irrelevant to us. We want native UI

[sleepybrett]

Maybe I'm missing something, but i pay for those teams with my client purchases. I have a mixed computing environment and have purchased versions 3, 4, 5, 6 & 7 for three platforms.

[maxharris]

Please let us know if you run into any problems or have suggestions on how we can improve.

Okay, I have a suggestion: drop Electron and keep supporting the native app you have.

[neon_electro]

I'll be trying out 1Password 8, but what are my options if I'd like to continue my subscription and stay on 1Password 7?