I’ve read 1PW’s explanation of how we ended up with 1PW 8 for macOS (posted below)
Maintaining “four full stacks of client implementations of our server APIs” meant “any changes needed to be coordinated across four teams.” So they wanted to build a common back end and new front ends for each OS.
And in the case of the Mac their plan was to build two versions “One written in SwiftUI that targeted the latest operating systems and another using web UI that allowed us to cover older OSes.” But that didn’t work out.
So today we have some people waiting to try the release version of the new 1PW Electron app before deciding if it is OK or not. We have others considering using the soon to be released new version of Keychain. Still others are evaluating established commercial products like LassPass or open source products like Bitwarden.
And for the adventurous I’ve run across a couple of password managers from developers that appear to have no previous experience with security software.
IMO it will be interesting to look back at all of this a year or two from now to see how everything turns out.
I’ll observe how it plays out in the next months.
I switched from a standalone version to a family plan in January of this year, so I have until Jan 2022 to decide if I’ll keep using it or not.
Family shared vault is really the key factor for me. That’s mainly why Apple keychain is not an option right now. Also, I really don’t trust Apple with such important information and don’t want to lock on more thing inside Apple’s ecosystem.
I actually found a better way to migrate from 1P account to KeePass. KeePassXC can import the opvault format almost perfectly, without messing with csv columns.
To do this, simply create a local 1Password vault, and copy all items in the 1password.com vault to the local vault.
Then in KeePassXC import menu choose import from 1Password. It asks for the location of the local vault, the vault password, and then prompts to save the converted kdbx file.
This is much pain free and I didn’t lose any information at all. There’s only some minor formatting issues because 1P has section dividers but KeePass doesn’t.
Which is fine, as long as it continues to work. My point was that one cannot reasonably expect “currently available sync methods” to work for the long haul.
This was a very interesting discussion, and it brought forth a view that I had never considered: that Apple may be falling behind the web frameworks. For some time I have had the feeling that Apple does not have a viable approach for developing on macOS and i(Pad)OS in a reusable way. They seem to be just throwing “cool stuff” out there to see what resonates. It was enlightening to hear my vague discomforts crystalized by professionals.
I have a local vault with my 1Password login. This is so I can sync iCloud on a new Mac and have the information I need with out having to lookup the personal key for the family subscription. Everything else is in in the family vaults or the work shared vault.
I have used 1Password since November 2007. I do not like local vaults are going away because I have a different password for it than the remote ones. I want to try the beta on pay personal mac, but have not had time to invest in the beta.
If cmd-/ logs me in and I can find what I need in the main app fast then I’m ok. I used obsidian, vs code and slack daily without much issue. All open at the same time.
I’m not as concerned with the UI of 1P as others here. It’s a tool to save and retrieve information; i.e. a database. If I “lived” in the app I might have more concerns.
I want my apps to help me get done what I need to do. If it fails at that it’s useless to me. But, I spend my time looking at code and the command line; the only beauty there is the font and colors I choose.
As I have experimented with Apple Keychain to replace 1PW I’m running into a significant limitation–one cannot add debit/credit cards to Keychain for autofill. Perhaps this will be possible with iOS15/Monterey? Adding to the Wallet doesn’t work if the card is a commercial card, e.g., my organization’s credit card.
Assuming this remains a limitation with iOS15/Monterey, I may need to stay with 1PW.
Am I correct in understanding the limitation or am I missing something?
I has and I’m aware of it. I just ran into a problem this morning when autofill did not open in Safari on the iPad even though the card information was in Safari (Mac). I thought I needed to add it while on the iPad but discovered that is not possible. I hope that iOS 15 enables one to add such information when using the iPhone or iPad.
