Passing on enpass for now… ?? – Enpass Password Manager Review

We picked enpass to replace another password manager some time ago. We used it quite awhile successfully. This latest upgrade blew our opinion. We’re passing enpass. Why? (tl;dr) First, a cardinal sin. With the upgrade the package scrambled MY data. (The developer told me this was intentional!) Fields in items were re-ordered, new (and—to me—unwanted and useless) fields were added. Unacceptable. Second, where the Settings have a toggle for displaying “Subtitles”, nowhere is documented what a Subtitle is. For some items it is the website address (URL), for some the login (Username)—no consistency, no documentation. Useless toggle. Third, some of my items have both a “Username” (used for login) and an “E-mail” (through which the site manager may send communications—including password resets). Upon autofill, enpass persisted in placing the “E-mail” value (not the “Username” value) onscreen, yielding denied access. Fourth, enpass converted to an outdated password strength meter. (This has been argued in tech journals and even passed down to “general-interest” media for those not tech savvy. By the new enpass test, all our passwords appeared puny. Tests elsewhere (e.g., rumkin) showed them as strong. The enpass meter became useless and worth ignoring. Finally, reaching out to enpass for support may yield, if anything, “Thanks for noticing that, sorry for the inconvenience, we may consider it for a future release.”) Chasm. For now I’ll place enpass in the chasm of my App Store purchase history. I may consider it for a future release.
Review by fjpoblam on Enpass Password Manager.