Cross platform design philosophy

Nhat_Nguyen

1Password is a cross-platform application that not only works on Windows or Mac, but it should also work on all available platforms, so it would be a tremendous advantage when they share the same source code. We can fix a bug faster, data can work across devices more effectively, and we can spend more time fixing and improving 1Password instead of dividing our resources to different departments to work on various native apps. There is usually difficulty communicating between teams since they use different technologies and that will make an issue takes much longer to resolve.

I appreciate this, but it isn't as good for the end user, because we end up with a compromised experience on each platform, rather than them all being the best they can be for their respective platforms.

There are excellent apps that use Electro such as Slack, VS code (One of the best code editors if not the best), Discord, WordPress are just a few of them and the list I believe will keep being bigger over time as more and more apps require to work cross platforms.

Sorry, none of those are excellent. They are all bloaty, hot, resource hogs that don't feel like native macOS Apps.

The development process of a native app will inarguably cost more for much less when we develop an app that must work on many platforms. We can't expect to spend resources to develop native 1Password 8 for Mac, Windows, iOS, Android separately and being effective. If we can't focus our resources, we will fall behind.

I respectfully disagree, you wouldn't have merged the code base if there wasn't a cost and efficiency saving for you in the long run. If the native apps are more expensive to make that's fine - given the price you charge, that's what you should be doing, not compromising the experience by using sub-standard frameworks such as Electron.

We did not just deciding to go for Electron without any researches and reasons. We guarantee that it fits our development focus to make great app with better performance, user friendly

I'm sure you had your reasons, what i am saying is that those reasons were flawed, or not particularly customer centric. I'm sorry to be blunt, but your guarantee has already been breached - it is less user friendly than before, and arguably less performant when you consider it is a massive resource hog.

Please give it a try to see how it works.

I have, and it is absolutely appalling, it looks swish, but it is not user friendly, it makes the computer run hot and hogs resources.