Week 9: The 14-Day Wait That Felt Like 14 Months

Build in Public — Week 9 (June 15–28)

Closed testing on Google Play has a requirement: you need at least 12 testers actively testing your app for 14 days before you can apply for production access. In enterprise software, deploying to 1,000 users on day one is normal. In indie development, you beg 12 strangers to test your app and hope they stay interested for two weeks.

Finding testers was harder than I expected. I joined tester communities, posted in relevant forums, and reached out to people who had shown interest in the app. Gradually, testers signed up from different parts of the world — Europe, South America, Southeast Asia. Each new tester felt like a small victory. Someone I had never met was willing to download my app and try it.

The waiting period was emotionally harder than building the app itself. During development, you’re in control. If something needs to be fixed, you fix it. During the testing period, you just wait. You check the Play Console multiple times a day, looking for crash reports, feedback, or any sign that someone is using the app. Most of the time, the console shows nothing, which is both reassuring and unsettling.

The Feedback That Came

When feedback did arrive, it was invaluable. Testers found issues I had missed because I had been using the app the same way every day. They tried different inputs, used the app at different times of day, tested it on devices I didn’t have access to. A few suggestions came up repeatedly: the onboarding flow needed improvement, the help section was hard to find, and users wanted a way to rate the app easily.

I collected all the feedback, prioritized it, and implemented a new version within three days. The onboarding was redesigned, the help section was made more accessible, and a rate button was added. This rapid iteration was only possible because the testing group was small and engaged. If I had waited to collect more feedback, the changes would have taken longer. But with a 14-day clock ticking, speed mattered more than volume.

The Emotional Rollercoaster

The 14 days of closed testing taught me something about the emotional side of indie development. When you’re building alone, you develop a certain confidence about your product. It works on your phone. You’ve tested every feature. You know all the edge cases you’ve handled. But when real people start using it, that confidence gets tested in new ways.

Every crash report feels personal. Every piece of negative feedback stings. Every silent day — where testers have the app but don’t seem to be using it — makes you question whether the product is good enough. You have to develop a kind of emotional resilience that has nothing to do with coding or product design.

But there are also moments that make it worthwhile. The first time a tester says “this is useful” or “I’ve been looking for something like this,” the weeks of work feel justified. Those moments are rare during the testing phase, but they’re enough to keep you going.

What I Learned

Week 9 taught me that the testing phase is as much about psychology as it is about quality assurance. The product gets better through feedback, but the developer gets better at handling uncertainty, rejection, and the long gaps between positive signals. Both are necessary for shipping.

Next week: the bug that only happened at 10 PM.