Six months ago I wrote a line in my year-end review file that I now think was half wrong: "Three launches this year, three flops. Stop launching quietly." I believed both halves of that sentence when I typed it. I was right about one half and badly wrong about the other, and untangling which was which took me until last month.
I am a solo developer. I have no growth team, no launch playbook, and no budget for a coordinated splash. When I ship, I ship alone, and the loudest part of any launch is usually the silence that follows. For a long time I read that silence as a verdict. This is the post I wish someone had handed me before I wrote that year-end line.
What I changed my mind about, in four lines:
- "Quiet launch" and "failed launch" are not the same event, and I had glued them together.
- The metric I judged launches by, signups on the day, was measuring the wrong window.
- Two of my three "flops" were still doing work months after I had written them off.
- The one thing I got right: chasing a spike for its own sake really is a bad use of my week.
The note I wrote to myself
I keep a launch log. One dated line per launch, in the same notebook where I track everything else, the kind of line that flows into my markdown vault on the days I sit down to curate. Going back through that log is the only reason I can write this with real numbers instead of remembered feelings. Here are the lines, lightly cleaned up.
2024-09-14 Product Hunt. 19 upvotes. Ranked ~30th for the day. Nothing.2025-01-22 Show HN. 4 points. Off the front of /newest in 35 minutes. Nothing.2025-04-03 Reddit r/iosapps update post. 6 upvotes, 2 comments, ~25 new users. Nothing.
Three times I wrote the word "Nothing." That word is the bug.
Launch one: the Product Hunt day I treated as a verdict
I had spent two weeks getting ready for Product Hunt. I built a gallery, wrote a maker comment, and lined up the one friend who would reliably click. On September 14, 2024, I posted at 7am Pacific and refreshed the page roughly every ninety seconds until lunch. By the end of the day I had 19 upvotes and a ranking somewhere around thirtieth. I closed the laptop and wrote "Nothing" in my log.
Here is what I could not see that day. Three of those 19 upvotes came from people who later emailed me. One of them is still using the app eighteen months later, and he sent me the single most useful bug report I have ever received, about a keyboard race condition I could never have reproduced on my own device. The Product Hunt day was a flop. The Product Hunt launch, measured over a year, brought me my most engaged early user. I had been grading a marathon by the time at the first mile marker.
Launch two: the Hacker News post that fell off in 35 minutes
On January 22, 2025, I posted a Show HN. It got four points and dropped off the new page in about half an hour. By the brutal arithmetic of Hacker News, that is close to invisible. I wrote "Nothing" again and started drafting a small apology to myself about how I clearly could not write a title that lands.
What I missed is that the post was indexed. For the next several months, a slow trickle of people searching for "iOS note to email" found that thread and the comments under it. One commenter had asked a sharp question about why I did not just use Shortcuts, and my answer to him became, almost word for word, a paragraph on my landing page that converts better than anything I wrote on purpose. The launch did not spike. It seeded. I did not own the word "seeded" yet, so I filed the whole thing under "failed."
This is the launch I was most wrong about, because I came closest to acting on the wrong lesson. After Show HN I seriously considered paying someone to "do launches properly." I am glad I did not. The post was already working. I simply could not see work that refused to arrive as a graph spike on day one.
Launch three: the Reddit post that actually was quiet
On April 3, 2025, I posted an update to r/iosapps. Six upvotes, two comments, about 25 new users I could attribute. Of the three launches, this is the one where quiet really did mean small. Months later I can find no thread of consequence leading back to it: no emails, no retained users I can trace, no sentence I quietly stole for the site.
I am including it on purpose, because the honest version of this post is not "every quiet launch is really a hidden win." That is the comforting story that keeps you doing something that is not working. Launch three was a modest, forgettable event, and pretending otherwise would make the other two reversals worthless. The skill is not telling yourself every launch mattered. It is being able to tell which ones did, and that takes longer than a day.
What was I actually wrong about?
The error was not optimism or pessimism. It was the measurement window. I judged every launch by signups-on-the-day, because that number is available, emotional, and arrives while I am still paying attention. The numbers that actually mattered (a retained user, an indexed thread, a sentence that explained the product better than I could) all showed up weeks or months later, after I had stopped looking and already stamped the launch "Nothing."
A spike is a measurement you can take in one afternoon. A seed is a measurement that requires you to come back in March. I had built my entire sense of whether launching was "worth it" on the one I could take quickly, which is exactly the wrong one for a solo dev with no paid acquisition and a product people adopt slowly.
What I got right, and am keeping
Here is the half of my year-end sentence I still stand behind. Chasing a spike for its own sake is a bad use of my week. I have watched indie developers, myself included, spend a fortnight orchestrating a Product Hunt run for a dopamine number that has evaporated by Thursday. For me, that prep time competes directly with shipping, and shipping is the only marketing I have ever found that compounds. So "stop launching for the spike" was correct. "Stop launching quietly" was the part I had wrong, and in December those two instructions felt identical. They are nearly opposite.
What I do these days is smaller and slower. I still launch, because launches create indexed surface area and the occasional excellent user. But I write the log entry with a blank space next to it, and I refuse to fill in the verdict for ninety days. The launch is not "Nothing." It is "pending." I check back in a quarter, and only then do I decide what it was.
Where I might be wrong next
I will name the part I am least sure about, because a confession that only covers old mistakes is too comfortable. My current belief is that ninety days is the right window. It might be too short. The Product Hunt user took eighteen months to surface that bug report; the Show HN thread is still trickling in. It is possible the correct unit for a solo launch is not a quarter but a year, and that I am about to repeat my original error one zoom level up: declaring launches "pending-failed" at ninety days when their real work lands at five hundred. Ask me in 2027. I will have a new line in the log, and probably a new thing I was wrong about.
If you have ever shipped into silence, I would like to know whether your quiet launches seeded or just sank, and how long you made yourself wait before you decided.
I'm a solo developer building Captio-style Simple Memo, an iOS app that turns a typed line into an email before you can switch apps. On the days I sit down to curate, those same lines collect in a markdown vault. I post here when I've changed my mind about something and worked out why.
Top comments (0)