1P_Ben It would seem that the decision to go non-native was arbitary, at least with regards to the user — it has resulted in a less functional, less stable, and potentially less secure solution.
And yet, inspite of all the discussion here about the fundermental problems that 1Password 8 presents and the critical bugs that still exist in this first release, Agilebits's response has been to consistently double-down — we know best.
I'm sorry to hear you aren't as thrilled with our new Knox design language as we are ...we're not looking to make further major changes to the design for 1Password 8
MacOS is not perfect but its intuitive for a reason — the Mac UI/UX only exists because of the consistency of its guidelines and the APIs that Apple provides — 1Password did not need a 'new design language' from a usability perspective, but clearly the javascript-based technologies underpinning version 8 have limitations that no amount of childish eye-candy can compensate for.
With the launch of 1Password 8, 1Password 7 is no longer supported ...it’s best to use the latest version ...I wouldn't encourage you to downgrade to 1Password 7.
How on earth is it best to use the latest version — that's disingenuous, it's certainly deluded. 1Password 7 is the upgrade here.
None of this bodes well. Agilebits have clearly chosen a direction of travel that shows contempt for its most loyal customers, and particularly their role in growing the company through the evangelising and supporting of 1Password to their extended circles of less tech-savvy friends, family and colleagues — misunderstanding this relationship is a massive miscalculation.