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
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
Well if your computer can't keep up with modern apps anymore, maybe it's time for an upgrade. You can't expect your old machines to perform well forever.
Did you miss the part where modern, brand new computers, including the latest Apple Silicon Macs, come with 8GB of RAM as standard?
Also, we are in a once-in-a-century global pandemic that has killed countless jobs and caused a global silicon shortage that is hampering production of new devices. It's not always easy or feasible to get a higher end machine since those SKUs tend to be build-to-order with weeks or even months of lead time.
It's not fair to treat it as if it was the final product.
It's just as fair as assuming that all the issues will be ironed out.
Besides, I wasn't treating it as the final version. I'm acknowledging where the wind is blowing, by 1p's own admission in several posts throughout these boards.
Nuance is really not that hard to understand.
That means right now, as in using the preview
Then stop using the preview and go back to the production version. There, problem solved. The early access version is not complete. That is really not that hard to understand. It's not fair to treat it as if it was the final product.
@privateUser
Yet, that is exactly how it feels for the years long 1P users.
If it feels like the end of the world to you, then maybe set your life's priorities straight. There are far worse things that could and will happen to you than your favorite password manager changing its looks. And if you keep judging a password manager by its "native feel", maybe rethink for what you buy a password manager in the first place.
I don't know how you came to this impression, but that is NOT what is happening.
You don't know that. Unless you work for 1p/AgileBits?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.
Reading what I wrote might help you. Here, try again:
Unfortunately for those of us using the preview on Mac for the moment
See that "for the moment" part? That means right now, as in using the preview. Your overzealousness in defending the 1p decision here might be making you jump to conclusions?
cryptochrome "Some here act as if 1P8 means it's the end of the world." Yet, that is exactly how it feels for the years long 1P users. Most of which chose 1P just because it was a native MacOS product. And guess what? One day it gets quietly replaced by something that has nothing left of a native MacOS app. Over night it went from a company that has started its business on MacOS platform to a generic "we sacrificed 90% of our customers to become a generic/boring cross platform Electron app."
Like I said, I hope AgileBits can clean it up. But so frequently these days, “it’s an alpha, it’ll get fixed!” never actually comes to pass for half or more of the problems users report, and those problems live on in production for years if they ever get addressed. I’ve seen it happen time and time again across several different types of software.
I installed 1P8 on my M1 iMac (16GB RAM) and used it with 1P7 at the same time. The difference is night and day. 1P7 uses around 130MB RAM on my system while the Electron app uses 250MB.
As far as the UI concerns, it definitely has nothing to do with a Mac app. It is too empty, scrolling feels unnatural to a Mac (no bouncing when reaching the top or bottom). I also prefer the categories on the side and not as a filter on top. All in all I prefer 1P7. It feels right on my Mac. I also do not like the way 1P8 preferences pop up. You also get only an x on the top right and no option to minimize the window, like on 1P7. It's disappointing. The only thing I liked is the search box, which works really well. Apart from that the Mac version is a big step backwards and a regression from 1P7 in all possible ways that matter to a user. For the business decision makers this is of course a great step, since they are saving lots amounts of money, by developing once for all platforms. The investors will definitely be happy.Well if your computer can't keep up with modern apps anymore, maybe it's time for an upgrade. You can't expect your old machines to perform well forever.
That being said, one user having 250 MB and another 75 MB clearly shows that this is not yet optimized. But if it can go down to 75 MB already, then I don't know how that can be a concern.
You are all judging an early alpha release and make assumptions based on that. You should at least give 1P the chance to deliver a final product before spamming the forums with manufactured outrage (that goes to everyone, not you in particular). Some here act as if 1P8 means it's the end of the world.
Several users have posted examples of 1PW8 using well in excess of 250MB. I hope AgileBits can get that cleaned up, but based on the track records of other apps that made the switch to Electron I’m not optimistic. For those other apps, usage dropped by 10-15% once all the optimizations had been implemented, and no further attempts at reducing consumption were made by the developers.
And of course 1PW8 is going to run fine on its own, where the real issue comes in is when several things are running… especially when many of things are also electron (hard to avoid these days). All it takes is a typical number of browser tabs and 2-3 electron/electron-like apps (slack, spotify, 1PW, evernote for example seems like a plausible combination) and the machine is going to have to start hitting the pagefile (even with memory compression) and performance will take a very noticeable hit.
I don’t intend to continue arguing, but resource consumption is a huge problem that’s going mostly unaddressed by the biggest names in software.
I am pretty sure 1P performs exceptionally well on a modern OS with just 8 gig of RAM installed. Especially on macOS, where we have things like memory compression.
It's a mute argument. The 1P folks have demonstrated in another thread how Electrum based 1P only uses 75 MB of main memory and another 25 MB for the Electrum renderer. On an installation with four accounts and thousands of objects.
