The day the app was finished, I didn't tell anyone. Do you understand that quiet feeling the night before release? The moment when an app I'd been building for months finally had all its features working. Icons lined up on the home screen, the screen opened when I tapped it, and I went through the entire flow from registration to login to posting. And yet, I quietly saved a screenshot to a folder, closed the screen, and ended that night alone. This essay begins from that night. It's about the experience of completing an app and even writing an announcement, but then not being able to press the "post" button for 23 days. I'll write honestly about why I was afraid and what changed things. There's almost no technical discussion here. This is about the heart of a creator. I hope it reaches even one person stuck in the same place.
The day after it was finished, I wrote the announcement. About 400 characters. The app's name, what it can do, the image of who I wanted to use it. I read it over many times, checked for anything odd, selected 3 screenshots. I'd even saved it as a draft. All that was left was to press "post"—and yet it sat untouched for 23 days.
The trap of "just a little more polishing"
At first, I had concrete reasons. "The font size bothers me." "The button colors aren't consistent." "The mix of English and Japanese feels a bit off." I'd fix something, then think "but maybe a little more," and fix it again. I spent the first week that way.
Around the second week, I suddenly realized: this will never end.
It wasn't that it wasn't finished. I just didn't want to admit it was finished. While I kept fixing things, I could stay in the "safe zone" of "not yet released." Since I hadn't shown it to anyone, no one could say anything about it. Without realizing it, I'd sunk deep into that subtle comfort.
I was getting better at making excuses to myself
What's interesting is that as the days passed, my "reasons for not posting yet" kept multiplying. "Monday is better for release announcements." "People don't check on weekends." "It might get buried by what's trending now." They all sound like real reasons. But looking back, I was just searching for "reasons not to do it today."
Even I found it strange, but I was more afraid of "being ignored" than "being criticized."
If someone saw it and said "this is hard to use," that would be okay. But if I posted and no one engaged with it. Zero likes, zero replies, zero shares, just quietly flowing down the timeline. I was terrified of that.
The feeling that what I made "never happened"
Not being seen by anyone felt worse than being criticized—that's what I felt. It seemed like months of time would just disappear.
But thinking about it calmly, that's a strange assumption, isn't it? If I don't post, I'm guaranteed no one will see it, yet I'm afraid of being ignored if I do post. If I think "no one will see it anyway," shouldn't posting give me at least some chance? Yet logic lost to emotion. Clean counterarguments don't work against fear.
The turning point came from an unexpected place.
In the community of indie developers I'm part of, I saw a post from someone. "It's about 60% complete, but I've had it in drafts forever, so I'm just gonna post it," with one screenshot. The UI was pretty rough, with some parts falling apart.
That post had 17 replies.
"I'm rooting for you." "I'm making something similar, so this makes me happy." "I want to see what comes next." "I'm curious how this works." Not a single harsh comment. Instead, there were comments of empathy for posting it rough and unfinished.
That changed my judgment
The premise of "post when it's finished" crumbled in that moment.
That person posted at 60% complete and reached 17 people. I had something I thought was 95% complete and hadn't shown it to anyone for 23 days. The answer was clear about which was right.
Posting something rough today reaches more people than polishing it to perfection. I thought I understood that intellectually, but seeing that post made me truly grasp it. Knowledge and understanding are different things.
That night, I opened the draft that had been sleeping for 23 days.
Reading it again, it wasn't that bad. I actually thought "why was I sitting on this?" It was a perfectly understandable piece of writing. I fixed one sentence, swapped out one screenshot, took a deep breath, and pressed "post."
My hands were shaking. Really. I'm not exaggerating.
The next morning
It didn't go viral. I'll be honest about that. But I had 4 comments. "I didn't know you were making this, I'm rooting for you." "I was thinking about making something similar." "I'll try it." "I'm looking forward to what comes next."
4 comments. The number alone is small. But for me, it was nothing like zero. Those 23 days in draft form were definitely zero. I was still scared, but I was glad I posted. I wanted to tell my past self: you did well.
There's something I can say honestly from this experience.
The condition of "just a little more polishing" has no end. Beyond the polishing, there's always "a little more" waiting. That's not diligence—it's just postponing fear. I learned that over 23 days.
Sometimes rough reaches people better
There's a paradox in the indie development world: imperfect things sometimes reach people better.
I think that 60% post got 17 replies because it was rough. People thought "I'm making something similar too" and "wow, they got this far, that's impressive." Perfectly polished things can feel too distant. They become "someone else's world," not yours.
Of course, minimum quality matters. I'm not saying you should post broken things. But if you set the condition "post when it's perfect," you'll never post. That much is clear now.
Completion begins "the moment you post"
There's one more thing I realized. Apps keep changing after you post them. You see reactions from people using it and find things to fix. Bugs appear. New features you want to add emerge.
In other words, "finish before posting" structurally doesn't work. The right order is to post and then move toward completion. During those 23 days I left it in draft, I lost all that time.
I wrote this essay not because the announcement went well. It's because seeing those 4 comments made me think "I should have posted instead of leaving it in draft." That's all.
If you have something finished right now, sleeping in your draft folder, I want to ask you one thing: "Isn't not showing it to anyone scarier than showing it?"
I only realized that question after 23 days. I don't think that was too late. But I do sometimes think I could have realized it sooner.
Posting is scary. It's still scary now. Every time I post, I'm scared. But leaving it in draft might be even scarier—that's the biggest thing I got from this experience.
Post something small today, if you can. I'm sure someone will see it.
Lily（@bokuwalily）― Indie developer. Making iOS apps and web services with AI as my partner.
🎁 A free bonus for reading all the way through
LINEで「自動化」と送って受け取る（実装テンプレ7本）
Lily（@bokuwalily）― After leading a marketing organization of 50 people as CMO, I now make iOS apps and web services independently. I consult on customer acquisition, user flow design, and AI implementation and business automation.
🖥️ My work and articles → bokuwalily.com
🐙 OSS → github.com/bokuwalily
🌍 Latest updates and inquiries → X @bokuwalily
