There are several competing password managers today of course! My take is that like Dropbox (disclaimer: paying Dropbox customer until iCloud Files is just a bit better), this is a feature, not a product (unless you need team or cross platform functionality, but for teams you should probably be enterprise grade with SSO instead of sharing creds).
I'd switch from BitWarden to a native Apple solution the moment the Keychain UX reached parity with BitWarden, n=1.
It is strictly for website address/passwords, so doesn't work for a more diverse robust security password manager.
And the sync is very flaky (when I create items within the setting application, they don't show up on my phone). And its multi steps to simply launch keychain since its not a true native app on MacOS nor iOS.
I like that keychain is limited, at least it makes me feel like there’s fewer possible vulnerabilities.
KeepassX and minikeepass on iOS are my go to for secure notes. I don’t see the need for super convenience with my credentials, I’m willing to do some work to access them.
Either way, I’m not handing over a database of login info to a SaaS company. Might make sense for large companies though.
As a sole user it's definitely a feature-not-product, but for teams 1Password really is a product with its extensive access controls etc.
Kinda reminds me of identity management / authentication. These also are features, right? But I feel a lot better about delegating that feature to a business whose core competency is that (eg. Okta, Google, …).
"Payment" also is a feature, but I'd never not use Stripe.
I'd switch from BitWarden to a native Apple solution the moment the Keychain UX reached parity with BitWarden, n=1.