I would be happy to pay the subscription fee for a native app, especially since my partner and parents can use it under the family plan. It works great for that

I would be happy to pay the subscription fee for a native app, especially since my partner and parents can use it under the family plan. It works great for that! I've been paying for upgrades since 2007 (version 2.0 I think). Except that version 7 also introduced some massive UI/UX regressions! There were so many that I started collecting them in a Ulysses note so that I wouldn't forget why 1Password has gone so far downhill. ---- Attachments: - Attachments used to be attached to entries by drag files there, and they'd show up at the bottom (if I wanted my passport, there'd be a single Passport entry with copyable fields + jpeg photos of front and back at the bottom). - Now, every attachment is a separate document cluttering up everything. If I want my passport, I search for "passport" and three separate entries come up: entry with passport details I can copy, and passport-front.jpg and passport-back.jpg. And if I delete Passport entry, the jpegs are still hanging around. - See [1][2] ---- When it doesn't sync, there's no "force sync" button on iOS. So I just sit there waiting... ---- Can't suppress "duplicate password" warning: - If I reuse a password on two or more entries, each of those entries shows this warning - No way to disable it, clutters up the UI - Some entries have an insecure password for local use, dev use, whatever, so let me disable the warning - Tons of threads on their forums about this complaining about it [3][4][5][6] ---- Another warning that can't be disabled in preferences: 2FA available but not enabled - If you have an entry where 2FA is available on that site, you cannot disable the warning if you don't have it set up - To actually disable this, you need to tag the entry with 2FA (which is dumb because it implies that it has 2FA, but the tag is showing that it DOESN'T have 2FA enabled) ---- Subdomain matching doesn't work: - This used to actually work fine but it was removed! - If you have a.test.com and b.test.com with different credentials, 1password treats them as the same website and will ALWAYS show entries for both, breaking autofill - See [7][8] ---- And after all this, I still planned to continue to use 1Password until they made their version 8 Electron announcement. That's absolutely the final straw and I won't be moving forward with them after that. 1 - https://discussions.agilebits.com/discussion/92007/1password-7-attachements-and-documents-issue https://discussions.agilebits.com/discussion/92007/1password... 2 - https://discussions.agilebits.com/discussion/111892/messy-documents-list https://discussions.agilebits.com/discussion/111892/messy-do... 3 - https://discussions.agilebits.com/discussion/95438/reused-password-warning https://discussions.agilebits.com/discussion/95438/reused-pa... 4 - https://1password.community/discussion/106132/suppress-the-reused-password-prompt https://1password.community/discussion/106132/suppress-the-r... 5 - https://discussions.agilebits.com/discussion/115492/feature-request-silence-reused-password-for-legitimate-cases https://discussions.agilebits.com/discussion/115492/feature-... 6 - https://1password.community/discussion/104141/watchtower-reused-passwords-esp-w-r-t-sso https://1password.community/discussion/104141/watchtower-reu... 7 - https://1password.community/discussion/89271/matching-sub-domains-no-plans-for-this https://1password.community/discussion/89271/matching-sub-do... 8 - https://1password.community/discussion/87028/stricting-url-matching-for-subdomains/ https://1password.community/discussion/87028/stricting-url-m...