Ask HN: How do you detect silent data loss in user-facing systems?
I’m not talking about crashes, errors, or failed requests.
I mean situations where data is lost quietly: - a user fills a long form, navigates away, and nothing is saved - a mobile browser suspends a tab and state disappears - a background sync never retries, but no error is reported
From the system’s point of view, everything “worked”. From the user’s point of view, their work is gone.
I’m curious: - Do teams actively try to detect this kind of silent data loss? - Or is it mostly accepted as unavoidable user behavior? - Are there metrics, patterns, or tools you’ve seen work for this?
Looking for real-world experiences, not theory. Some web analytics libraries will take screen recordings of each user session. (No comment on the ethics of that.) Making a habit of watching those recordings in the early days of releasing a new feature or major UX change is a common pattern for detecting when users give up and supporting theories as to why. I have seen many websites that detect if you've entered something into a field or touched some control and then try to switch away from the page. They then pop up a dialog box saying something like "you have unsaved changes, are you sure you want to leave?" Yeah, I’ve seen that too. I always feel a bit uneasy with that pattern though. It kind of pushes the responsibility back to the user and adds friction, and it still doesn’t help when things go wrong accidentally (tab suspension, crashes, backgrounded apps). Once that happens, there’s no warning and no signal that anything was lost. Is that just something teams generally accept, or have you seen other ways people deal with it?