You tested everything. Then real users showed up. What broke for you? 😅
First, thank you 🙏 More of you signed up, tried Ownfeed, and wrote to me yesterday than I expected.
Some of you hit a bug within minutes, told me, and came back after I fixed it. I don't take that for granted.
Here's the honest part: I tested every flow, many times, before launch.
Then real users arrived, and in the first hour something broke that had never broken in testing.
A few hours later, a second thing. Both fixed the same night.
What stings isn't the bug. It's that I felt ready, and the thing that broke was the plain part I had stopped looking at, not the hard part I worried about.
I don't think I'm special here. So, makers 👇
What broke on your launch day that had passed all your testing?
What do you do differently before every launch because of it?
I'll turn your answers into my own pre-launch checklist and post it back here.
Thank you again, everyone who tried it yesterday 🚀
Replies
Not launched yet, but a beta user did this to Top10Q: yesterday's unfinished items were still in today's 10 when they opened it the next morning. I had only tested the midnight reset in the same session, so now I check it the next day on a second account before I trust a build.
@mostafahosseini "Tested the midnight reset in the same session" is the whole story: it passed because time never actually passed. Real users bring real clocks.
"Check it the next day on a second account" goes straight into my checklist. Thanks, and good luck with the Top10Q launch.
@shun_build Fair point — same-session testing lied to me. I set a calendar block now to open a second account the next morning before I call a build good. Thanks for adding the checklist line.