A user found the bug I should have caught myself

I was collecting user feedback on Iqra a few weeks ago. One of the users pointed out a bug. A section of the app was not working correctly. I knew the section. I had made changes to it recently — and shipped them directly to production without running through my usual testing flow.

A user told me about the bug. Not my emulator. Not my test release. A user.

I fixed the bug, made a few more improvements, added some things to the app. When I finally sat down to build the test release properly, this came back to me. So here it is — written down, for anyone building a product right now.

The flow that actually protects you

Every change, no matter how small, goes through three stages before it reaches your users.

First, test on the emulator. Catch the obvious breaks early, before anything leaves your machine. Second, publish a test release and run it on a real device. The emulator lies sometimes — screen sizes behave differently, performance feels different, interactions that work in simulation break on actual hardware. Third, only then push to production.

It takes more time than shipping directly. It has saved me more time than it has cost me.

Why developers skip this

It is not always laziness. Sometimes it is a small change — one line, one fix — and it feels unnecessary to run the full flow for something that minor. That feeling is exactly when the mistake happens. The smaller the change feels, the easier it is to justify skipping the test. And the skipped test is always the one that finds you later, through a user report.

The honest note

If you already do this — good. This was not written to teach you something you know. It was written because someone reading this is about to push a change directly to production right now, and this might be the thing that stops them.

Your users should not be your test environment.