3 ms·

I’ve been using 1Password for years, mainly because the data stays local. If they decide to go full cloud-mode I’m switching to something else or just write my

I’ve been using 1Password for years, mainly because the data stays local. If they decide to go full cloud-mode I’m switching to something else or just write my own cli password manager.

AGKyle 9y ago
Disclosure: I work for AgileBits, makers of 1Password We've already announced that 1Password 7 for Mac will be available via standalone licenses, and 1Password 7 for Windows will offer standalone vaults and be available via a standalone license model. So nothing is changing in that regard. Our 1Password.com is the default solution we send our users to but standalone vaults are an option for those that wish to continue down that path. Kyle AgileBits
- plainOldText 9y ago
  Thank you for your reply! I'm more than glad to pay for standalone licenses as I find 1Password extremely useful.
- RoXX1337 9y ago
  will 1Password 7 for windows finally have feature parity with the mac/ios versions? It has been borderline unusable for years, I complained in the forums like 2 years ago and all that has happened since then is that my thread got deleted.
  - AGKyle 9y ago
    Feature parity is something that our Windows team will be working towards. But you have to keep in mind that our Mac and iOS versions have existed for around 10 years. We last rewrote both of them for version 4 of each. 1Password for 4 iOS came out in late 2012, and 1Password 4 for Mac came out in late 2013. Also keep in mind that both our Mac and iOS applications have a fair bit of shared code. The entirety of their backend, cryptography, local database, and plenty of other utility classes. This means we write something for one and the other can often use it immediately. They're also by far our most popular clients so we have the most people working on them. Our Windows team has to try to keep up with that. So, as you can imagine they have a lot of work to do. I would not say they will be feature parity complete, more or less, ever. It's an uphill battle. However, I think it's safer to say that with 1Password 7 they will have the basics done that will allow them to start implementing more user facing features to try to narrow that gap. There will always be a gap, but it can certainly be a smaller gap. We don't delete any threads on our forum unless they are extremely egregious, so my guess is that the thread still exists unless you got out of line (or others maybe did). But we have always acknowledged that our Windows apps have had work to do. With 1Password 6 for Windows we rewrote the entire client from scratch. It used to be written in Delphi. The new client is written in C# and built on more modern Windows APIs. We wanted to build for the future this time but we also knew that it was going to set us back to square one. So about two years ago is when we started work on 1Password 6. It has come a long way, and with version 7 we'll see the return of standalone vaults and standalone licensing for those that want to remain on that path. Hope that helps some, I just want to set expectations accordingly. Our Mac and iOS apps haven't stopped iterating, and our Windows application was already behind by several years because of the rewrite, it also has nothing that it can share code with, so it's at a disadvantage. We want feature parity and we will likely reach that for the most common features but there will always be a gap. As long as you understand the above, we're happy to field requests for what you believe needs to be there that isn't already there (in version 6). Kyle AgileBits

I’ve been using 1Password for years, mainly because the data stays local. If they decide to go full cloud-mode I’m switching to something else or just write my own cli password manager.

AGKyle 9y ago

Disclosure: I work for AgileBits, makers of 1Password We've already announced that 1Password 7 for Mac will be available via standalone licenses, and 1Password 7 for Windows will offer standalone vaults and be available via a standalone license model. So nothing is changing in that regard. Our 1Password.com is the default solution we send our users to but standalone vaults are an option for those that wish to continue down that path. Kyle AgileBits

plainOldText 9y ago
Thank you for your reply! I'm more than glad to pay for standalone licenses as I find 1Password extremely useful.
RoXX1337 9y ago
will 1Password 7 for windows finally have feature parity with the mac/ios versions? It has been borderline unusable for years, I complained in the forums like 2 years ago and all that has happened since then is that my thread got deleted.
- AGKyle 9y ago
  Feature parity is something that our Windows team will be working towards. But you have to keep in mind that our Mac and iOS versions have existed for around 10 years. We last rewrote both of them for version 4 of each. 1Password for 4 iOS came out in late 2012, and 1Password 4 for Mac came out in late 2013. Also keep in mind that both our Mac and iOS applications have a fair bit of shared code. The entirety of their backend, cryptography, local database, and plenty of other utility classes. This means we write something for one and the other can often use it immediately. They're also by far our most popular clients so we have the most people working on them. Our Windows team has to try to keep up with that. So, as you can imagine they have a lot of work to do. I would not say they will be feature parity complete, more or less, ever. It's an uphill battle. However, I think it's safer to say that with 1Password 7 they will have the basics done that will allow them to start implementing more user facing features to try to narrow that gap. There will always be a gap, but it can certainly be a smaller gap. We don't delete any threads on our forum unless they are extremely egregious, so my guess is that the thread still exists unless you got out of line (or others maybe did). But we have always acknowledged that our Windows apps have had work to do. With 1Password 6 for Windows we rewrote the entire client from scratch. It used to be written in Delphi. The new client is written in C# and built on more modern Windows APIs. We wanted to build for the future this time but we also knew that it was going to set us back to square one. So about two years ago is when we started work on 1Password 6. It has come a long way, and with version 7 we'll see the return of standalone vaults and standalone licensing for those that want to remain on that path. Hope that helps some, I just want to set expectations accordingly. Our Mac and iOS apps haven't stopped iterating, and our Windows application was already behind by several years because of the rewrite, it also has nothing that it can share code with, so it's at a disadvantage. We want feature parity and we will likely reach that for the most common features but there will always be a gap. As long as you understand the above, we're happy to field requests for what you believe needs to be there that isn't already there (in version 6). Kyle AgileBits