Abstract
LastPass is a long-established password manager with 16.8M+ installs. Recent reviews describe autofill that stopped working reliably after a legacy feature was removed, forced re-authentication that ignores biometrics, and a broken support line — all layered on top of a well-known history of data breaches that already cost it goodwill.
Background
Once the default recommendation for password management, LastPass Password Manager is now the subject of some of the highest-upvoted complaints in this batch.
What it does
Stores and autofills passwords and logins from an encrypted vault across sites and apps, with biometric unlock and cross-device sync.
What changed
A legacy autofill mode was removed, and reviewers describe the replacement as unreliable — double authentication prompts, biometrics ignored in favor of the master password, crashes on selecting a saved credential.
Why it is soft
Long-time users still describe years of daily reliance on the product — the frustration is that a tool they trusted with everything stopped being dependable, not that they never wanted a password manager.
Strengths
The praise that survives is about years of daily habit, not a feature — that habit, plus a 16.8M-install base already primed to switch, is worth more than a typical incumbent's install count.
Years of daily reliance
Multiple reviewers describe using it across a decade and multiple platforms, showing real, durable habit in a category people don't casually abandon.
16.8M+ installs
A large base actively unhappy with reliability is a rare thing: proven demand paired with an open door to switch.
I've used LastPass even longer now since my last review. I used it on Windows computers first. It always worked great for me. When the Android app came out I started using it on my phone. I'm very satisfied with both versions of LastPass.
Market gap
The recurring complaints, grouped into named clusters, most-common first:
Autofill and biometrics stopped being reliable
By far the largest cluster: legacy autofill removed with a buggier replacement, double authentication prompts, biometrics ignored in favor of retyping the master password, and crashes when closing the fill prompt.
Trust eroded by data breaches
A recurring theme independent of the bugs: reviewers cite the company's history of data breaches as the reason they're finally done tolerating reliability problems they'd previously overlooked.
Support is effectively unreachable
Paid support that routes to a "not logged in" dead end, and a support phone number reviewers say connects to people who claim not to work for the company.
Edited to add this: still complete garbage especially now that legacy auto fill is removed, it's practically useless on S26. Been premium user for 7+ years. Recently, the Android app has become absolute garbage. Keeps crashing. Makes me authenticate twice, before selecting the credentials for a site and then again afterwards!
Legacy Fill Removed = 0 stars. LastPass has too many data breaches to mess around with app operation; adding/removing the parts of the app aren't worth keeping it around anymore because it's breaking the effectiveness of the app that once allowed me to overlook their "mishaps".
- Ship one autofill path and make it reliable, not two half-working ones. The single most-repeated complaint is a regression, not a missing feature — reliability here is the entire product.
- Never override a biometric unlock with a forced password re-entry. Multiple reviewers name this specific regression as the final straw after years of tolerance.
- Put a real, reachable human behind billing and account issues. A security product that's also impossible to get help from compounds the trust problem instead of offsetting it.
Build complexity
Estimated, not derived: one developer, part-time, no funding and no paid acquisition. This is the heaviest build in this batch — a password manager is real cryptography and OS integration, not a CRUD app with a lock screen.
| Workstream | Weeks |
|---|---|
| Encrypted vault + zero-knowledge sync architecture | 4.0 |
| Android autofill service integration | 3.0 |
| Biometric unlock + secure session handling | 2.0 |
| Cross-device account + encrypted backup | 2.0 |
| Billing, polish, store listing | 3.0 |
| Total | 14.0 |
Expected revenue
Assumes a modest $2.99/month tier, reached without paid acquisition — a deliberately conservative estimate given how crowded and trust-sensitive this category already is.
| Month 12, monthly | ||
|---|---|---|
| Installs | 15,000 | |
| Activated | 6,000 | 40% |
| Retained 30d | 3,000 | 20% |
| Paid | 600 | 4% |
| Revenue | $1,800 |
Biggest challenges
Not the autofill fix itself — the security expertise bar is real and unusually unforgiving, and the honest competition is already-trusted brands, not just the incumbent above.
Asymmetric downside risk
A mistake in the encryption or sync design isn't a normal bug — it's a potential breach, and this category punishes that kind of mistake far harder than a typical consumer app.
Named, trusted alternatives already exist
Reviewers already recommend switching to 1Password, Bitwarden, or Proton Pass — a new entrant competes with those, not just with a fixed LastPass.
AI angle
Neither condition for a genuine AI angle holds cleanly here — the core product is cryptography and reliable OS integration, which AI doesn't make meaningfully cheaper to build or newly possible. The one honest, modest use is operational rather than product: an AI support assistant that actually resolves common autofill/biometric issues in chat would directly answer the "support nightmare" complaint above, but that's a support-cost saving, not a product differentiator.
Conclusion
Skip it. The complaint volume is real and specific, but this category punishes a solo builder's mistakes unusually hard, the build is long, and reviewers already point to trusted, established alternatives rather than asking for a new unknown vault.
14 weeks
Time to v1
$2.99/mo
A deliberately conservative price
$1,800
Revenue at month 12
119
Upvotes on the top complaint, but named competitors already exist