I've been using 1PW for TEN years now. There have been some major hiccups along the way, but in general, it's been worth the trouble. There are several reasons I've stuck with Agile including: security, speed, and usability. Running v6 made me smile when I would hear about hacks related to Dashlane and Lastpass... I was fine with my local LAN sync over WiFi. Very secure! Over time, as my entirely family started using 1PW, the concept of shared groups of credentials started to look appealing. Fast forward to the Safari 13 release along with Agile's refusal to update 1PW v6 to be compatible, and we were finally pushed to upgrade to v7. (Admittedly, Apple forced a new/different/improved security model on Agile.)
To be fair, many of the bad reviews for 1PW now center on the subscription model. But as a developer, I don't have a problem paying reasonable annual fees for a critical piece of software. And 1PW is something I use every day.
While we've gained sharing functionality with teams and family in v7, we've lost more.
1PW 7 now takes between 1 to 3 SECONDS to pull up it's credentials page when you login to a website.
What's the big deal with 2 seconds? Compared to 1PW 6 this about 10x slower, and creates real usability issues for frequent users.
I'm completely accustomed to invoking 1PW6 and typing immediately to narrow a search... this is no longer possible, and there are many double/triple triggers of 1PW7 b/c it's easy to forget how slow it operates. (This on a 2013 12-core MacPro with 64GB of RAM and 4000 passwords... so NOT a computer or config issue.) You can find reports of slowness all the way back to 2018 for v7, with little or no resolution from the Support Forum (this will come up again below).
With 1PW6, most web-based logins would be filled in properly. With 1PW7 there's a new issue: focus is frequently NOT on the form elements of a page, so your selected ID/PW does NOT get filled in. I'm guessing this is a "feature" of the new app/browser-plugin model. But the end result is purpose-defeating: randomly, on different browsers and different webpages, selecting the default login from 1PW when invoked, then hitting return... does NOTHING.
No fields filled in... just nothing. You re-invoke 1PW, wait 2 seconds (b/c it's slow), may be good, may be nothing.
You must mouse to the ID field, click to guarantee focus, then invoke 1PW7.
This defeats the usability of this app.
This is a perhaps a "little thing", but it addresses a bigger issue.
6+ years ago, and mulitple times, I created bug reports AND posted to the support forums, pointing out one simple improvement (or bug, depending on your perspective):
1PW does NOT use the full URL to select the most appropriate password entry.
For many users, this is not a big deal: they only have one GMail login, and one Marriott login. But for developers, web designers, and anyone in a corporate environment, this is a much bigger deal.
Example of three URLs: abc.com/1 1 abc.com/22 abc.com/33
You have multiple IDs... why wouldn't 1PW auto-select (or rank at the top) the one that matches the CLOSEST?
Same thing for sub-domains: www.abc.com dev1.abc.com dev2.abc.com
This happens ALL THE TIME in corporate and development environments and it would be TRIVIAL to code an appropriate algorithm to select the MOST appropriate login based on the URL you are visiting.
Picky? Perhaps. But if the ONE THING you do in life is auto-fill passwords, shouldn't this work well?
And, if someone (and multiple others) have pointed this out to you for SIX YEARS, don't you think this could have been fixed? My guess: it points to similar oversights in other areas of support and bug fixing.
So: what are we left with?
Bitwarden perhaps. At least it is open-source and you can fix things yourself.
Or, perhaps other commercial apps that have decent security.
I'm hopeful Agile does the right thing and responds to its user base.