Vlad
'Default password provider' with additional captions to inform the user of this
Can you expand on default captions (we are looking for exact text to use).
Caption when 'Orion Keychain' selected in Orion Settings > Passwords:
- New passwords are saved to Orion Keychain, accessible from other browsers that support Password Autofill.
- Passwords from other providers such as Safari, 1Password or Strongbox can still be used, but not updated.
Caption when '3rd party provider' selected:
- Passwords from providers such as Safari, 1Password or Strongbox can be used, but not updated.
An alternative design to the popup button with choices, could be a 'Use Orion Keychain' toggle button, i.e.:
[x] Use Orion Keychain
which can gray out the checkboxes in the Password Autofill section if de-selected, and defaults to 'on'.
This would make it clearer to the user what features they can expect to give up by not using Orion Keychain.
(again maybe worth explaining as caption text in the settings item?)
Can you expand on the text?
I think a 'Use Orion Keychain' toggle that disables the Password Autofill section checkboxes would make it clear enough to the user that if they go with 3rd party provider only (i.e. don't elect to use Orion Keychain), they won't be able to save new passwords.
One more suggestin: in the autofill menu,
- the 'Password Providers...' menu item when using Orion Keychain, may be more understandable if described as 'Other Password Providers...';
- it might flow better if it's at the end of the list (below 'Suggest new password...')
In general the easiest is to just use Orion keychain. You can even import all safari passwords to it so it is all native and avaialble. It is secure and uses same tech as Safari. And you can even use passwords you save to Orion keychain in Safari natively or export them later if you do not want to use Orion.
I've come to that understanding now. During on-boarding though, the mere thought of adopting another keychain made me wonder immediately about the prospect of the 2 password dbs going out of sync over time, whether I can cross-access them etc, all of which were hurdles towards a decision to import, and at a time when I was keen to test out the new browser.
Som, given it's a big ask to import the Safari keychain, these points you mentioned would definitely be appreciated by the tech savvy if they are made available during on-boarding, either as help text under a '?' button, or a link to a webpage.
The limitations of UX are mainly because of the limitations of available Apple APIs on macOS.
As a macOS developer I fully appreciate the 3rd-party-hostile API design problems you're up against, and salute Orion's efforts despite this.