Is the 1Password 8 Mac electron app experiment about over so the dev team can get back to building a quality native app for the Mac? The other option is staying on 1Password 7 till I move my family account and three companies I consult with to another platform. I loved 1Password 7, 6, etc., but this version 8 is a mess. (Granted, it's better than most electron apps, but that is not a high bar)

1Password Version: Not Provided
\nExtension Version: Not Provided
\nOS Version: Not Provided

Is the 1Password 8 Mac electron app experiment about over so the dev team can get back to building a quality native app for the Mac? The other option is staying on 1Password 7 till I move my family account and three companies I consult with to another platform. I loved 1Password 7, 6, etc., but this version 8 is a mess. (Granted, it's better than most electron apps, but that is not a high bar)

1Password Version: Not Provided
\nExtension Version: Not Provided
\nOS Version: Not Provided

I have used 1Password for a long time. I like the native solution before 1password 8, 1password 8 as a mess in election framework. I consider to switch another instead of it. As an app user and developer, I think who provide an election solution to customer just not respect the users. , I hate the election framework app which just slow and fat.

Hey kleerkoat

Thanks for sharing, and for taking the time to explain what is important to you. Our current push with password generation is through our implementation of Apple's password manager resources. Apple describes this as \"A place for creators and users of password managers to collaborate on resources to make password management better.\" In practical terms what that means at the moment for 1Password users is that 1Password will suggest the strongest passwords possible that any given site can accept, as long as that site's password requirements have been added to the Apple repository. Defining a global set of rules seemingly runs contrary to this goal, as what various sites will accept can be quite different. You can still do that though, at least to some extent, if you wish.

Here are some screenshots of the options available in the password generator as it stands:

After you've made your selections, toggling the \"use as default for suggestions\" option will make the choices you've picked be the default. I'd recommend leaving it on \"Smart Password,\" which is the option that takes advantage of Apple's repo, but if you prefer random or memorable that is possible as well.

I hope that helps!

Ben

i've been a user since my iPhone3gs. it's the only app i willingly throw my cash at every year. it sounds like i am just a vanilla user. i have one vault. in all these years i've never tagged or organized anything. my thousands of passwords have just been thrown in there.

with that being said, i don't care if it's electron or something else. i would have liked to have seen us apple users get a native app since the apple community has showed you guys all this love through the years.

but reality and business is what it is. i've used 1P on windows. the thing that bothered me was the non-parity between windows and mac. i think, and am probably right having consistency between the platforms makes devlopment easier, maybe with electron updates and new features will come out quicker? also just as important is the look, feel, and functionality being consistent. so when you jump platforms you know it's 1P.

all i want is more ways to retrieve a password, i really want a more frictionless way to add one entry, and i want a fast search. the other features of 1P are just gravy on potatoes. we like gravy but we really know it's the potatoes are sustaining us.

i do have one teeny wish, being able to set a password style as default. i always have to change it when i make a password. we should be able to define our password style globally in preferences imo, then change it individually on creation if needed.

one more, with all the formulas for making a password available, you can generate a random password that covers just about every login requirement except mixing numbers with memorable. the other two you can get a mix or numbers, caps, special chars, and letters. it's only memorable that is lagging behind. i know, it's just a little thing. being a user since my 3gs i've had alot of time working with it, it's easy to get annoyed over that timeframe.

@aexvir There's a whole forum thread in regards to multiple vaults and unlocking all of them, you can read it here:
\nhttps://1password.community/discussion/122614/two-accounts-now-needs-two-different-passwords-every-time-you-login#latest

For some people, a single password for each vault can work, but in a lot of instances where you must use different passwords, the changes in 1Password 8 completely break normal usage. This is a major issue that simply won't be fixed.

Hi @aexvir:

While the specifics of this are a bit above my head, this was a reference I was pointed to:

All sorts of things you can get wrong in Unicode, and why

As I mentioned above, we do have plans to improve search even more, but I can't share more specifics at this time.

As for the discussion of account passwords, our Principal Security Architect, @jpgoldberg, has written a much better summary of how this makes more sense and makes it obvious what information unlocks with what account password:

\n

Suppose Patty has two accounts. One of them is her personal account and the other is with her job at the DIA (Dog Intelligence Agency). Patty does not want account PW unlocked most of the time, but she does want PP unlocked most of the time. In particular, she doesn't want the unlocking of the two accounts in lockstep. (All puns intended.) So. what does she do? She sets up a different account password for each. (Many of my examples involve my dogs Patty and Molly.)

\n\n

Molly, on the other hand (paw) has a personal account, MP, and a work account, MW. She wants to unlock both with a single account password. If you (or Molly) want to unlock two accounts using a single account password it makes most sense to set the same account password for both of those accounts. This is what I meant when I said the new system makes more sense.

\n\n

Suppose also that the DIA (not being as intelligent as their name claims) insists that account passwords be changed every two dog years. (Or every four months). If Patty always unlocks her work account with her personal account password she is certainly violating the intent of her employer's policy. Probably the letter of it as well. This is just one of the ways in which Patty may want to need different account password practices for her different accounts. She most certainly does not want to change her personal account password every few months.

\n\n

Molly wants her account unlocking to be in lockstep with each other. The most natural and semantically coherent way to achieve that is to have the same account password for those accounts she wants to unlock as a group.

\n\n

The old system

\n\n

In the old system, there was a little known and poorly understood concept of \"primary account.\" It would, on your own disk, have encrypted secrets needed to unlock other accounts. Your primary account was rarely something a user chose for that purpose, but instead was a consequence of the order in which they set up their accounts on that device. It was fairly arbitrary which account became the primary.

\n\n

One difficulty with the lack of transparency to the user about what account password was unlocking what is that users could forget that they even had a different account password for their non-primary accounts. Forgetting you have a separate password for an account is a good way to forget that password. Suppose Molly was using the old system. She regularly unlocked both her accounts with the password for her primary account on her computer. Note that \"primary\" may not mean the one that has the information that Molly needs the most. It just happens to be the one that she set up first on that device. She is never prompted for the account password for the \"secondary\" account (which might contain the most important data for her). She forgets that secondary account password and she forgets that she even has a different password for that account.

\n\n

Now suppose the nefarious Mr Talk (the neighbor's cat) steals Molly's computer, and there is no way for Molly to get it back from him. Molly also doesn't have good back ups. So now Molly needs to set things up on a new computer. She does have her Secret Keys for both accounts safely stored for such an event, but she doesn't have the passwords written down because she is supposed to remember them. She can set up her new computer and unlock what was in her old primary account, but she has no way to unlock what was under an account password that she'd forgotten about.

\n\n

This kind of problem is the result of the old system being very opaque to users. Now having a much clearer relationship between account password and the accounts it unlocks should very much reduce that problem. If you want multiple accounts to unlock when you give a single account password there is a very natural thing to do about it. You no longer have silent unlocking of accounts.

\n\n

[...] Now we make it easy for people (and dogs) to have multiple accounts, and these different accounts are part of different teams and families with their own policies. So we took the opportunity to design unlocking in a way that makes sense on their own at the expense of a substantial behavior change.

\n

Jack

thanks @\"jack.platten\" for the answer; when you're mentioning that

\n

The changes to search were made to improve search behavior for international languages.

\n

do you have any document I can be referred to as how having another surface is improving the search behaviour for international languages? I'm struggling to see how this is better and I'm curious to know the logic behind this change

\n

We recommend using the same account password across any 1Password accounts you may have

\n

woah... really? this kind of sounds like giving up on security just for the sake of working around an artificial limitation that wasn't there before... again I'm interested on the reasoning behind such change as I'm struggling to see how this is better than what we had earlier with 1password 7 :/

Hi @aexvir:

Thanks for your feedback on this. We're always striving to improve the performance of 1Password.

Dave has spoken just earlier today on the topic of the sidebar here, and we're going to continue to iterate to see if we can find a way to make everyone happy, but for the moment at least, we'll be sticking with the current design of vaults and tags in the sidebar, and categories in the dropdown.

Alfred integration is something we're still exploring, but I don't have specifics for you just yet.

Search is another area we're actively working on taking a look at. The changes to search were made to improve search behavior for international languages.

\n

for some reason it keeps unlocking only one vault when opening 1pw, and it's the one I use the least

\n

The short version is that 1Password 7 would unlock all 1Password accounts with the password of the first 1Password account (or Primary standalone vault) that was added to the 1Password app. 1Password 8 now however will only unlock accounts that share the same account password. We recommend using the same account password across any 1Password accounts you may have. If using multiple account passwords is necessary, after each account has been unlocked using its specific account password, using Touch ID or your Apple Watch to unlock will unlock all accounts.

Jack

I've just updated to 1pw 8 beta and I also want to chime in on this discussion, as it has been a disappointing experience from the first moments of using it :/

\n
• performance overall is just poor (13\" macbook pro 2020, i7, 16gb ram; not a slow machine)\n\n
  \n
  • scrolling feels sluggish
  \n
  • icons take 10+ seconds to load when scrolling
  \n
  • switching between items is immediate but the icon has ~3 seconds delay on being updated on the detail view
  \n
  • resizing the window feels bad, it's just laggy and the ui always struggles to catch up with the window size
  \n
  • clicking on the preview button on any document takes a couple seconds to open the preview
  \n
  • and many other overall interactions that just don't feel snappy
  \n
\n
• the menubar item is just useless, I miss 1pw mini
\n
• quick access is also useless, I already use the alfred integration; again, I miss 1pw mini
\n
• for some reason it keeps unlocking only one vault when opening 1pw, and it's the one I use the least
\n
• the search is annoying, why doesn't it filter the current items instead of popping yet another surface with them like on 1pw 7?
\n
• the sidebar is also useless, I don't use tags and I always search for stuff on all vaults; but I do use categories :(
\n
• the watchtower view also seems pointless? it was more comfortable to access it on the sidebar :/
\n
• and for some reason the web view of the watchtower isn't centered, and personally I find the overview \"progress bar\" comically large and silly; although those are small things
\n

these are the main points I'm struggling with, although I fully agree with the other points mentioned earlier. for now I've downgraded back to 1pw 7

dunno... it's just sad that an app that I have to use daily, and that I really enjoyed using; it's suddenly more annoying to use. it just feels a step back from what I already have with 1password 7, and I'm afraid of the day when I won't have a choice but to use 1pw 8

I'm not going to just jump on the \"electron bad\" wagon, right now this app has less features than 1pw 7 and some of the ux decisions taken on this new version makes the usage more cumbersome and slower than before and this affects me directly, be it an electron app or not

I'm also planning on keeping v7 around for as much as possible due to Electron. Apart from the bloat, there are many little things that just don't integrate nicely in macOS. For instance, unless it changed recently, every Electron app keeps its caches in non-standard places, not even bothering to exclude them from Time Machine, thus wasting time and space during every hourly backup...

Working on my wife’s iMac that has 1PW 7, it was so clear how much better 1PW mini still is over the new menu bar quick access for 1PW. Everything one would need pretty much is right there. Not at all true of the new version. Sad.