Why does 1PW8 for Mac ignore the native passkey Web API?
I recently saw this post from Ricky Mondello (Apple's chief Passkey engineer) on Mastodon:
... and was wondering why AgileBits have chosen to do that?
Can anyone from AgileBits justify their reasoning behind not using the platform-native methods? All the replies to Ricky's post were in agreement, and lambasting 1PW8's UI for Passkeys.
I'd be very interested to hear from anyone who knows. Thanks.
1Password Version: 8.10.58
Extension Version: Not Provided
OS Version: macOS 15.2
Browser: Not Provided
Comments
-
please please can we get native autofill sometime soon even if it is just in the beta/nightly for now? It is just so painful that this is such user facing improvement and to have it be ignored or if it is in the works. That would be disappointing to have it kicked down the road as the feature already exists on iOS. Anyway, I am going to just going to keep asking until it happens.
and if it is in the works. Can it not the end of 2025?...can be bumped to the front of the line?
1 -
The team isn't closing the door on support for macOS AutoFill and I'll share your feedback with the team internally. For the time being, 1Password in the browser provides a consistent passkey experience for 1Password customers regardless of which browser or desktop platform (Mac, Windows, Linux, etc..) they choose to use.
Are there specific issues that you're running into with how 1Password handles passkeys today? You mentioned the UI, what specifically doesn't work for you? My apologies if you've shared this already in a previous thread.
-Dave
0 -
In my opinion, consistency across platforms is not as important as following the individual platforms UI standards and guidelines.
I would assume the vast majority of people choose their desktop OS because they prefer the user interface and way it operates. Making apps the same across platforms and different to the host OS, takes that preference away. In fact it means people have to learn how your app differs and adapt, rather than just "knowing" how to use it because they know the OS conventions.
Most people don't switch desktop OSs very often. People generally choose Mac or Windows (or Linux) and sticks with it for years. Unless you work in specific fields (e.g. web/software development) where you must use multiple OSs, how an app looks on another OS is irrelevant to most users.
In my experience, the reason developers choose to use the same cross-platform designs, technologies, and UIs, rather than building to take advantage of each platforms strengths and differences, is to save them development time and money - not for the customers benefit at all. In fact, it's usually to the customers detriment, as the app doesn't fit their OS perfectly, is bloated with cross-platform frameworks (duplicating the existing OS frameworks functionality), and often doesn't take advantage of OS specific features and runs slower than using native frameworks.
The 1Password Passkey UI just doesn't look like part of macOS - it doesn't even use the system font. It's a bit clunky in places. For example, logging into playstation/sony.com I get prompted to unlock 1Password first by the 1PW extension, which I attempt to do in the second differently styled (system?) dialog. That dialog disappears after authenticating but the 1PW extension hasn't noticed 1PW is unlocked and I have to refresh the page to get it to notice. Other times the "Unlock 1Password" button in the 1PW extension dialog just doesn't do anything. It's just not as seamless and friction-free as it should be.
1 -
@Dave_1P I have stated elsewhere. It is not consistent experience, creates unneeded friction, and confusion for most users.
So this statement:
"1Password in the browser provides a consistent passkey experience for 1Password customers regardless of which browser or desktop platform (Mac, Windows, Linux, etc..) they choose to use."This I just disagree with. It does not provide consistent experience. There is no other way to explain it.
1
