Google makes you answer a form before your app goes anywhere near real users. Somewhere in the middle of it is a question that reads like a formality: does your app let people report a concern, and does someone look at it?
I've had a report button in TenderNest for a long time. Tap it on a note, type a reason, done. I built it, confirmed the tap worked, and moved on to the next thing, the way you do with a hundred small features when you're the only one building the app. I was ready to check the box and move to the next question.
Instead I filed a real test report and went looking for it on the review side, the screen only I ever see.
It wasn't there. It was never going to be there. The report saved fine, straight into a table nobody reads from. I'd built the "tell us" half of the feature and never finished the "someone hears you" half. All this time the button worked perfectly from where a user stands. You tap it, it thanks you, and nothing tells you it went nowhere after that.
That became the evening's real work instead of a checkbox. I routed reports into the queue I review, added a way to suspend an account, and made sure reported content remained available for review. I'd checked that someone could send a report. Now I checked that I could actually deal with it.
Nobody hit this. No user complained. I hadn't released the app yet. I found it because I was bored enough late at night to test my own button rather than trust that some earlier version of me had finished the job.
That's most of what solo safety work looks like, in my experience. Rarely a dramatic catch. Usually just deciding, for one evening, not to take the checkbox's word for it.
