Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
martijnvdwal
2 years agoNew Contributor
Please consider integrating 1Password as a Credential Provider on macOS.
For my personal life I am using iCloud Keychain to store my passwords and passkeys, for work we use 1Password and I am quite fond of using it. But I do have something I would like to see improved.
...
gussic
24 days agoSuper Contributor
I've been asking for this since 1Password 8 was first released. Hopefully the slightly more positive comments by Travis in the Reddit AMA bode well for this to be implemented in the near(ish) future. I understand it wouldn't completely replace the 1Password Safari extension but it would be fantastic to have for those that continue to experience issues with the extension (which are frustrating to say the least) as either a fallback, or a primary method, with the extension acting as a 'fall-back' for the autofilling types that aren't supported by macOS AutoFill. It would also make signing into desktop apps significantly better. I know Universal AutoFill exists, but there are still consistent issues with that.
- 1P_Dave24 days ago
Moderator
Thank you for the continued feedback! As Travis mentioned in our Reddit AMA, this is something that we're looking into and we appreciate you letting us know where you'd find this functionality useful!
-Dave
- gussic23 days agoSuper Contributor
Thanks 1P_Dave
I hope you can really stress to Travis and the other folks actually in charge of potentially implementing features like this that this pain point is growing really long in the tooth. I know you guys are all doing your best to create a great experience for everyone - but this is one instance where the degraded user experience has been consistently pointed out to you all for a number of years now with very little movement on it. Simply saying there are to many limitations to macOS Autofill when there are so many ongoing issues with the Safari Extension is just not good enough; although, I am sure it is unintentional, it really does show a lack of respect for the people who pay to use your App on platforms that you once prioritised.I understand there are priorities and as your company has grown it has naturally reassessed these and (sadly) shifted away from being an 'Apple first' company and started to pivot to Enterprise, Developers and Windows as your primary foci. I think we all (unfortunately) accept that but these obvious pain points are really frustrating to end users. I respectfully don't think enough attention has been paid to issues such as these or the litany of Safari extension issues that you and I have discussed over the years.
The Safari extension as the primary method of autofill was great when there was literally no other option but sadly the issues with it have only grown/multiplied as it has grown more complex. I appreciate the reasons for this are not solely on 1Password - I understand that Apple have imperfect APIs and implementation of APIs that are sub-par in areas but this lack of attention to a clear customer pain point would never have lasted this long in the 1Password 6 and 7 days.
I hope as a company you can remember your roots as an Apple first App and service, and whilst we may no longer be your primary target market maybe you can find a way to better respect the community that at one stage 1Password clearly loved. We still have a lot of affection for your App and Service, and really do want it to be the best it can be across all platforms, we're just tired of being the afterthoughts in terms of user experience that we've clearly been for a number of years now.(To state what I hope is obvious - none of this is directed at you specifically as an individual as I know time and time again over the years all you do is respond to us users on the forum here and try to help us in the best way you can. I know we all really do truly appreciate it. I hope this post can be flagged to senior management.)
EDIT: Just in case it wasn't obvious - macOS Autofill just works. When using Apple Passwords, or Strongbox (which I trialed for a while but didn't adopt as local vault and iCloud vault syncing just wasn't what I wanted) I NEVER had an issue where it failed to fill a username or password. I never had an instance where it bugged out or froze. Compare this to the 1Password Safari Extension just today, where I have had at least 4 times where it has failed to fill a username and password.- 1P_Dave22 days ago
Moderator
Thank you so much for taking the time to share your thoughts and for caring about 1Password and the experience on macOS. We wouldn’t be where we are today without passionate customers like you.
We absolutely care about the macOS experience, it’s why we’ve invested heavily in integrating 1Password 8 more deeply with macOS than any previous version. Features like Universal Autofill, SSH Agent, Terminal integration, and more are all designed to make 1Password feel at home on the Mac. We’ve also rebuilt 1Password for Safari using Apple’s latest web extension technology, moving away from the older Safari app extension to ensure a more modern experience.
We’re continuing to explore native macOS AutoFill integration closely, as mentioned earlier. While there are still some platform limitations to work through, it remains an area of active exploration and work to make sure we get it right. I'll definitely share your feedback with the appropriate folks internally.
-Dave