People see progress happening on something they don’t use (because standalone is basically feature-complete) and just want to gripe. I’ve been a stand-alone user for literally as long as I can remember and have never had a single issue with 1P.
I think it comes from a desktop software mentality, where things remained rather static relative to mobile’s rapid changes.
We've already announced that 1Password 7 for Mac and 1Password 7 for Windows will continue to offer standalone licensing.
Just a heads up that we're not removing the option for users like yourself that want to continue to use standalone vaults and the licensing to go with it.
That said, if you haven't, I would recommend and least trying our 1Password.com service. It was built and designed from the ground up to work for 1Password. It's an incredibly great experience. If you try it and aren't interested after the trial I'd love to hear your feedback on why. No credit card is necessary to try it.
Kyle
AgileBits
We recently updated 1Password 6 for iOS to work with the new Dropbox version 2 API. Going forward it should be fine until the next Dropbox API changes and presumably that will be a lot smoother than the change from version 1 to 2 that we just did... at least, I hope. We had several people put a lot of time into that transition.
I'm not sure if your comment applied directly to us, but for anyone wondering we tend to update 1Password pretty regularly. We are not at risk of ever being an app that falls on the "not continuously updated" lists I don't think. We were there on day 1 for Drag and Drop on iPad, and day 1 for Face ID. Much like we were there on day 1 for Touch ID and extensions.
1Password for Mac does not depend on Dropbox's API, it syncs directly to the Dropbox folder on the Mac. So as long as that doesn't change it has zero dependency on Dropbox itself.
Kyle
AgileBits
I was just talking about the hypothetical situation for iOS apps (and thus their users) _if_ the apps don't get updates.