Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
gussic
4 years agoContributor
Cross platform design philosophy
I understand a part for you deciding to go for Electron on the front end was so that the Apps could all look and feel as close as possible to each other across the various different platforms. Can I ask, seriously, who actually asked for this?
I've done a quick and dirty survey of my non technically bless friends - not a single one of them expects or wants Apps to behave the same way across all platforms. All of them expect, and are happy to accept that each platform will make Apps looks and behave differently.
Shouldn't the focus being on using the best available to technologies and frameworks to make each App feel, look and function the best for its respect platform, even if that means it isn't exactly consistent across each?
I'm just struggling to understand this design decision, and it makes me sad because it really feels like an absolute betrayal for one of the key things you used to stand for, having the best native Mac Apps possible. Using Electron is completely at odds with having the best native Mac App possible, because there are other, better frameworks out there.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
- Former Member
I respectfully disagree on the RAM point. Several major vendors, Apple included, still sell laptops and desktops that only have 8GB of RAM, the former of which can’t be upgraded. Furthermore, there’s quite a lot of people who are still using old laptops with only 8GB of soldered RAM because those machines still meet those users’ requirements, making spending on upgrades a dicey value proposition (especially with how processing power has plateaued in the past decade).
Personally, yes, I won't buy anything with less than 16GB, and have preference for a 32GB+. But I’m a software engineer and tech enthusiast, and as such I’m in a very tiny bubble. The average individual isn’t so well off in terms of hardware, and because of that I do what I can to make sure the software I work on is finely crafted and doesn’t require more resources than it absolutely has to, because a few hundred megs here and a few hundred megs there pile up fast.
- cryptochromeOccasional Contributor
Don't be ridiculous.
- Former Member
You wouldn't judge a newborn by its cooking abilities, would you.
Well, if the newborn had no eyes and hands, then I would know that life will be hard for it. This is the state of 1Password8 on the Mac. - cryptochromeOccasional Contributor
Unfortunately for those of us using the preview on Mac for the moment, it's less "other platforms getting the features that were Apple-native" and more "stripping the Mac-native version to match the others."
I don't know how you came to this impression, but that is NOT what is happening. You're looking at an early preview that doesn't have all the features yet, but my understanding is that there will be feature parity with previous versions and then some.
You wouldn't judge a newborn by its cooking abilities, would you.
- kcastillNew Contributor
I'm quite happy to get the features from the Apple versions over to my platforms.
I hear this, and am all for it.
Unfortunately for those of us using the preview on Mac for the moment, it's less "other platforms getting the features that were Apple-native" and more "stripping the Mac-native version to match the others."
- Former Member
One could open up the arc a little further: As some people have probably noticed, we are slowly burning our asses off. One of the ways out of the dilemma is NOT to waste more energy. I've been wondering for a while now what all these Electron-like apps and other JS hell apps consume more energy than their efficiently programmed counterparts.
Billions of computers and servers operating as if resources were free. I studied technical computer science. I used to develop software for devices with little memory and CPU. I dare say that all those who bluntly pull thousands of node/whatever dependencies into their code can't really develop SW. They can nail together prefabricated boards, but that's about it.
I had compared a few Electron apps to their native counterparts a while back. The bottom line was that the resource consumption was at least 3 to 5 times and even up to 10 times higher. Be it CPU, processes/threads (this also costs resources), RAM and battery. Not only do the apps themselves consume more battery, you also need more and more RAM - and RAM, oh wonder, needs more energy.
There are some projects out there that are also multiplatform. They use e.g. Java or C/C++ as a core and marry this with a corresponding GUI on the respective platforms. Like Cyberduck, Transmission or Handbrake, for example.
- cryptochromeOccasional Contributor
I love all the Agilebits employees with burner accounts now.
First of all, stop making dumbfounded accusations. If you search my previous posts on this forum you will realize quickly that your comment was pretty idiotic.
Second, saying that the sole differentiator of 1P was UI polish just shows how little you know about password managers in general and just how exceptional 1P's security architecture is compared to other password managers. And that's what you actually should be concerned about, not fancy looks.
I am a security engineer in my professional career and I chose 1P solely for what it does, not for how it looks. Just to add to my previous post to give some more context.
- Former Member
I love all the Agilebits employees with burner accounts now.
1Password's sole differentiator between LastPass, Dashlane, and Bitwarden has been how polished their apps are on Mac and iOS. If you toss that to the side, you might as well use a cheaper (LastPass) or more open and secure (Bitwarden) alternative.
- cryptochromeOccasional Contributor
I welcome the unified code base. I could not care less whether the app "feels" like a fancy native Apple app. I care about progression, faster bug fixes and a working product that gives me the same experience and UX across all platforms. The looks of the app is irrelevant.
I am also using 1P on multiple platforms (macOS, Windows, and Android) and always felt the Windows app is lacking severely in user-friendliness (1P mini on Windows is an abomination compared to 1P mini on the Mac, to name just one example).
As for Electron being a memory hog... It's 2021. You should (and most likely have) a machine with at least 16 GB of RAM. Obsessing over Electron is manufactured outrage, nothing more. I run multiple Electron apps on my machine side by side on a daily basis (stuff like Discord, Slack) and never had any issues in terms of memory or other resources. Google Chrome, in its native macOS iteration, is a far heavier app than any of the Electron apps I use.
So yea, I asked for this and I think it's about time this finally happened. It means faster version iterations, faster bug fixes, faster innovation and progression for 1P going forward. Something we will all benefit from.
- dserodioOccasional Contributor
I use a Mac because I care about a consistent user experience across apps, not just within each app across platforms.
Me too. If I were to use only webapps I'd be using a Chromebook.
Very disappointed about this decision, every Electron app I've used (Slack, Discord, WhatsApp, Evernote…) is bloated and buggy. I guess 1Password is about to become of of these apps which I have to restart frequently to try and free some resources.
Just as I write this comment, Evernote is eating 49% CPU, WhatsApp using 1.7GB RAM, etc.