Loading…
Users of an insurance site kept being asked to verify their identity with a face scan, seconds after they had already done it. The logins were all working. The app was simply asking anyway, and it took me three rounds of debugging to find out why.
Signing in to the cabinet meant a biometric face scan — and three hours later you had to do it again. The session length wasn't the bug; the missing half was renewal. Now the site quietly renews itself for fifteen days, and the hardest part was making sure it never renews twice at once.
We retired the registration form on an insurance site - now your first face scan simply creates your account. Then a real user got locked out by an account they made back in 2023, and the fix taught me more than the feature did.
The policy-cancellation wizard already worked — users could verify identity, pick a policy, and submit a refund request. Then came a focused afternoon, the kind that actually decides whether a feature ships: cutting the product list to what the insurance core can really cancel, replacing scan-on-every-cancellation with a 30-minute verification window, making the wizard survive page reloads and language switches, and teaching the reason chips to match the product. About three hours of work, none of it a rewrite — all of it the difference between "works" and "ready".
We were releasing sign-in via MyID, Uzbekistan's face-recognition identity system — and found that on phones a successful face scan dropped users back on the login page as if nothing happened. Here's how we prepared the release, hunted the bug down to a single line, and fixed it.
Three improvements around our online policy cancellation: every attempt now starts with a real identity check through MyID, the page no longer asks for card details when a request already exists, and "nothing here yet" screens finally help instead of confusing.